[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1907) Upgrade Ajax4jsf and Richfaces to Richfaces 3.1rc5

[ http://jira.jboss.com/jira/browse/JBSEAM-1907?page=comments#action_12375837 ] Christian Bauer commented on JBSEAM-1907: ----------------------------------------- Isolated the problem, it's the page parameter (documentHome.setNodeId). Which might have something to do with the Ajax4JSF update or not. This is the form submit before the update: (http-192.168.0.4-8080-2hread) 10:16:12,683 TRACE [SeamPhaseListener] before phase: RESTORE_VIEW 1 (http-192.168.0.4-8080-2hread) 10:16:12,683 DEBUG [FacesLifecycle] >>> Begin JSF request (http-192.168.0.4-8080-2hread) 10:16:12,684 DEBUG [SeamPhaseListener] beginning transaction prior to phase: RESTORE_VIEW 1 (http-192.168.0.4-8080-2hread) 10:16:12,684 DEBUG [UTTransaction] beginning JTA transaction (http-192.168.0.4-8080-2hread) 10:16:12,696 TRACE [SeamPhaseListener] after phase: RESTORE_VIEW 1 (http-192.168.0.4-8080-2hread) 10:16:12,697 DEBUG [Manager] No stored conversation, or concurrent call to the stored conversation (http-192.168.0.4-8080-2hread) 10:16:12,698 TRACE [RootInterceptor] intercepted: documentHome.POST_CONSTRUCT (http-192.168.0.4-8080-2hread) 10:16:12,698 TRACE [RootInterceptor] intercepted: documentHome.create (http-192.168.0.4-8080-2hread) 10:16:12,699 TRACE [RootInterceptor] intercepted: feedDAO.POST_CONSTRUCT (http-192.168.0.4-8080-2hread) 10:16:12,699 TRACE [RootInterceptor] intercepted: nodeDAO.POST_CONSTRUCT (http-192.168.0.4-8080-2hread) 10:16:12,699 TRACE [RootInterceptor] intercepted: userDAO.POST_CONSTRUCT (http-192.168.0.4-8080-2hread) 10:16:12,700 DEBUG [SessionImpl] opened session at timestamp: 11891529726 (http-192.168.0.4-8080-2hread) 10:16:12,700 DEBUG [ManagedPersistenceContext] created seam managed persistence context from EntityManagerFactory (http-192.168.0.4-8080-2hread) 10:16:12,707 TRACE [RootInterceptor] intercepted: documentHome.setNodeId (http-192.168.0.4-8080-2hread) 10:16:12,711 TRACE [SeamPhaseListener] before phase: APPLY_REQUEST_VALUES 2 This is the form submit after the update: (http-192.168.0.4-8080-1hread) 10:24:04,614 TRACE [SeamPhaseListener] before phase: RESTORE_VIEW 1 (http-192.168.0.4-8080-1hread) 10:24:04,614 DEBUG [FacesLifecycle] >>> Begin JSF request (http-192.168.0.4-8080-1hread) 10:24:04,614 DEBUG [SeamPhaseListener] beginning transaction prior to phase: RESTORE_VIEW 1 (http-192.168.0.4-8080-1hread) 10:24:04,615 DEBUG [UTTransaction] beginning JTA transaction (http-192.168.0.4-8080-1hread) 10:24:04,625 TRACE [SeamPhaseListener] after phase: RESTORE_VIEW 1 (http-192.168.0.4-8080-1hread) 10:24:04,625 DEBUG [Manager] No stored conversation, or concurrent call to the stored conversation (http-192.168.0.4-8080-1hread) 10:24:04,625 TRACE [SeamPhaseListener] before phase: APPLY_REQUEST_VALUES 2 So page parameters are no longer set on the view on form submits, hence APPLY REQUEST VALUES works on a view that is in an illegal state. -- 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