Even if system bundle exports those packages, your bundle won't be able
to see them unless it imports. Ideally, the EJB container generated
proxy object should be using a class loader that can see these
additional classes instead of assuming caller's class loader to be
capable of loading them. So, pl file a bug under ejb category. In the
meanwhile, I guess the work around can keep you going.
Thanks,
Sahoo
On Monday 19 September 2011 05:57 PM, forums_at_java.net wrote:
> Sahoo,
>
> Thanks for the quick reply. The solution DynamicImport-Package:
> com.sun.ejb.*
> did not help because something else was missing.
> DynamicImport-Package: * did
> solve it but, is it the way? I thought these classes (com.sun.*, sun.*
> etc.)
> would be part of the system bundle and available to any bundle. Is
> that the
> way it should be or I got it wrong?
>
> I guess I post the issue under the OSGi-JavaEE component?
>
> Thanks
>
> SDJ
>
>
> --
>
> [Message sent by forum member 'djordjevs']
>
> View Post: http://forums.java.net/node/844474
>
>