https://issues.apache.org/bugzilla/show_bug.cgi?id=52970
--- Comment #3 from Konstantin Kolinko <knst.koli...@gmail.com> 2012-03-22 14:25:10 UTC --- There is nothing in your stacktrace that comes from Tomcat EL implementation. There should be other "Caused by" somewhere further. Looking at method selection code in javax.el.BeanELResolver#invoke(..) - The "paramTypes" argument there is usually null. In that case the method is identified by the count of parameters, not by their types. If that were the case, type coercion will happen later and would not result in MethodNotFoundException. So where is it thrown from? - If the "paramTypes" argument is not-null then it will be used to select exact method. Is it your case? The requirements for BeanELResolver#invoke() API are set in EL 2.2 specification (see 2.2.9, page 38). I see no provision to respect EL coercion rules when paramTypes != null. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
