From adffaces-issues-return-2235-apmail-incubator-adffaces-issues-archive=incubator.apache.org@incubator.apache.org Fri Mar 16 08:43:37 2007 Return-Path: Delivered-To: apmail-incubator-adffaces-issues-archive@locus.apache.org Received: (qmail 46905 invoked from network); 16 Mar 2007 08:43:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Mar 2007 08:43:37 -0000 Received: (qmail 40684 invoked by uid 500); 16 Mar 2007 08:43:45 -0000 Delivered-To: apmail-incubator-adffaces-issues-archive@incubator.apache.org Received: (qmail 40664 invoked by uid 500); 16 Mar 2007 08:43:45 -0000 Mailing-List: contact adffaces-issues-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: adffaces-issues@incubator.apache.org Delivered-To: mailing list adffaces-issues@incubator.apache.org Received: (qmail 40655 invoked by uid 99); 16 Mar 2007 08:43:45 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2007 01:43:45 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2007 01:43:36 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E98A371412C for ; Fri, 16 Mar 2007 01:41:29 -0700 (PDT) Message-ID: <19679871.1174034489954.JavaMail.jira@brutus> Date: Fri, 16 Mar 2007 01:41:29 -0700 (PDT) From: =?utf-8?Q?Matthias_We=C3=9Fendorf_=28JIRA=29?= To: adffaces-issues@incubator.apache.org Subject: [jira] Updated: (ADFFACES-261) JBoss Seam conversation propagation doesn't work when STATE_SAVING_METHOD=client In-Reply-To: <17169347.1161874636554.JavaMail.root@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/ADFFACES-261?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias We=C3=9Fendorf updated ADFFACES-261: ---------------------------------------- Affects Version/s: 1.0.1-incubating-core-SNAPSHOT > JBoss Seam conversation propagation doesn't work when STATE_SAVING_METHOD= =3Dclient > -------------------------------------------------------------------------= ------- > > Key: ADFFACES-261 > URL: https://issues.apache.org/jira/browse/ADFFACES-261 > 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, JBo= ss 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 save= SerializedView was called on a Seam's implementation of javax.faces.applica= tion.StateManager. When Trinidad is installed in a classpath along with JBo= ss Seam it blocks calls to Seam's StateManager if STATE_SAVING_METHOD is s= et to "client". The following code does it: > class: org.apache.myfaces.trinidadinternal.application.StateManagerIm= pl > 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 s= tate saving configuration? It looks like a side effect and intrusive behavi= or. --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.