|DynamicImport-Package question while patching DataNucleus for OSGi [message #730566]
||Wed, 28 September 2011 16:04
| Matthew T. Adams
Registered: July 2009
Location: Austin, TX
I'm in the process of patching DataNucleus to build better OSGi jars. As such, I've got its POMs configured to use maven-bundle-plugin and I have one question, which is one of practicality versus correctness:|
What are the ramifications if I add "DynamicImport-Package: *" just in case there are package dependencies that aren't caught by maven-bundle-plugin?
As I understand it, OSGi class loader(s) will search packages statically declared in Import-Package, and only if not found, will begin searching in packages according to DynamicImport-Package. This seems reasonable given that transparent persistence (ORM) products might need to instantiate not only persistable user classes, but also compile- or run-time generated query classes (like criteria/query classes), as well as product-specific plugins that the product might go looking for.
Any practical advice is appreciated. Unless I hear otherwise, I'm going to add it, if only to make the experience better for the end user.
Powered by FUDForum
. Page generated in 0.01839 seconds