[
https://issues.apache.org/jira/browse/ARIES-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925483#action_12925483
]
Alasdair Nottingham commented on ARIES-466:
-------------------------------------------
What artefact did you get from maven? If you downloaded the
org.apache.aries.jndi.core artefact from maven you would see different things
from using org.apache.aries.jndi-0.2-incubating.jar.
Is their any chance you could add the exception you hit into the bug? It might
help me work out what went wrong.
Alasdair
> org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise
> implementation
> --------------------------------------------------------------------------------
>
> Key: ARIES-466
> URL: https://issues.apache.org/jira/browse/ARIES-466
> 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.
