Bug 793691 (JBEPP-767)

Summary: PBR-224: PBR-223 javax.faces.ViewState returns the same value for each portlets on one portal page using "client" state saving. PBR-200 Serializable PortalIdentity$JBossLoginDelegate holds reference to non-Serializable WebAuthentication object.
Product: [JBoss] JBoss Enterprise Portal Platform 4 Reporter: Gary Hu <garyhu2>
Component: unspecifiedAssignee: Jboss Support <support-patch>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3.0.GA_CP5CC: epp-bugs, garyhu2, prabhat.jha
Target Milestone: ---   
Target Release: 4.3.0.GA_CP5   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-767
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-10 10:05:18 UTC Type: Support Patch
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
portletbridge-api-2.0.0.FINAL.EPP43CP05.PBR224.jar
none
portletbridge-impl-2.0.0.FINAL.EPP43CP05.PBR224.jar none

Description Gary Hu 2011-01-04 21:08:42 UTC
Patch Instructions: PATCH NAME:
        JBEPP-767
PRODUCT NAME:
        JBoss Enterprise Portal Platform (EPP)
VERSION:
        5.1
SHORT DESCRIPTION:
       javax.faces.ViewState returns wrong value when using "client" state saving. Serializable PortalIdentity$JBossLoginDelegate holds reference to non-Serializable WebAuthentication object.
LONG DESCRIPTION:
       javax.faces.ViewState returns wrong value when using "client" state saving. Serializable PortalIdentity$JBossLoginDelegate holds reference to non-Serializable WebAuthentication object.
MANUAL INSTALL INSTRUCTIONS:
       Replace portletbridge-impl.jar and portletbridge-api.jar in the application's deployment archive with the version contained in this patch distribution.
       Make sure to use Richfaces 3.3.1.SP2 and seam jars shipped by EPP 4.3-CP05.
       For the PBR-223, additional configuration is required to fix the issue. There are two options for the configuration:
       1) add the following to the portlet.xml
        <init-param>
                <name>javax.portlet.faces.excludedRequestAttributes</name>
                <value>com.sun.faces.*<value>
        </init-param> 
        2) add the following to the faces-config.xml
        <application 
           <application-extension>
            <bridge:excluded-attributes>  
                <bridge:excluded-attribute>com.sun.faces.*</bridge:excluded-attribute>
            </bridge:excluded-attributes>
          </application-extension>
        </application>
COMPATIBILITY:
        N/A
DEPENDENCIES:
        N/A
SUPERSEDES:
        N/A
SUPERSEDED BY:
        JBoss EPP 5.1
CREATOR:
        Gary Hu
DATE:
        2011/01/04 
Patch Repository Link: https://support.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=5193
SVN / CVS Isolated Branch: http://svn.jboss.org/repos/portletbridge/tags/2.0.0.FINAL.EPP43CP05.PBR224/
Support Case Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000004StwsIAC&sfdc.override=1
project_key: JBEPP

Comment 1 Gary Hu 2011-01-04 21:19:04 UTC
Patch Instructions: Added: PATCH NAME:
        JBEPP-767
PRODUCT NAME:
        JBoss Enterprise Portal Platform (EPP)
VERSION:
        5.1
SHORT DESCRIPTION:
       Richfaces component rich:fileUpload doesn't work in portletbridge 2.1.0.GA.EPP51
LONG DESCRIPTION:
       Richfaces component rich:fileUpload doesn't work in portletbridge 2.1.0.GA.EPP51. The upload listener doesn't get invoked.
MANUAL INSTALL INSTRUCTIONS:
       Replace portletbridge-impl.jar and portletbridge-api.jar in the application's deployment archive with the version contained in this patch distribution.
       Make sure to use Richfaces 3.3.1.SP2 and seam jars shipped by EPP 4.3-CP05.
       For the PBR-223, additional configuration is required to fix the issue. There are two options for the configuration:
       1) add the following to the portlet.xml
        <init-param>
                <name>javax.portlet.faces.excludedRequestAttributes</name>
                <value>com.sun.faces.*<value>
        </init-param> 
        2) add the following to the faces-config.xml
        <application 
           <application-extension>
            <bridge:excluded-attributes>  
                <bridge:excluded-attribute>com.sun.faces.*</bridge:excluded-attribute>
            </bridge:excluded-attributes>
          </application-extension>
        </application>
COMPATIBILITY:
        N/A
DEPENDENCIES:
        N/A
SUPERSEDES:
        N/A
SUPERSEDED BY:
        JBoss EPP 5.1
CREATOR:
        Gary Hu
DATE:
        2011/01/04 


Comment 2 Gary Hu 2011-01-04 21:20:02 UTC
Attachment: Added: portletbridge-api-2.0.0.FINAL.EPP43CP05.PBR224.jar
Attachment: Added: portletbridge-impl-2.0.0.FINAL.EPP43CP05.PBR224.jar


Comment 3 Gary Hu 2011-01-04 21:24:21 UTC
Patch Instructions: Removed: PATCH NAME:
        JBEPP-767
PRODUCT NAME:
        JBoss Enterprise Portal Platform (EPP)
VERSION:
        5.1
SHORT DESCRIPTION:
       Richfaces component rich:fileUpload doesn't work in portletbridge 2.1.0.GA.EPP51
LONG DESCRIPTION:
       Richfaces component rich:fileUpload doesn't work in portletbridge 2.1.0.GA.EPP51. The upload listener doesn't get invoked.
MANUAL INSTALL INSTRUCTIONS:
       Replace portletbridge-impl.jar and portletbridge-api.jar in the application's deployment archive with the version contained in this patch distribution.
       Make sure to use Richfaces 3.3.1.SP2 and seam jars shipped by EPP 4.3-CP05.
       For the PBR-223, additional configuration is required to fix the issue. There are two options for the configuration:
       1) add the following to the portlet.xml
        <init-param>
                <name>javax.portlet.faces.excludedRequestAttributes</name>
                <value>com.sun.faces.*<value>
        </init-param> 
        2) add the following to the faces-config.xml
        <application 
           <application-extension>
            <bridge:excluded-attributes>  
                <bridge:excluded-attribute>com.sun.faces.*</bridge:excluded-attribute>
            </bridge:excluded-attributes>
          </application-extension>
        </application>
COMPATIBILITY:
        N/A
DEPENDENCIES:
        N/A
SUPERSEDES:
        N/A
SUPERSEDED BY:
        JBoss EPP 5.1
CREATOR:
        Gary Hu
DATE:
        2011/01/04  Added: PATCH NAME:
        JBEPP-767
PRODUCT NAME:
        JBoss Enterprise Portal Platform (EPP)
VERSION:
        5.1
SHORT DESCRIPTION:
       javax.faces.ViewState returns wrong value when using "client" state saving. Serializable PortalIdentity$JBossLoginDelegate holds reference to non-Serializable WebAuthentication object.
LONG DESCRIPTION:
       javax.faces.ViewState returns wrong value when using "client" state saving. Serializable PortalIdentity$JBossLoginDelegate holds reference to non-Serializable WebAuthentication object.
MANUAL INSTALL INSTRUCTIONS:
       Replace portletbridge-impl.jar and portletbridge-api.jar in the application's deployment archive with the version contained in this patch distribution.
       Make sure to use Richfaces 3.3.1.SP2 and seam jars shipped by EPP 4.3-CP05.
       For the PBR-223, additional configuration is required to fix the issue. There are two options for the configuration:
       1) add the following to the portlet.xml
        <init-param>
                <name>javax.portlet.faces.excludedRequestAttributes</name>
                <value>com.sun.faces.*<value>
        </init-param> 
        2) add the following to the faces-config.xml
        <application 
           <application-extension>
            <bridge:excluded-attributes>  
                <bridge:excluded-attribute>com.sun.faces.*</bridge:excluded-attribute>
            </bridge:excluded-attributes>
          </application-extension>
        </application>
COMPATIBILITY:
        N/A
DEPENDENCIES:
        N/A
SUPERSEDES:
        N/A
SUPERSEDED BY:
        JBoss EPP 5.1
CREATOR:
        Gary Hu
DATE:
        2011/01/04 


Comment 4 Prabhat Jha 2011-01-04 21:28:20 UTC
All testing has been done at https://issues.jboss.org/browse/JBQA-4043. This jira is simply to follow the standard patch process.

Comment 5 Gary Hu 2011-01-04 21:29:26 UTC
ghu@ghu-rh:~/downloads/jboss/portal/jboss-epp-4.3$ md5sum portletbridge-api-2.0.0.FINAL.EPP43CP05.PBR224.jar 
f4714fe14120c0cc2555c9f874b4648d  portletbridge-api-2.0.0.FINAL.EPP43CP05.PBR224.jar
ghu@ghu-rh:~/downloads/jboss/portal/jboss-epp-4.3$ md5sum portletbridge-impl-2.0.0.FINAL.EPP43CP05.PBR224.jar 
c5f6cd408b2680cd68706544449cd6f3  portletbridge-impl-2.0.0.FINAL.EPP43CP05.PBR224.jar


Comment 6 Tushar Gandotra 2011-01-10 10:05:18 UTC
The patch is available for download from the following location:
https://support.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=5193

Comment 7 Tushar Gandotra 2011-01-10 10:05:18 UTC
Patch Repository Link: Added: https://support.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=5193