Hi Tom, I think your bundle should just work by exporting the package which contains the interfaces. Why do you need the other one? If you export these interfaces in your Manifest.MF you will be able to implement your application without depending on the implementation of these interfaces, in this way if the implementatation change, you could continue using your application since the exported interfaces did not change. If you want to use this interfaces you should get a service which implement these interfaces, but that is transparent to you, since you would be getting the service though a interface name, not the implementation one.
I hope this can help you Regards David -----Mensaje original----- De: [email protected] [mailto:[email protected]] En nombre de Tom Kesling Enviado el: jueves, 06 de mayo de 2010 14:34 Para: OSGi Developer Mail List Asunto: [osgi-dev] What are best practices for split packages across mutiple bundles 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
