You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "David Schmitz (JIRA)" <ji...@apache.org> on 2010/10/24 12:38:38 UTC

[jira] Created: (ARIES-466) org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise implementation

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


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.


Re: [jira] Updated: (ARIES-466) org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise implementation

Posted by Alasdair Nottingham <no...@apache.org>.
Mark,

If you run:

svn ps svn:log --revprop -r1027526 "ARIES-446 AriesApplicationManager
registers an application BundleRepository even when one already
exists. Patch by Chris Wilkinson."

It should update the svn:log to be correct. I wont sort the JIRA side
of the story, but at least the svn log will be correct.

Alasdair

On 27 October 2010 19:41, Mark Nuttall (JIRA) <ji...@apache.org> wrote:
>
>     [ https://issues.apache.org/jira/browse/ARIES-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Mark Nuttall updated ARIES-466:
> -------------------------------
>
>    Comment: was deleted
>
> (was: Apologies for the accidental commit error. My October 11th svn commit should have been against ARIES-466, not ARIES-446. )
>
>> 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.
>
>



-- 
Alasdair Nottingham
not@apache.org

[jira] Commented: (ARIES-466) org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise implementation

Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Commented: (ARIES-466) org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise implementation

Posted by "David Schmitz (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ARIES-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925380#action_12925380 ] 

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 http://www.apache.org/dyn/closer.cgi/incubator/aries/org.apache.aries.jndi-0.2-incubating.jar

> 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.


[jira] Commented: (ARIES-466) org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise implementation

Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ARIES-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924716#action_12924716 ] 

Alasdair Nottingham commented on ARIES-466:
-------------------------------------------

Mark,

I think you accidentally tagged a commit against this issue. Any chance you could add a comment indicating which JIRA it should have been associated with?

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.


[jira] Updated: (ARIES-466) org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise implementation

Posted by "Mark Nuttall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ARIES-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Nuttall updated ARIES-466:
-------------------------------

    Comment: was deleted

(was: Apologies for the accidental commit error. My October 11th svn commit should have been against ARIES-466, not ARIES-446. )

> 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.


[jira] Commented: (ARIES-466) org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise implementation

Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Commented: (ARIES-466) org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise implementation

Posted by "Mark Nuttall (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ARIES-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925492#action_12925492 ] 

Mark Nuttall commented on ARIES-466:
------------------------------------

Apologies for the accidental commit error. My October 11th svn commit should have been against ARIES-466, not ARIES-446. 

> 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.


[jira] Commented: (ARIES-466) org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise implementation

Posted by "Mark Nuttall (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ARIES-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925496#action_12925496 ] 

Mark Nuttall commented on ARIES-466:
------------------------------------

Apologies for the accidental commit error. My October 11th svn commit should have been against ARIES-446, not ARIES-466.

> 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.