[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3674) Custom parameter value in <redirect> is not being propagated (regression)
Dan Allen (JIRA)
jira-events at lists.jboss.org
Mon Dec 1 16:43:37 EST 2008
[ https://jira.jboss.org/jira/browse/JBSEAM-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12440641#action_12440641 ]
Dan Allen commented on JBSEAM-3674:
-----------------------------------
As it turns out, this was a bug in hot deployment. The page descriptors were being read in outside of Seam's application context, which was causing the expressions to be initialized w/o a FacesContext. Hence, when it came time to resolve the expressions, they came up empty. I have corrected this error and also added unit tests to verify it doesn't bite us again.
> Custom parameter value in <redirect> is not being propagated (regression)
> -------------------------------------------------------------------------
>
> Key: JBSEAM-3674
> URL: https://jira.jboss.org/jira/browse/JBSEAM-3674
> Project: Seam
> Issue Type: Bug
> Components: JSF Integration
> Affects Versions: 2.1.0.SP1
> Reporter: Dan Allen
> Assignee: Dan Allen
> Fix For: 2.1.1.CR2
>
>
> I want to propagate a param so that it survives a redirect. This is what I have done until now.
> <navigation from-action="myaction">
> <redirect view-id="/pages/page.hxtml" >
> <param name="category" value="#{param.name}"/>
> </redirect>
> </navigation>
> However, since 2.1, this doesn't work anymore. The param is still propagated but not the value.
--
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