I've done some looking around for some best practice guidelines. Can't find anything other than speaking to standard software methodologies. Not really clear examples.
Anyhow, I have two questions about how people do things. 1. Is it a good idea to separate Interfaces and Implementations into separate bundles. In my case there are a number of possible implementations for certain service interfaces that may come along in time within my development group. If I include the Interface in my first implementation bundle then new implementations of that interface will either have to have a dependency to my first implementation or be included together with the other implementation. Neither of these seem like good ideas. So my thinking is to create a number of small bundles that include only the interface, or one bundle with all the interfaces. However, one of the best practices I did find said something about not creating huge dependency trees. 2. What do people do to set up unit tests for their services? JUnit? I started going down the track of creating a test interface that could be queried by a 'testing service'. It would look for all implementations of that testing interface and run all the tests. It then occurred to me that there's got to be something out there that already does something like this. Of course the problem with this way of looking at things is that only the exposed (exported) services/packages could be tested. Thoughts? _________________________ Joel Schuster The NAVSYS Corporation 14960 Woodcarver Road Colorado Springs, CO 80921 719-481-4877 ext. 138
