[
http://jira.jboss.com/jira/browse/JBSEAM-2096?page=all ]
Norman Richards closed JBSEAM-2096.
-----------------------------------
Resolution: Done
Fixed. These components are manually removed from the page context by the phase listener.
When the components were changed from unwrap to factory components, the component name
of the classes changed, which messed things up.
I think we need to revisit these components at some time, as coupling the phase listener
to them is a bad design. In my limited examples, these components worked correctly as
EVENT scope components, but I'm not sure if that's the right decision.
conversationStack and conversationList don't get refreshed
----------------------------------------------------------
Key: JBSEAM-2096
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2096
Project: JBoss Seam
Issue Type: Bug
Reporter: Norman Richards
Priority: Minor
Fix For: 2.0.0.GA
The changes here seem to be causing problems:
http://fisheye.jboss.com/changelog/JBoss?cs=MAIN:gavin:20070708211336
I'm not sure if this affects other components, but the changes the values to be
cached in page scope. This causes a problem if an action causes a conversation to begin
but doesn't navigate to a new view. We should either revert the changes or perhaps
change these components to EVENT scope. (I'm not sure if there are any issues moving
to EVENT scope. If there are, then these should revert to being @Unwrap components)
--
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