[seam-issues] [JBoss JIRA] Closed: (JBSEAM-4519) Conditional navigation rules vs JSF 2.0
Marek Novotny (JIRA)
jira-events at lists.jboss.org
Thu Feb 4 13:32:19 EST 2010
[ https://jira.jboss.org/jira/browse/JBSEAM-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marek Novotny closed JBSEAM-4519.
---------------------------------
Fix Version/s: 2.2.1.CR1
Resolution: Done
it will be documented in JBSEAM-4495 until JSF 2 allows to turn off implicit navigation or any other solution to get rid of this requirement defining navigation rule for non-null outcomes.
> 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
> Fix For: 2.2.1.CR1
>
>
> 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
More information about the seam-issues
mailing list