https://issues.apache.org/bugzilla/show_bug.cgi?id=56425
lafleche <lafle...@amazon.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Version|7.0.53 |7.0.55
Resolution|FIXED |---
--- Comment #3 from lafleche <lafle...@amazon.com> ---
Can I see the commit where this bug was fixed?
I ran into this bug when upgrading from 7.0.50 to 7.0.55.
I was looking at the latest code for BeanELResolver.java and Util.java.
At a glance, it looks like:
getWrapper() does a bunch of fancy things including type coercion
getMethod() only looks for a perfect match.
I don't see BeanELResolver calling getWrapper() anywhere, only getMethod().
This matches the behaviour I'm seeing, where I get MethodNotFoundExceptions
forr mappings like:
doFoo(Integer bar) -> doFoo(int bar)
--
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
