[ http://issues.apache.org/jira/browse/VELOCITY-132?page=comments#action_12432616 ] Nathan Bubna commented on VELOCITY-132: ---------------------------------------
Llewellyn, were you able to update your patch to fully fix this? > IllegalArgumentException while calling an overloaded method > ----------------------------------------------------------- > > Key: VELOCITY-132 > URL: http://issues.apache.org/jira/browse/VELOCITY-132 > Project: Velocity > Issue Type: Bug > Components: Source > Affects Versions: 1.3-rc1 > Environment: Operating System: All > Platform: All > Reporter: MySign > Fix For: 1.5 > > Attachments: includecall.vm, velocity_patch.patch, velocitybug.vm, > VelocityCachingBug.java > > > If there are two methods with the same name and different parameters like: > public class myClass > { > public String foo ( Integer intObj ); > public String foo ( String str ); > } > and a velocity template like this > $myObj.foo( $someObj.getNull() ) > $myObj.foo( $str ) > while $someObj.getNull() returns null and $str is a java.lang.String object > with a String like 'test'. Because velocity caches the first method with the > Integer argument on calling with the parameter null (which isn't of course of > any type/class) the call fails with the String argument, because velocity > tries > to call the foo( Integer intObj )! > In the velocity log appears a IllegalArgumentException which is right, but > velocity should call the right method! > mike -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
