Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Date: Thu, 20 Oct 2011 21:13:10 +0000 (UTC)
From: "Michael Freedman (Created) (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Message-ID: 
 <1097807557.17752.1319145190950.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (PORTLETBRIDGE-221) Add explicit exclusions for
 trinidad in 329 branch
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Add explicit exclusions for trinidad in 329 branch 
---------------------------------------------------

                 Key: PORTLETBRIDGE-221
                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-221
             Project: MyFaces Portlet Bridge
          Issue Type: Bug
          Components: Impl
    Affects Versions: 2.0.0
            Reporter: Michael Freedman
            Assignee: Michael Freedman


We are running into problems with a user of the 329 branch codeline when using with extra Faces (componentkit) extensions.  The problem is the bridge is updating the bridge scope at the end of the render request pushing all new attributes created during the render into the scope.  These extensions are expecting this so numerous request scope attrs which are "flags" that something is initialized/done are inappropriately being carried forward and used causing malfunctions.  At the moment we don't want to just blanket reverse the code from saving the scope at the end of the render -- instead deciding the safest thing is to just exclude the specific packages that might exist.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira