[jira] Created: (PORTLETBRIDGE-83) JSP sessionScope ELResolution fails for ManagedBeans (at sessionScope)

[My Faces - Dev mailing list]

JSP sessionScope ELResolution fails for ManagedBeans (at sessionScope)
----------------------------------------------------------------------

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


When running in the bridge (portlet container) the JSP session and the FacesContext session refer to different scopes.  The former is the application (http) session while the later is the portlet session.  When evaluating a JSP expression of a session scoped managed bean the managed bean resolver recognizes/acknowledges the reference but defers to the JSP implict resolver to actually find it/resolve it from the session.   Since the manage bean resolver check is at portlet scope and the JSP resolver check is at http/application scope -- we end up getting an error.  Fix is to have the bridge's EL resolver check in the portlet session for any properties it fails to resolve.

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

[My Faces - Dev mailing list]

     [ https://issues.apache.org/jira/browse/PORTLETBRIDGE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Freedman resolved PORTLETBRIDGE-83.
-------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.0.0

Fixes are self explanatory in the bug description.

> JSP sessionScope ELResolution fails for ManagedBeans (at sessionScope)
> ----------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-83
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-83
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: Impl
>    Affects Versions: 1.0.0-beta, 2.0.0-alpha
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 1.0.0, 2.0.0
>
>
> When running in the bridge (portlet container) the JSP session and the FacesContext session refer to different scopes.  The former is the application (http) session while the later is the portlet session.  When evaluating a JSP expression of a session scoped managed bean the managed bean resolver recognizes/acknowledges the reference but defers to the JSP implict resolver to actually find it/resolve it from the session.   Since the manage bean resolver check is at portlet scope and the JSP resolver check is at http/application scope -- we end up getting an error.  Fix is to have the bridge's EL resolver check in the portlet session for any properties it fails to resolve.

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