Subj : Re: static method signature matching issues in Rhino & JUnit
To   : netscape.public.mozilla.jseng
From : mohaks
Date : Thu Aug 18 2005 04:42 pm

Thanks for the reply.

Looking at the LC3 spec, it would appear that in this case the "string"
to java.lang.String conversion ought to be preferred over the
conversion to java.lang.Object.  So, I don't think it's a case of LC3
mandated ambiguity.

Also, I really do think that this issue is caused by the updates
between 1.5.2 and 1.5.3 related to resolving method ambiguity.  I
checked our JUnit version and it doesn't appear that anything has
changed there that would have introduced this ambiguity.  Regardless,
as you mention, it does appear to be a real issue with the Rhino method
selector.

thanks again,
mohak

.