Well, I don't know if I'd consider that the most frequent use case, but it could be on the search path for sure! :-) That's a pretty cool idea, by the way.
-----Original Message----- From: Pablo Lalloni [mailto:[EMAIL PROTECTED] Sent: Monday, July 31, 2006 9:47 AM To: dev@hivemind.apache.org Cc: James Carman Subject: Re: New convention? El Lunes, 31 de Julio de 2006 07:49, James Carman escribió: > Yes, *Impl in the same package might even be the first place it looks. > Then look for an *Impl in the impl subpackage. I normally use the latter > setup, but many folks do just put the implementation classes in the same > package as their interface. I'd like to make HiveMind very simple to > configure with minimal effort. That's why we offer the option to use > "convention over configuration." In cases when there will be just a single impl or a "default" one for a given service we just make it a static inner class of the service interface. public interface SomeService { ... public static class Default implements SomeService { ... } } So if the impl "search path" includes this idiom, it would be great for us as this is definitely the most frequent case here. -- Pablo
