[
http://jira.jboss.com/jira/browse/JBSEAM-1574?page=comments#action_12370193 ]
Norman Richards commented on JBSEAM-1574:
-----------------------------------------
Functionally, this change looks ok to me. The only think I see is that we are sort of
getting confused about which aspects of the first view and which aspects of the second
view are applied. As it exists now, all the aspects of the first view are applied,
except we render a different view. (if you wanted the aspects of the second view applied,
you could redirect and everything would be as you expect)
With this change, settings like login-required and no-conversation-view are taken from the
first view, but the action and conversation settings are taken from the second view.
Compare this to a non-redirect navigation in faces-config.xml where all aspects of the
second view would be applied.
I don't know how much any of that matters, but I thought I'd give my assessment.
pages.xml actions are not called when using "render" with
s:link and s:button
-----------------------------------------------------------------------------
Key: JBSEAM-1574
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1574
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 2.0.0.BETA1
Reporter: Michael Youngstrom
Assigned To: Gavin King
Fix For: 2.0.0.CR1
<page view-id="/list.xhtml">
<navigation>
<rule if-outcome="detail">
<render view-id="/detail.xhtml"/>
</rule>
</navigation>
</page>
<page view-id="/detail.xhtml"
action="#{bean.loadDetail}"/>
Does not appear to call #{bean.loadDetail} when the list navigation rule is executed.
Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira