This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

Comment

But if you think of it, we always use a menu to move from a window to another window without saving anything (on desktop), so an invocation of action in menu would seem weird. Is there any usecases about using menu to invoke an action ? using it as a navigation ?

Comment

The only question I have with this approach is that the menu onclick will start a new flow. When the user selects a new menu item which triggers a new flow how will the old flows be terminated or removed?

Comment

I'm not sure that there is a built in mechanism for this. Of course, the session timeout will remove all flows along with the session.

I have seen examples of a servlet filter to remove expired flows from the current session.

The other option would be to disable/enable menu items to ensure that flows are completed prior to invoking another? This would be my preferred option but the first one is valid also. Perhaps you could raise a JIRA issue to have it added.