|No DynamicImport-Package in Scoped Bundle? [message #663591]
||Tue, 05 April 2011 14:03
Registered: February 2011
I'm using Jabsorb to do JSON marshalling/unmarshalling within my Virgo OSGi application. I created an OSGi bundle for Jabsorb and found that I had to add DynamicImport-Package=* to its manifest because Jabsorb uses Class.forName(String name) during unmarshalling. If you need to understand why Class.forName(String name) is an issue, read this. I understand there are other ways to deal with this issue, but DynamicImport-Package seems like a reasonable solution for a serialization library.|
Anyway, DynamicImport-Package for my Jabsorb bundle seems to work great until I use it within an application defined by a scoped plan. It works fine without a plan and it works fine within an application defined by an un-scoped plan. To clarify, Jabsorb is not referenced directly in my plan, but it is used as a runtime dependency via OSGi dependency resolution.
I'd like to use a scoped plan to get the nice Virgo logging benefits that I only seem to get with scoped plans.
Any ideas what could be going on here?
Powered by FUDForum
. Page generated in 0.01784 seconds