[ 
https://issues.apache.org/struts/browse/SHALE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40841
 ] 

Veit Guna commented on SHALE-427:
---------------------------------

Yes, Craig already mentioned that, but this is a simple usecases that shouldn't 
need any coding at all.

Nevertheless, thanks for that hint.


> Allow non-dialog outcomes to be handled with ease
> -------------------------------------------------
>
>                 Key: SHALE-427
>                 URL: https://issues.apache.org/struts/browse/SHALE-427
>             Project: Shale
>          Issue Type: Improvement
>          Components: Dialog
>    Affects Versions: 1.0.4
>            Reporter: Veit Guna
>
> Currently there's no easy way to include the shale dialog component into an 
> existing webapp that has non-dialog links like menus (always visible).
> So, when entering a dialog from within a menu, it is not possible to leave 
> the dialog through menu links without putting all possible outcomes to the
> dialog configuration (doh!).
> Spring Webflow offers the possibility to include global-transitions which are 
> inherited to the single dialogs. But that isn't very handy, too. For example 
> if I add a new menu entry, I always have to remember to update the webflow 
> (and of course the jsf navigation rules).
> Perhaps it could be configured per shale dialog whether non-dialog outcomes 
> are valid. In addition shale could check if a normal jsf transition for the 
> given outcome exists and maybe give a warning or something if not. A kind of 
> fallback.
> Other ideas are welcome.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to