[
https://jira.jboss.org/jira/browse/JBSEAM-4148?page=com.atlassian.jira.pl...
]
Norman Richards commented on JBSEAM-4148:
-----------------------------------------
i've been looking into this, and I'm not sure that the current behavior is wrong.
The exception filter happens outside of faces/seam lifecycle, and so it's natural to
assume that Seam will have cleaned up it's state. The fact that it didn't always
do this correctly before was a bug.
That being said, it's not unreasonable to hope that we could support this in some way.
However, I'm not entirely sure if we can do this without it being a complete hack.
I'm exploring whether or not we can save some of the context objects to be used in the
the pseudo-context we use for doing redirects. However, I'm feeling that such a
change will likely be too large for this release, since we won't have much time to
determine if it causes any other problems with properly cleaning up. I'm not going to
move it out of the release just yet as I'm still looking into some redirect-related
issues which might make this one more manageable.
Exception Filter Regression on Page Parameter Propagation
---------------------------------------------------------
Key: JBSEAM-4148
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4148
Project: Seam
Issue Type: Bug
Components: Exception Handling
Affects Versions: 2.1.2.CR1
Environment: Ubuntu 8.04, Seam 2.1.2.CR1, JDK 1.6.0_07, JBoss App Server
4.2.3.GA
Reporter: Mark Torres
Assignee: Norman Richards
Fix For: 2.1.2.CR2
Page parameters bound to event -scoped components are not being propagated during
redirects on the exception filter.
--
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