Closed volosied closed 2 years ago
The method mapping was updating for EL 5.0 as part of #159. Once the implementation is updated for #159 (I haven't seen any activity from the Glassfish team along those lines) this issue should be addressed.
Done from an API perspective. See https://github.com/eclipse-ee4j/expressly/issues/3 to track the implementation in GlassFish.
I encountered the following exception when testing the code below on Wildfly 24."
Tomcat had updated their varargs handling in BZ 65358, and I'm wondering if this API could have something similar applied?
However, I understand this might also be due to vagueness in the spec? Enum could be coerce to a string? I appreciate any assistance. Thanks!
EL Expression:
${testBean.testMethod(testBean.getLevel(), testBean.getLevel(), testBean.getLevel())}