You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
Caused by: javax.el.MethodNotFoundException: Unable to find unambiguous method: class com.test.TestBean.testMethod(com.test.Level, com.test.Level, com.test.Level)
at javax.el.ELUtil.findMostSpecificWrapper(ELUtil.java:407)
at javax.el.ELUtil.findWrapper(ELUtil.java:376)
at javax.el.ELUtil.findMethod(ELUtil.java:271)
at javax.el.ELUtil.findMethod(ELUtil.java:230)
at javax.el.BeanELResolver.invoke(BeanELResolver.java:327)
at org.apache.jasper.el.JasperELResolver.invoke(JasperELResolver.java:147)
public enum Level {
LOW (1);
private final int levelCode;
private Level(int levelCode) {
this.levelCode = levelCode;
}
}
public class TestBean {
public Level getLevel() {
return Level.LOW;
}
public String testMethod(Level level1, Level... level2) {
return "(Level level1, Level... level2)";
}
public String testMethod(String param1, Level... level2) {
return "(String param1, Level... level2)";
}
}
EL Expression: ${testBean.testMethod(testBean.getLevel(), testBean.getLevel(), testBean.getLevel())}
The text was updated successfully, but these errors were encountered:
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.
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())}
The text was updated successfully, but these errors were encountered: