[
https://issues.apache.org/jira/browse/ARIES-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924718#action_12924718
]
Alasdair Nottingham commented on ARIES-466:
-------------------------------------------
David,
I've looked at the jar for the 0.2 release and current maven output for 0.3 and
the only thing it includes that isn't part of our JNDI implementation is the
org.osgi.service.jndi package which just contains interfaces, no implementation.
>From what you say I suspect the problem might be that you have two
>implementations of the JNDI specification in your runtime, not that our
>implementation includes the org.osgi.service.jndi interfaces. I can't say for
>sure without seeing the exception.
> 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.
