[ http://issues.apache.org/jira/browse/ADFFACES-261?page=comments#action_12447586 ] Adam Winer commented on ADFFACES-261: -------------------------------------
What about hooking ViewHandler.writeState()? In JSF 1.1, this might fire slightly earlier than you want (on the close of h:form, not actually when the page completes, at least in JSPs), but it should be very similar in behavior. > JBoss Seam conversation propagation doesn't work when > STATE_SAVING_METHOD=client > -------------------------------------------------------------------------------- > > Key: ADFFACES-261 > URL: http://issues.apache.org/jira/browse/ADFFACES-261 > Project: MyFaces ADF-Faces > Issue Type: Bug > Environment: JBoss 4.0.4 GA, JBoss JEMS installer 1.2.0 beta, JBoss > Seam 1.0.1 GA, Facelets-1.1.11, Trinidad m1 snaphot revision 466296 > Reporter: Alexei Novikov > Priority: Minor > > Correct conversation handling in JBoss Seam requires that the method > saveSerializedView was called on a Seam's implementation of > javax.faces.application.StateManager. When Trinidad is installed in a > classpath along with JBoss Seam it blocks calls to Seam's StateManager if > STATE_SAVING_METHOD is set to "client". The following code does it: > class: org.apache.myfaces.trinidadinternal.application.StateManagerImpl > method: SerializedView saveSerializedView(FacesContext context) > 213 if (!isSavingStateInClient(context)) > 214 return _delegate.saveSerializedView(context); > Is that a right thing that the state management delegation depends on a state > saving configuration? It looks like a side effect and intrusive behavior. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
