On Monday 30 January 2006 04:58, Jeff McAffer wrote: > At the risk of exposing some religion...
:o) > There seems to be quite a bit of debate on where to put API packages > relative to their implementation(s). The current one on hand for us is > the javax.servlet API and the HTTP service implemenation. (see > https://bugs.eclipse.org/bugs/show_bug.cgi?id=121585 if you want the gory > details). My personal view is that each bundle should be resolvable and startable by its own merit. Which means the API jar needs to be both in the client and the provider bundle, and OSGi will load those from whoever is launched first. However, I am not totally familiar with the classloading resoluton in OSGi yet, and there are probably strong arguments against this. The alternative is "API bundles", and then the question is how those are to be organized. Having the API in the service provider bundle is IMHO only suitable if the API and impl are so tight that other implementations are not to be expected. Cheers Niclas _______________________________________________ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
