[
https://issues.apache.org/jira/browse/MYFACES-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul McMahan resolved MYFACES-1593.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
Assignee: Paul McMahan
> javax.el.CompositeELResolver cannot resolve managed beans
> ---------------------------------------------------------
>
> Key: MYFACES-1593
> URL: https://issues.apache.org/jira/browse/MYFACES-1593
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-252
> Affects Versions: 1.2.0-SNAPSHOT
> Reporter: Paul McMahan
> Assigned To: Paul McMahan
> Fix For: 1.2.0-SNAPSHOT
>
>
> With a managed bean defined in faces-config.xml like this:
> <managed-bean>
> <managed-bean-name>
> mybean
> </managed-bean-name>
> <managed-bean-class>
> MyBean
> </managed-bean-class>
> <managed-bean-scope>
> request
> </managed-bean-scope>
> </managed-bean>
> FacesCompositeResolver can resolve the bean but javax.el.CompositeELResolver
> cannot. It does not insulate the ManagedBeanResolver with the code in
> VariableResolverToELResolver that sets the propertyResolved flag back to
> false after ManagedBeanResolver returns null and relies on
> ScopedAttributeResolver to return it from the proper scope later.
> For example, this code will fail to resolve the managed bean:
> PageContext context = JspFactory.getDefaultFactory().getPageContext( ... );
> ELResolver resolver = context.getELResolver(); // jasper returns a
> javax.el.CompositeELResolver
> MyBean mybean = resolver.getValue(context, null, "mybean"); // returns null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
