]
Peter Brewer updated JBSEAM-4375:
---------------------------------
Attachment: nested_MEI_problems_updated.patch
Updated patch to unflush the child conversation. Otherwise, entities in the child
component remain passivated.
ManagedEntityInterceptor destroys components in parent nested
conversation, when ending a nested conversation
-------------------------------------------------------------------------------------------------------------
Key: JBSEAM-4375
URL:
https://issues.jboss.org/browse/JBSEAM-4375
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Reporter: Darryl Smith
Attachments: nested_MEI_problems.patch, nested_MEI_problems_updated.patch,
TEST_CASE.zip
setup:
Parent (cid1)
-> First Nested (cid2)
----> Second Nested (cid3)
cid3: conversation.endAndRedirect(true); which calls setLongRunningConversation(false);
FacesManager's redirect method tries to encode the page parameters of the parent
view, which accesses a component
created in cid2 the conversation we are returning to.
This triggers ManagedEntityWrapper's switchToConversationContextOfComponent which
switches the current conversation to cid2
after ManagedEntityWrapper wraps the component ManagedEntityWrapper's
restorePreviousConversationContextIfNecessary method is called with oldCid = cid3
which triggers Contexts.getConversationContext().flush();
When flush is invoke the conversation (cid2) isn't long running, so flush removes all
components created in cid2
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: