[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-79.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.0.0
Modified code so the ELContext sets a bit after the bridge determines in is
contextCreated listener whether the rfeceived context is JSF or JSP (difference
is whether the context is an isntanceof the Portlet(Bridge)ELContext. The
resolvers getValue() now uses this context to determine which context its
running in. When in JSP it delgates processing any portlet defined objects
while handling them in the JSF context.
> Bridge's ELReoslver should resolve JSP EL differently than JSF EL
> -----------------------------------------------------------------
>
> Key: PORTLETBRIDGE-79
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-79
> 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
>
>
> Currently the bridge has a single ELResolver that does the same thing whether
> resolving in a JSP or JSF expression. However, the bridge's EL resolver is
> designed to do 2 things: expose portlet defined objects already accessible
> in JSP EL in a JSF EL and expose new variables (not defined by spec) in both
> environments. This means the impl should distinguish between whether its
> doign a JSF or JSP EL and in the case of a JSP EL it should evaluate the
> portlet defined objects -- rather it should defer these to the JSP builtin
> resolver.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
