Split packages are bad. Don't do it! Interfaces in one package, implementation in another. --
BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788 From: Tom Kesling <[email protected]> To: OSGi Developer Mail List <[email protected]> Date: 2010/05/06 08:42 Subject: [osgi-dev] What are best practices for split packages across mutiple bundles Sent by: [email protected] 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? 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
