[
http://jira.jboss.com/jira/browse/JBSEAM-1293?page=all ]
Gavin King closed JBSEAM-1293.
------------------------------
Resolution: Out of Date
Right, this is a known bug in MyFaces. Nothing we can do about it, except get off MyFaces
and migrate to the RI (which we already did do).
Page parameters not working
---------------------------
Key: JBSEAM-1293
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1293
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Reporter: Chris Rudd
Im attempting to use the Page parameter feature detailed in section 5.1.1.1 of the
documentation.
<pages>
<page view-id="/edit.xhtml">
<param name="id" value="#{editor.id}"/>
</page>
</pages>
based on my understanding of the functiuonality if i go the url /edit.xhtml?id=foobar
then editor.id should be set to 'foobar'.
This is not occuring. After tracing the code it seems like this is where the magic should
happen:
AbstractSeamPhaseListener.java : 70
//apply page parameters to the model
if ( facesContext.getRenderResponse() )
{
Pages.instance().applyRequestParameterValues(facesContext);
}
else
{
Pages.instance().applyViewRootValues(facesContext);
}
Im using myfaces 1.1.4 with server side view state. What appears to be happening is that
myfaces will restore the saved view state (im not sure it should be, as its a GET
request). When this happends facesContext.renderResponse is never called.
Thus when it gets to the above code, the page parameters are restored from the wrong
location.
--
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