[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4411) jPDL re-installing its first seam object

jPDL re-installing its first seam object ---------------------------------------- Key: JBSEAM-4411 URL: https://jira.jboss.org/jira/browse/JBSEAM-4411 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Environment: WinXP64 MyEclipse JBoss latest RF Reporter: Tony Herstell Priority: Critical Given this snippit <start-state name="entry"> <transition name="start" to="getUsersDetails"> <action expression="#{risingstars.registrationController.initUpdateRegistrationDetails}"></action> </transition> </start-state> <page name="getUsersDetails" view-id="/pages/user/updateUserDetails.xhtml" redirect="true" no-conversation-view-id="/home.xhtml"> <description>Updating of User (#{risingstars.user.lastname}, #{risingstars.user.firstname})</description> <transition name="cancel" to="end" /> <transition name="next" to="evaluateDetails"/> </page> I enter the jPDL and the bean has a User in scope... say (say id 123) auto created by @In(create=true) @Out(required=true) private User user; I then do this in initUpdateRegistrationDetails : this.user = (User) entityManager.createQuery("from User u where u.email = :email").setParameter("email", credentials.getUsername()).getSingleResult(); Which forces the user in scope to now point to this new user (say id 456) What happens if by the time we get to the next page we have switched back to the original User (123).