Warning for potential parameter matching issues

[jaikiran]

Just recently a user found an issue with the AS 5.1.0 GA http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156075

The issue is similar to what has been discussed sometimes earlier
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=92698

http://lists.jboss.org/pipermail/jboss-development/2009-April/014085.html

As discussed in those posts, its not possible to correctly figure out the constructor/method that is to be used. But i believe, its possible to write out a meaningful WARN message warning developers of a potential issue with the configuration because of the presence of multiple constructors/method that are a possible match. The issue in AS 5.1.0 GA could have been caught earlier had there been such a WARN message. In the previous forum discussion there was a task which talked about adding this WARN message https://jira.jboss.org/jira/browse/JBMICROCONT-40. The issue is actually resolved, but there are no WARN messages generated for the faulty configurations. Maybe something more has to be done?

[dmlloyd]

Maybe an error would be a better idea - that way Hudson would catch this well before a release?

[jaikiran]

Maybe an error would be a better idea - that way Hudson would catch this well before a release?

I thought about the error option too. But i guess it would break backward compatibility. Assuming we need backward compatibility for this :)

[alesj]

If we're about to check all possible matches due to missing info,
I would then suggest we use a better mechanism/structure as just plain iteration + matching.

What that exactly is one would need to check some theory,
but this is what I would like at the end:

MatchingMechanism m = ...;
CtorInfo ctor = m.findCtor(paramTypes, failIfNoMatch, failIfMultiple);

Where this would account for everything, e.g. possible progression, ...