[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1903) Facelets EL functions do not work

Facelets EL functions do not work --------------------------------- Key: JBSEAM-1903 URL: http://jira.jboss.com/jira/browse/JBSEAM-1903 Project: JBoss Seam Issue Type: Bug Components: EL, JSF Affects Versions: 1.2.1.GA Environment: Linux 2.6.20-16-generic (i386) JBoss AS 4.2.0.GA JSF 1.2 (Sun) 1.2_04 Facelets 1.1.12 Ajax4jsf 1.1.1 Richfaces 3.0.1 Reporter: Martin Kouba Facelets EL functions do not work after form submit (both normal and ajax). It is certainly classloading problem - org.apache.el tries to load EL function impl. class but there is no appropriate classloader. I studied JBoss classloading model and probed various configurations - without result. 10:22:56,291 ERROR [STDERR] java.lang.ClassNotFoundException: No ClassLoaders found for: cz.mydomain.CoreELFunctions 10:22:56,293 ERROR [STDERR] at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212) 10:22:56,293 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:514) 10:22:56,293 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408) 10:22:56,293 ERROR [STDERR] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) 10:22:56,293 ERROR [STDERR] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) 10:22:56,293 ERROR [STDERR] at java.lang.Class.forName0(Native Method) 10:22:56,293 ERROR [STDERR] at java.lang.Class.forName(Class.java:164) 10:22:56,293 ERROR [STDERR] at org.apache.el.lang.FunctionMapperImpl$Function.getMethod(FunctionMapperImpl.java:147) 10:22:56,294 ERROR [STDERR] at org.apache.el.lang.FunctionMapperImpl.resolveFunction(FunctionMapperImpl.java:53) 10:22:56,294 ERROR [STDERR] at org.apache.el.parser.AstFunction.getValue(AstFunction.java:71) 10:22:56,294 ERROR [STDERR] at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) 10:22:56,294 ERROR [STDERR] at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71) It is somehow related to bug JBSEAM-1179. However this bug does not offer any solution.