Hi, On 06.05.2010 13:34, Tom Kesling wrote: > I'm trying to understand the rules/best practices for working with > split packages. > > I have a bundle that depends on a package that exists in two separate bundles. > The package in one bundle contains interfaces and the package in the > other bundle contains implementation of those interfaces. > > Is this a bad pattern to follow? > Will this create class loader issues? > Should split packages be avoided?
IMHO split packages are to be avoided. Not only do they generate problems for the framework but also for maintenance: You always have to find the source for problems etc. It may be good to split API and implementation into separate bundles, but then I would also place them into distinct packages. Maybe you don't even want to export the implementation packages but make the implementations available as services .... Regards Felix > > Any advice/best practices would be appreciated. > > Thanks, > T > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
