[jboss-jira] [JBoss JIRA] (WFLY-3350) ELException when using { in string literal
Farah Juma (JIRA)
issues at jboss.org
Wed May 21 12:18:56 EDT 2014
[ https://issues.jboss.org/browse/WFLY-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969425#comment-12969425 ]
Farah Juma commented on WFLY-3350:
----------------------------------
It turns out that this is a known issue that was fixed in Mojarra 2.2.6:
https://java.net/jira/browse/JAVASERVERFACES-3135
Since Mojarra was upgraded from 2.2.5 to 2.2.6 in WildFly 8.1.0.CR1, I'm going to close this issue.
> ELException when using { in string literal
> ------------------------------------------
>
> Key: WFLY-3350
> URL: https://issues.jboss.org/browse/WFLY-3350
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF
> Affects Versions: 8.0.0.Final
> Environment: WildFly 8.0.0 Final
> Reporter: Bauke Scholtz
> Assignee: Farah Juma
>
> When using { in string literal in an EL expression in a Facelet like below
> {code}
> #{'blah blah {0} blah blah'}
> {code}
> WildFly 8.0.0 Final throws the following EL exception:
> {code}
> javax.el.ELException: EL Expression Unbalanced: ... #{'blah blah {0} blah blah'}
> at com.sun.faces.facelets.el.ELText.findVarLength(ELText.java:476)
> at com.sun.faces.facelets.el.ELText.parse(ELText.java:396)
> at com.sun.faces.facelets.el.ELText.parse(ELText.java:342)
> at com.sun.faces.facelets.compiler.TextUnit.flushTextBuffer(TextUnit.java:139)
> at com.sun.faces.facelets.compiler.TextUnit.flushBufferToConfig(TextUnit.java:257)
> at com.sun.faces.facelets.compiler.TextUnit.addChild(TextUnit.java:248)
> at com.sun.faces.facelets.compiler.CompilationManager.startUnit(CompilationManager.java:418)
> at com.sun.faces.facelets.compiler.CompilationManager.pushTag(CompilationManager.java:308)
> at com.sun.faces.facelets.compiler.SAXCompiler$CompilationHandler.startElement(SAXCompiler.java:266)
> ...
> {code}
> This EL construct has worked for ages in all other major servers such as JBoss AS, EAP, Tomcat, TomEE, GlassFish, WebSphere/Liberty, Geronimo, etc.
> We discovered this problem when testing all pages of OmniFaces Showcase (currently deployed to JBoss EAP 6.2 at OpenShift) on WildFly 8.0.0 Final. The following showcase page http://showcase.omnifaces.org/functions/Strings failed at WildFly with this exception.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
More information about the jboss-jira
mailing list