[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4495) Page actions do not work with JSF 2.0
[
https://jira.jboss.org/jira/browse/JBSEAM-4495?page=com.atlassian.jira.pl...
]
Dan Allen commented on JBSEAM-4495:
-----------------------------------
If we get the change we are requesting in the JSF issue, then here is what we can do.
After a page action, we check to see if the navigation case was derived from implicit
navigation. If so, we only invoke navigation if the outcome has the syntax of a view ID
(e.g., /main.xhtml). (Or perhaps we just disable navigation outright in that case). We
just don't want to surprise the user and we want to have some sort of reasonable
backward compatibility. We might even need a setting in Seam.
Page actions do not work with JSF 2.0
-------------------------------------
Key: JBSEAM-4495
URL: https://jira.jboss.org/jira/browse/JBSEAM-4495
Project: Seam
Issue Type: Bug
Components: JSF Integration
Affects Versions: 2.2.0.GA
Reporter: Jozef Hartinger
Assignee: Norman Richards
Priority: Blocker
Fix For: 2.2.1.CR1
Looks like implicit navigation in JSF 2.0 messes up with page actions in Seam. For
instance, the following page action from the booking example:
<page view-id="/home.xhtml" action="#{identity.isLoggedIn}">
seems to cause the result of the action (false) to be taken as an implicit navigation
information and the application fails with
HTTP Status 404 - /seam-booking/false.seam
--
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