Wildfly 14.01 JSP EL not working with constants

[ptuomaal]

I have faced pretty similar bug that was in Wildfly 10 (Java EE 7 + EL 3.0 + Wildfly 10 - returns empty string on constant ). JSP constans are working with WLF 10.1 but not in WLF14/14.01. I created a simple test project for this: GitHub - elbitoy/jsptest

In the test project I have simple index.jsp file where I use some constants:

When I run the page for the first time things are getting weird. Only first custom constant is evaluated:

If I hit refresh for the page even the java.lang.* constants stop working

Has any others faced similar problem? I tried to look from known WLF bugs for the issue but could not find any. Currently this is preventing us for upgrading WLF from 10.1 to 14.01. I have not managed to create any workaround for the issue. Any help for this is more than welcome

-Petri

[jaikiran]

There have been some issues in 14.0.x related to EL which have been fixed post 14.x release. Issues like:

[WFLY-11065] Usage of static fields from java.lang classes as EL expressions in JSPs doesn't work for servlet 4.0 - JBos…

[WFLY-11095] Wildfly 14.0.0 regression: EL returns empty string on constant - JBoss Issue Tracker

Is it possible for you to try the latest nightly build from here https://ci.wildfly.org/viewType.html?buildTypeId=WF_Nightly  and see if its fixed there?

[ptuomaal]

I got mixed results with the nightly build. If my web.xml version is 3.1 then the snapshot actually works worse because it does not even evalueta Boolean.TRUE/Integer.MAX values. However if I change web.xml version to 4.0 constants works fine.

In Wildfly 14 there is no difference between web.xml version 3.1 or 4.0. At least on my tests.

WLF 15 snapshot with web.xml 3.1

WLF 15 snapshot with web.xml 4.0

WLF 14.01 with web.xml 4.0

[jaikiran]

Are you certain that on that nightly version, the 3.1 web.xml version is causing that (blank) output? I just gave your repo a try with the latest (locally) built WildFly upstream and it works all fine:

START

A:true

B:2147483647

C:TEST1

D:TEST2

END

I did a minor but irrelevant to this test change, in your repo's index.jsp and used:

Servlet Version: <%= application.getEffectiveMajorVersion() %>.<%= application.getEffectiveMinorVersion() %>

to print the major/minor servlet version of the _application_ but like I say, that doesn't play a role in the rest of the output.

[ptuomaal]

you are right, the web.xml with 3.1 is also working with nightly build. Maybe I typed 3.0 instead of 3.1 for my initial try.

Thanks for your help with this. We will refactor our code away from using static fields in JSP as it looks like we need to proceed with the WLF14