[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4519) Conditional navigation rules vs JSF 2.0

[Stephan Bublava (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12503252#action_12503252 ] 

Stephan Bublava commented on JBSEAM-4519:
-----------------------------------------

Adding a fallback rule so that all outcomes are covered is an easy workaround. If this is actually required then it would be good to have a note in the documentation that explains this.

> Conditional navigation rules vs JSF 2.0
> ---------------------------------------
>
>                 Key: JBSEAM-4519
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4519
>             Project: Seam
>          Issue Type: Bug
>          Components: JSF Integration
>    Affects Versions: 2.2.0.GA
>            Reporter: Stephan Bublava
>
> If the outcome of an action method is not covered by a navigation rule, you stay on the current page with JSF 1.2. With JSF 2.0 the outcome is interpreted as view id.
> Example:
> <page view-id="/administration/currency/edit-currency.html">
> 	<navigation from-action="#{currencyEditor.confirmChanges}">
> 		<rule if-outcome="confirm">
> 			<render view-id="/administration/currency/confirm-edit-currency.html" />
> 		</rule>
> 	</navigation>
> </page>
> If currencyEditor.confirmChanges() returns "edit", JSF 2.0 tries to render /administration/currency/edit.html instead of /administration/currency/edit-currency.html.
> BSEAM-4495 describes a similar problem.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira