aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Schmitz (JIRA)" <>
Subject [jira] Commented: (ARIES-466) org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise implementation
Date Wed, 27 Oct 2010 14:20:20 GMT


David Schmitz commented on ARIES-466:

Hi Alasdair,

I got it to work with the Aries JNDI bundles but the difference now is that I'm using the
jars provided via maven. 
The jars  provided on your download page seam to differ see

> org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise implementation
> --------------------------------------------------------------------------------
>                 Key: ARIES-466
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: JNDI
>    Affects Versions: 0.2
>         Environment: all
>            Reporter: David Schmitz
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
> org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise bundle implementations
which causes problems when using 
> <dependency>
>      <groupId>org.osgi</groupId>
>      <artifactId>org.osgi.enterprise</artifactId>
>      <version>4.2.0</version>
> </dependency>
> as well. If used with org.osgi.enterprise one gets an error that the Initial JNDI Context
Factory is already registered and aries JNDI can not work. 
> I could get around this problem by using org.eclipse.gemini.naming.framework with org.osgi.enterprise
+ rest of aries. 
> So my suggestion is simply remove org.osgi api implementation from org.apache.aries.jndi-0.2-incubating
and use the one from reference org.osgi.enterprise bundle.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message