On Oct 16, 2007, at 15:48 , Richard S. Hall wrote:
- Should I package each interface class in a separate bundle
and install them in the framework before consumers and providers
are resolved ? The risk is to end up with a great number
of bundles (may be not very efficient to have one class loader
per service interface).
This would be okay.
Alternatively, depending on your application, you might also be able
to bundle a set of related interfaces into a single bundle. From past
experiences, I have seen many cases where a whole set of domain
interfaces exist which are basically the contracts that everybody
needs to respect.
- Any other solutions ?
I, personally, would have each service provider embed the service
interface package and then import/export it. If your service
interface packages are small, then this should not add much overhead.
I agree with Richard here, either you embed the service interfaces in
the provider bundles, or you make them available separately (possibly
grouping interfaces as suggested above). Also, you might find that
during development, a different strategy might be convenient than
when deploying the application (but in general, it's best to keep
those the same).
Greetings, Marcel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
