I confused by your message.  Are you saying these com.sun.jndi* packages are 
exported by a geronimo bundle?  If so, which one?  That would be a mistake we'd 
like to  fix.
I didn't see these exports in the geronimo-jta_1.1_spec bundles I looked in.

And, I agree with Andreas that adding these to jre.properties is the correct 
approach (other than convincing mq not to use them :-)

thanks
david jencks
On Mar 12, 2011, at 2:35 PM, Bengt Rodehav wrote:

> I'm not sure if this is the right forum for this question but I'll give it a 
> try.
> 
> I'm trying to use Websphere MQ (client jar's) from within Karaf 2.1.3. I've 
> had great troubles with this since there are several problems with the OSGi 
> bundles that are included in MQ (version 7.0.1.4). By manually editing the 
> manifest of the bundles I've finally gotten it to work. However, one of the 
> bundles conflict with my Geronimo jta bundle which caused me not wanting to 
> use that bundle. However, that bundle also exports the following packages 
> (which MQ needs):
> 
>  com.sun.jndi.fscontext
>  com.sun.jndi.ldap
>  com.sun.jndi.toolkit.chars
>  com.sun.jndi.toolkit.corba
>  com.sun.jndi.toolkit.ctx
>  com.sun.jndi.toolkit.dir
>  com.sun.jndi.toolkit.url
>  com.sun.jndi.url.file
>  com.sun.jndi.url.jndi
>  com.sun.jndi.url.ldap
> 
> If I add these properties to jre.properties then it works. However, I believe 
> this is bad practice. It is usually better to deploy a bundle that exports 
> the packages. Most of the JEE specs are provided as bundles by Geronimo but I 
> haven't found a bundle including the above packages. Does anyone know where I 
> can find that? Or is adding them to jre.properties OK?
> 
> /Bengt

Reply via email to