EAP 7's EL equals operations work differently from EAP 6 one.
For example: put the following JSP in your web application (e.g. example.war)
Then, access the above JSP with curl command:
- Expected result (EAP 6's behavior):
- Actual result (EAP 7's behavior):
In the section 1.9.2 of EL 3.0 Specification, the ==,!= operators have the following step:
Note that the step "If A or B is Byte, Short, Character, Integer, or Long coerce both A and B to Long, apply operator" should happen earlier than the step coercion to String. So, it appears that EAP 7's behavior violates the spec.