[ http://issues.apache.org/jira/browse/HIVEMIND-124?page=comments#action_65724 ] Richard Hensley commented on HIVEMIND-124: ------------------------------------------
When I use my hivemind from CVS with this patch to BuilderPropertyFacet, I get a very reasonable error messages that points me to the problem right away. The isAssignableToType() method seems to be used in the autowiring code quite a lot. After reviewing the code, I can't see that eating the ApplicationRuntimeException is a good thing. > Report a proper message when a constructor argument in BuilderFactory is > invalid > -------------------------------------------------------------------------------- > > Key: HIVEMIND-124 > URL: http://issues.apache.org/jira/browse/HIVEMIND-124 > Project: HiveMind > Type: Bug > Components: framework > Reporter: Richard Hensley > Attachments: patch.txt > > My situation is that I use constructor arguments for all my required > parameters of objects. The code inside of the BuilderFactoryLogic uses the > BuilderPropertyFactet.isAssignableFrom() method to figure out if a particular > parameter in a constructor is right. The > BuilderPropertyFactet.isAssignableFrom() eats an ApplicationRuntimeException > and returns false. This is bad when you miss-spell a service name, for > instance: > <service>service:MyServic</service> > When you meant, > <service>service:MyService</service> > The error that Hivemind throws is that it had trouble finding a valid > constructor, when the real problem was that it had problems finding your > service to even check if the constructor was valid. -- 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]
