JWS 3 Tomcat 7 does work with JDK8, EWS 2.1.1 Tomcat 7 contains the older ECJ, so it doesn't compile _any_ JSPs on JDK 8. Note: JDK 8 _is not_ a supported platform for EWS 2: https://access.redhat.com/articles/258223 Question: Is it O.K. to have this old ECJ in EWS 2.1.1 then? If you find it cool and expected, feel free to close the bugzilla.
> Question: Is it O.K. to have this old ECJ in EWS 2.1.1 then? While I don't really want to say it's OK, I think that it has to be unless you consider it a blocker for the release so that we can get EWS 2.1.1 out the door. I say that because the problem didn't just come up overnight; java8 has only been partially supported by ECJ since EWS 2.x was released and has also affected rhel-6 tomcat6 forever (see https://bugzilla.redhat.com/show_bug.cgi?id=1223609). Users can precompile their JSPs to workaround the issue and while that is a pain, JSP compilation is the only thing that doesn't work as far as I know with java8. Another thing though is that the latest release of java8 on RHEL completely breaks this; some previous versions worked, but with the 101+ build (iirc) it doesn't work at all. Maybe a java8 downgrade could also temporarily work around the issue until they're able to upgrade to JWS 3? I don't want to be the end-all say on this, but it's a -1 vote from me.
Coty, Remy, thanks for the feedback. Based on what you said, I'm giving nack (-) to my own bug report with the conclusion that any JDK8 related issue is out of EWS 2 scope and requires upgrading to JWS 3 Tomcat 7 or 8. If anyone feels differently, please, comment or reopen. -K-