When it sees an other-wise unset, writable property that is an interface, it assumes the proeprty should be wired to a service.
It searches for a service that implements that exact service. If exactly one is found, then success. If zero or more than one, then error. Generally, you can only rely on autowire within your module, using interfaces you define. Otherwise, an upgrade may result in an additional service implenting the interface and you'll start getting errors. For sanities sake, the hivemind and hivemind.lib modules do not take advantage of autowiring. Someboyd may put another implementation of org.apache.hivemind.service.ClassFactory or something, someday. However, in my expereience, where autowiring makes sense, it works just fine. I'm thinking of adding an additional autowiring logic, to wire a List property to a configuration with the same id as the service. On Thu, 5 Aug 2004 14:11:21 -0400, James Carman <[EMAIL PROTECTED]> wrote: > It appears that HiveMind will not only auto-wire the documented, specific > services to an object using the BuilderFactory. It seems to also auto-wire > ANY service which it knows about. Is this actually intended? I am curious, > because I'd like to tell folks in my article that they can rely on > BuilderFactory to auto-wire their own services together and not just > auto-wire the "known" service types. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
