Wildfly 8.1.0, JSPs and Java 8 syntax

[jessholle]

In Wildfly 8, when I try to specify:

<jsp-config source-vm="1.8" target-vm="1.8"/>

in the configuration, I get:

16:47:00,320 WARN  [org.apache.jasper.compiler] (default task-6) JBWEB005029: Unknown source JVM 1.8 ignored

16:47:00,321 WARN  [org.apache.jasper.compiler] (default task-6) JBWEB005030: Unknown target JVM 1.8 ignored

How can I use Java 8 syntax in JSPs in Wildfly 8.1.0???

--

Jess Holle

[jaysensharma]

There seems to be some issue related to "source-vm="1.8" target-vm="1.8"" mentioned as part of    [WFLY-4362] Web container (undertow) isn't able to compile JSPs containing JDK 8 specific code (lambda expressions) - JB…

I can see no such WARN in wildfly-9.0.0.Alpha2-SNAPSHOT.   Try with latest WildFly :    Downloads · WildFly

[ctomc]

Yes this problem was related to bug in ejc compiler and how jasper(jsp compiler) understands lambda.

You guys can grab WildFly 9 beta2 which should work quite well.

[jessholle]

Wildfly 9 beta is not an option.

I need this to work with Wildfly 8.1.0 or 8.2.0.  Moverover it doesn't seem like a bug in EJC or lambda understanding -- rather it would seem that no one tried to even make jsp-config recognize 1.8 as a valid source/target for JSP compilation.

Note that this has been working in Tomcat 8 for some time now -- via EJC and Jasper.

[ctomc]

Yes jasper compiler needed to learn java 8 support.

we backported commits need to make this work to jastow.

this ware the changes needed Comparing f2a0f1346cac771633248515883c0206808f7243...76943fa16a7c419c450993ad7b2ab771db731bfc · undertow-io/jastow · Git…

including the ECJ update to 4.4.x that is the version that added java8 syntax support

You can make it work on wildfly 8.2 by manually updating jastow to Maven Repository: io.undertow.jastow » jastow » 1.1.1.Final

and ecj to Maven Repository: org.eclipse.jdt.core.compiler » ecj » 4.4.2

[jessholle]

Thanks, dropping those updates in place and updating module.xml did the trick.