myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "DK (JIRA)" <...@myfaces.apache.org>
Subject [jira] Created: (PORTLETBRIDGE-127) FacesContext.getCurrentInstance().getExternalContext().getSessionMap().remove() does not seem to work wth the bridge
Date Tue, 02 Mar 2010 20:25:27 GMT
 FacesContext.getCurrentInstance().getExternalContext().getSessionMap().remove() does not seem
to work wth the bridge
---------------------------------------------------------------------------------------------------------------------

                 Key: PORTLETBRIDGE-127
                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-127
             Project: MyFaces Portlet Bridge
          Issue Type: Bug
    Affects Versions: 1.0.0-beta
         Environment: WebSphere Portal 6.1.5 running on Windows XP Pro
MyFaces Portal Bridge 1.0.0.beta2
            Reporter: DK


I've been working on a POC application with PrimeFaces, deploying as a web app first, and
then portalizing it and deploying to WebSphere Portal.

When deployed as a web app, the following method removing JSF managed bean worked fine:

    public static void discardManagedObject(String objName) {
        FacesContext.getCurrentInstance().getExternalContext().getSessionMap().remove(objName);
    }

It also seemed to work on the previous iteration of this app with IBM JWL Portlet Bridge 3.1.3.

When deployed as a portlet with MyFaces Bridge 1.0.0.beta2, this does not seem to work anymore
and the logic in code had to be changed as a workaround.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message