Closed glassfishrobot closed 12 years ago
@glassfishrobot Commented Reported by kchung
@glassfishrobot Commented wrschneider99 said: Is this the same as the one I opened here?
@glassfishrobot Commented kchung said: Fixed in release 2.2.2.
http://search.maven.org/#browse|-1545957111
@glassfishrobot Commented This issue was imported from java.net JIRA UEL-19
@glassfishrobot Commented Marked as fixed on Thursday, October 13th 2011, 10:35:47 am
From Martin KoÄ�Ã:
EL 2.2 introduces method invocation but if you try use it like rendered="#
{bean.getRendered(param)}
" there is an unpleasant surprise: both implementations of BeanELResolver (Glassfish, Tomcat) use this construction during method invocation:
ExpressionFactory exprFactory = ExpressionFactory.newInstance();
That newInstance() always involves FactoryFinder mechanism, callstack then looks like :
org.apache.catalina.loader.WebappClassLoader.findResourceInternal org.apache.catalina.loader.WebappClassLoader.findResource org.apache.catalina.loader.WebappClassLoader.getResourceAsStream javax.el.FactoryFinder.find(String, String, Properties) javax.el.ExpressionFactory.newInstance(Properties) javax.el.ExpressionFactory.newInstance() javax.el.BeanELResolver.invokeMethod(Method, Object, Object[])
Always tries to locale factory implementation, that means /META-INF/services reading! This is not problem in myfaces, but users don't distinguish between JSF and EL well.
Environment
Operating System: All Platform: All
Affected Versions
[current]