You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Mahammad Nasir <ma...@huawei.com> on 2010/03/08 08:49:14 UTC

Not able to find javax.* related classes

Hi All
 
My bundles are not able to find the packages related to javax.*
 
But if i print values for key FRAMEWORK_SYSTEMPACKAGES, it prints all the
javax packages. But bundles not able to find the classes/packages unless in
manifest file we explicitly import the packages.
 
As i remember earlier (I donot know why,How) this was working without
explicitly adding import statement. 
 
Is there any other simple way to tell framework to find the system packages?
For example to use string class we dont explicitly import the packages. 
 
Nasir

Re: Not able to find javax.* related classes

Posted by Felix Meschberger <fm...@gmail.com>.
Hi,

Just like any imports javax.* must be regularly imported by packages.
The only exception to this rule are java.* classes.

If you do not import javax.* you would have to provide them by boot
delegation. But I strongly discourage this as IMHO this defeats much of
what OSGi is all about.

Regards
Felix

On 08.03.2010 08:49, Mahammad Nasir wrote:
> Hi All
>  
> My bundles are not able to find the packages related to javax.*
>  
> But if i print values for key FRAMEWORK_SYSTEMPACKAGES, it prints all the
> javax packages. But bundles not able to find the classes/packages unless in
> manifest file we explicitly import the packages.
>  
> As i remember earlier (I donot know why,How) this was working without
> explicitly adding import statement. 
>  
> Is there any other simple way to tell framework to find the system packages?
> For example to use string class we dont explicitly import the packages. 
>  
> Nasir
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org