incubator-adffaces-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias We├čendorf (JIRA) <>
Subject [jira] Updated: (ADFFACES-261) JBoss Seam conversation propagation doesn't work when STATE_SAVING_METHOD=client
Date Fri, 16 Mar 2007 08:41:29 GMT


Matthias We├čendorf updated ADFFACES-261:

    Affects Version/s: 1.0.1-incubating-core-SNAPSHOT

> JBoss Seam conversation propagation doesn't work when STATE_SAVING_METHOD=client
> --------------------------------------------------------------------------------
>                 Key: ADFFACES-261
>                 URL:
>             Project: MyFaces ADF-Faces
>          Issue Type: Bug
>    Affects Versions: 1.0.1-incubating-core-SNAPSHOT
>         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.
You can reply to this email to add a comment to the issue online.

View raw message