Conversation propagation inconsistency -------------------------------------- Key: JBSEAM-4280 URL: https://jira.jboss.org/jira/browse/JBSEAM-4280 Project: Seam Issue Type: Bug Components: Wicket Affects Versions: 2.1.2.GA Reporter: Cruz Fernandez Storing a list of entities in the conversation is not working correctly. On several cases a list of nulls is produced instead of the list of entities. The "EntityBeanList" is in passivated state when a page is used for a second request (for example when an onClick method is executed, or the page is refreshed with F5 in the browser). I have debugged the LifeCycle and I realized the "PREPARE_REQUEST" step is calling the global UNFLUSH in a temporary conversation context. Afterwards in step "RESOLVE_TARGET" the conversation is restored to the long-running but the UNFLUSH is never called. The unflush method of ServerConversationContext activates all the lists in the context, but should be called AFTER the conversation is propagated. -- 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