[JBoss JIRA] Created: (JBOSGI-81) Provide propper JNDI integration (RFP-84)

[JBoss JIRA] (JBOSGI-581) Update...

[JBoss JIRA] (JBOSGI-579)...

Thomas Diesler (JIRA)

Tuesday, 12 May 2009 Tue, 12 May '09

9:25 a.m.

Provide propper JNDI integration (RFP-84) ----------------------------------------- Key: JBOSGI-81 URL: https://jira.jboss.org/jira/browse/JBOSGI-81 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Assignee: Thomas Diesler https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Thomas Diesler (JIRA)

Thursday, 28 May Thu, 28 May

5:52 p.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Provide propper JNDI integration (RFP-84)

[ https://jira.jboss.org/jira/browse/JBOSGI-81?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Fix Version/s: JBossOSGi 1.0.x

...

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

Friday, 11 December Fri, 11 Dec

5:41 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Certified JNDI integration

[ https://jira.jboss.org/jira/browse/JBOSGI-81?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Summary: Certified JNDI integration (was: Provide propper JNDI integration (RFP-84)) Component/s: jboss-osgi-jndi (was: Other)

...

Certified JNDI integration -------------------------- Key: JBOSGI-81 URL: https://jira.jboss.org/jira/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.x https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...

Thomas Diesler (JIRA)

Thursday, 11 February Thu, 11 Feb

3:23 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Certified JNDI integration

[ https://jira.jboss.org/jira/browse/JBOSGI-81?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Fix Version/s: JBossOSGi 1.0.0 Beta7 (was: JBossOSGi 1.0.x)

...

Certified JNDI integration -------------------------- Key: JBOSGI-81 URL: https://jira.jboss.org/jira/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...

Thomas Diesler (JIRA)

Tuesday, 4 May Tue, 4 May

5:08 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) [EOSGi] Certified JNDI integration

[ https://jira.jboss.org/jira/browse/JBOSGI-81?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Summary: [EOSGi] Certified JNDI integration (was: Certified JNDI integration)

...

[EOSGi] Certified JNDI integration ---------------------------------- Key: JBOSGI-81 URL: https://jira.jboss.org/jira/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.x https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...

Thomas Diesler (JIRA)

6:05 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Certified JNDI integration

...

Certified JNDI integration -------------------------- Key: JBOSGI-81 URL: https://jira.jboss.org/jira/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...

Thomas Diesler (JIRA)

Thursday, 6 May Thu, 6 May

5:14 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) [EOSGi] Certified JNDI integration

...

[EOSGi] Certified JNDI integration ---------------------------------- Key: JBOSGI-81 URL: https://jira.jboss.org/jira/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...

Thomas Diesler (JIRA)

Thursday, 5 August Thu, 5 Aug

3:11 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Compliant JNDI integration

[ https://jira.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Summary: Compliant JNDI integration (was: [EOSGi] Certified JNDI integration)

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://jira.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

Tuesday, 26 July Tue, 26 Jul

5:53 a.m.

New subject: [JBoss JIRA] Resolved: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved JBOSGI-81. ---------------------------------- Resolution: Out of Date Out of Date

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Fix For: Approved and Unscheduled https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

5:57 a.m.

New subject: [JBoss JIRA] Reopened: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened JBOSGI-81: ----------------------------------

...

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

5:57 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Fix Version/s: Approved and Unscheduled

...

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

5:57 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Comment: was deleted (was: Out of Date)

...

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

6:01 a.m.

New subject: [JBoss JIRA] Resolved: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved JBOSGI-81. ---------------------------------- Fix Version/s: (was: Approved and Unscheduled) Resolution: Out of Date Out of Date

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

Friday, 29 July Fri, 29 Jul

4:43 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Comment: was deleted (was: Out of Date)

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

4:43 a.m.

New subject: [JBoss JIRA] Reopened: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened JBOSGI-81: ---------------------------------- Please vote if you want to see progress on this

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

4:47 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Fix Version/s: Approved but Unscheduled

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

David Bosschaert (JIRA)

4:47 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert updated JBOSGI-81: ----------------------------------- Fix Version/s: (was: Approved but Unscheduled) Description: Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42 (was: https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ...)

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

David Bosschaert (JIRA)

4:49 a.m.

New subject: [JBoss JIRA] Commented: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert commented on JBOSGI-81: ---------------------------------------- Looking up an InitialContext in the OSGi Service Registry is supported today. The main thing that's missing right now is support for the osgi: naming context so that you can do lookups such as: osgi:service/org.acme.MyService osgi:servicelist/javax.sql.DataSource/(&(db=mydb)(version=3.1)) osgi:service/foo osgi:framework/bundleContext

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Fix For: Approved but Unscheduled Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

4:49 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Fix Version/s: Approved but Unscheduled

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Fix For: Approved but Unscheduled Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

Monday, 1 August Mon, 1 Aug

4:39 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Fix Version/s: Community Pickup Area (was: Approved but Unscheduled) What needs to be done here is to take a look at http://aries.apache.org/modules/jndiproject.html or an equivalent implementation and see if it is sufficiently abstracted to integrate with the JNDI store that is available in AS7. Compliant OSGI/JNDI functionality in AS7 is the target.

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Fix For: Community Pickup Area Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

Wednesday, 17 August Wed, 17 Aug

4:34 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Fix Version/s: JBossOSGi 1.0.2

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.2 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Thomas Diesler (JIRA)

4:34 a.m.

New subject: [JBoss JIRA] Updated: (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Fix Version/s: (was: Community Pickup)

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.2 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

David Bosschaert (Assigned) (JIRA)

Monday, 9 January Mon, 9 Jan

5:36 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert reassigned JBOSGI-81: -------------------------------------- Assignee: David Bosschaert

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Assignee: David Bosschaert Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

-- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

David Bosschaert (Updated) (JIRA)

5:36 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert updated JBOSGI-81: ----------------------------------- Fix Version/s: (was: JBossOSGi 1.0.2)

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Assignee: David Bosschaert Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

Thursday, 12 January Thu, 12 Jan

8:12 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert commented on JBOSGI-81: ---------------------------------------- With AS7-3286 in place any OSGi-compliant JNDI implementation (such as the one from Apache Aries) can be dropped in to provide this functionality.

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Assignee: David Bosschaert Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

Wednesday, 25 January Wed, 25 Jan

8:32 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Fix Version/s: JBossOSGi 1.0.1

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: jboss-osgi-jndi Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

Monday, 6 February Mon, 6 Feb

9:33 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert resolved JBOSGI-81. ------------------------------------ Resolution: Done Added tests to JBOSGi umbrella: Running org.jboss.test.osgi.example.jndi.JNDITestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.073 sec Running org.jboss.test.osgi.example.jbossas.JNDIIntegrationTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.086 sec Pull request: https://github.com/jbosgi/jbosgi/pull/1

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

Tuesday, 7 February Tue, 7 Feb

5:52 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened JBOSGI-81: ---------------------------------- Fails in AS {code} 11:45:15,229 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.aries.jndi:0.3.1 11:45:15,240 INFO [org.jboss.as.server] (pool-9-thread-1) JBAS018559: Deployed "org.apache.aries.jndi:org.apache.aries.jndi:0.3.1" 11:45:15,289 INFO [org.apache.aries.jndi.startup.Activator] (pool-4-thread-1) It was not possible to register an InitialContextFactoryBuilder with the NamingManager because another builder called org.jboss.as.naming.InitialContextFactoryBuilder was already registered. Support for calling new InitialContext() will not be enabled.: java.lang.IllegalStateException: InitialContextFactoryBuilder already set at javax.naming.spi.NamingManager.setInitialContextFactoryBuilder(NamingManager.java:692) [rt.jar:1.6.0_29] at org.apache.aries.jndi.startup.Activator.start(Activator.java:76) at org.apache.aries.jndi.priv.Activator.start(Activator.java:38) at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300) at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223) at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488) at org.jboss.test.osgi.example.NamingSupport.provideJNDIIntegration(NamingSupport.java:45) {code}

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

5:56 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert commented on JBOSGI-81: ---------------------------------------- Does it actually fail the test or are you simply seeing the exception? This message is emitted by Aries when it cannot set certain statics in the VM. The reason that it can't set these statics is because AS7 already sets them so this exception (and another one which is also logged at INFO level) can be ignored. So regardless of the exception, the functionality should still work (if the test passes).

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

6:02 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler commented on JBOSGI-81: -------------------------------------- Tests in error: testOSGiNamingContext(org.jboss.test.osgi.example.jndi.JNDITestCase): Unable to obtain JNDI Context Manager Service

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

6:04 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert commented on JBOSGI-81: ---------------------------------------- Thanks - I'll have a look.

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

7:45 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

9:16 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert commented on JBOSGI-81: ---------------------------------------- I wonder could it be a timeout or something? I haven't been able to reproduce the failure. I've tried on a Mac with JDK 1.6 and on Fedora 16 with OpenJDK 1.7. Should I try to increase the timeout and see if that helps? The Hudson machine is potentially a lot busier than my machine and may therefore take a bit longer to be finished initializing.

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

9:34 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert commented on JBOSGI-81: ---------------------------------------- I've sent another pull request where I removed the timeout and improved the test as suggested here [1]. Pull request: https://github.com/jbosgi/jbosgi/pull/2 [1] https://github.com/bosschaert/jbosgi/commit/f62c0132f803a3c5b4fcfefd75f86...

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

10 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert edited comment on JBOSGI-81 at 2/7/12 10:00 AM: ----------------------------------------------------------------- I've sent another pull request where I removed the timeout and improved the test as suggested here [1]. Pull request: https://github.com/jbosgi/jbosgi/pull/3 [1] https://github.com/bosschaert/jbosgi/commit/f62c0132f803a3c5b4fcfefd75f86... was (Author: bosschaert): I've sent another pull request where I removed the timeout and improved the test as suggested here [1]. Pull request: https://github.com/jbosgi/jbosgi/pull/2 [1] https://github.com/bosschaert/jbosgi/commit/f62c0132f803a3c5b4fcfefd75f86...

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

Wednesday, 8 February Wed, 8 Feb

3:39 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler commented on JBOSGI-81: -------------------------------------- The [server.log|https://hudson.qa.jboss.com/hudson/view/JBossOSGi/job/jbosgi-r...] says {code} 07:01:56,248 INFO [org.apache.aries.jndi.startup.Activator] (pool-4-thread-1) It was not possible to register an InitialContextFactoryBuilder with the NamingManager because another builder called org.jboss.as.naming.InitialContextFactoryBuilder was already registered. Support for calling new InitialContext() will not be enabled.: java.lang.IllegalStateException: InitialContextFactoryBuilder already set at javax.naming.spi.NamingManager.setInitialContextFactoryBuilder(NamingManager.java:692) [rt.jar:1.6.0_30] at org.apache.aries.jndi.startup.Activator.start(Activator.java:76) at org.apache.aries.jndi.priv.Activator.start(Activator.java:38) at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300) at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223) at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488) at org.jboss.test.osgi.example.NamingSupport.provideJNDIIntegration(NamingSupport.java:45) {code} The root cause is AFAICS that the InitialContextFactoryBuilder singleton is already set in the VM.

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

3:57 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

10:43 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert commented on JBOSGI-81: ---------------------------------------- The actual problem is this: {noformat}Failed: org.jboss.test.osgi.example.jbossas.JNDIIntegrationTestCase.testOSGiNamingContext: java.lang.ClassCastException: org.apache.aries.jndi.ContextManagerService cannot be cast to org.osgi.service.jndi.JNDIContextManager at org.jboss.test.osgi.NamingSupport.provideJNDIIntegration(NamingSupport.java:47) at org.jboss.test.osgi.example.jbossas.JNDIIntegrationTestCase.testOSGiNamingContext(JNDIIntegrationTestCase.java:88){noformat} Looking at the source in Aries, the ContextManagerService implements JNDIContextManager. So the test must be getting the JNDIContextManager class from another source than the Aries JNDI bundle.

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

Friday, 2 March Fri, 2 Mar

3:20 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

3:35 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler commented on JBOSGI-81: -------------------------------------- We still have this InitialContextFactoryBuilder exception issue, which would not be acceptable in EAP. We can either defer until this is fixed upstream or provide a fork that logs a warning. Both is fine with me. There needs to be documentation coverage as well.

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

3:55 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert commented on JBOSGI-81: ---------------------------------------- When I look at the source code where this message is emitted, I can see that it's a log message at the info level (see http://svn.apache.org/repos/asf/aries/trunk/jndi/jndi-core/src/main/java/...): logger.log(LogService.LOG_INFO, Utils.MESSAGES.getMessage("unable.to.set.static.ICFB.already.exists", getClassName(InitialContextFactoryBuilder.class)), e); The log message contains the exception, but the exception isn't propagated up.

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

4:03 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler edited comment on JBOSGI-81 at 3/2/12 4:03 AM: -------------------------------------------------------------- When I look at the source code where this message is emitted, I can see that it's a log message at the info level (see http://svn.apache.org/repos/asf/aries/trunk/jndi/jndi-core/src/main/java/...): {code} logger.log(LogService.LOG_INFO, Utils.MESSAGES.getMessage("unable.to.set.static.ICFB.already.exists", getClassName(InitialContextFactoryBuilder.class)), e); {code} The log message contains the exception, but the exception isn't propagated up. was (Author: bosschaert): When I look at the source code where this message is emitted, I can see that it's a log message at the info level (see http://svn.apache.org/repos/asf/aries/trunk/jndi/jndi-core/src/main/java/...): logger.log(LogService.LOG_INFO, Utils.MESSAGES.getMessage("unable.to.set.static.ICFB.already.exists", getClassName(InitialContextFactoryBuilder.class)), e); The log message contains the exception, but the exception isn't propagated up.

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

4:05 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler edited comment on JBOSGI-81 at 3/2/12 4:05 AM: -------------------------------------------------------------- Yes, this should be changed to {code} logger.log(LogService.LOG_INFO, message, classname); logger.log(LogService.LOG_DEBUG, message, classname, e); {code} of simmilar. We don't want to see the exception at info level was (Author: thomas.diesler): Yes, this should be changed to {code} logger.log(LogService.LOG_INFO, message, classname); logger.log(LogService.LOG_DEBUG, message, classname, e); {code}

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

4:05 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler commented on JBOSGI-81: -------------------------------------- Yes, this should be changed to {code} logger.log(LogService.LOG_INFO, message, classname); logger.log(LogService.LOG_DEBUG, message, classname, e); {code}

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

4:15 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert commented on JBOSGI-81: ---------------------------------------- I actually tried to change this, but there was some pushback from others who are using these log message for a particular purpose, so I'm quite doubtful that this change will be accepted by the Aries community. What I can try is to remove the exception from the INFO level but keep the message, then log the exception at debug level, would that work?

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

4:42 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] David Bosschaert edited comment on JBOSGI-81 at 3/2/12 4:40 AM: ---------------------------------------------------------------- Edit: at closer inspection I see that we were proposing the same thing :) I'll see if I can get this agreed in the Aries community. was (Author: bosschaert): I actually tried to change this, but there was some pushback from others who are using these log message for a particular purpose, so I'm quite doubtful that this change will be accepted by the Aries community. What I can try is to remove the exception from the INFO level but keep the message, then log the exception at debug level, would that work?

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

4:48 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler edited comment on JBOSGI-81 at 3/2/12 4:48 AM: -------------------------------------------------------------- Yes, this should be changed to {code} logger.log(LogService.LOG_INFO, message, classname); logger.log(LogService.LOG_DEBUG, message, classname, e); {code} or similar. We don't want to see the exception at info level was (Author: thomas.diesler): Yes, this should be changed to {code} logger.log(LogService.LOG_INFO, message, classname); logger.log(LogService.LOG_DEBUG, message, classname, e); {code} of simmilar. We don't want to see the exception at info level

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

Monday, 5 March Mon, 5 Mar

8:16 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

Wednesday, 7 March Wed, 7 Mar

5:17 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Fix Version/s: JBossOSGi 1.0.2 (was: JBossOSGi 1.0.1) The mandatory dependency on Blueprint should be resolved as well. Please provide a link to the corresponding issue in Aries

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.2 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

David Bosschaert (JIRA)

5:29 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.2 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

Thursday, 26 April Thu, 26 Apr

4:48 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Component/s: JNDI (was: Other)

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: JNDI Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.2.0 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

Thomas Diesler (JIRA)

Monday, 18 June Mon, 18 Jun

4:43 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

David Bosschaert (JIRA)

Monday, 23 July Mon, 23 Jul

9:49 a.m.

New subject: [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration

...

Compliant JNDI integration -------------------------- Key: JBOSGI-81 URL: https://issues.jboss.org/browse/JBOSGI-81 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: JNDI Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 2.0.0 Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42

4300

days inactive

5468

days old

jboss-osgi-issues@lists.jboss.org

Manage subscription

52 comments

4 participants

tags (0)

participants (4)

David Bosschaert (Assigned) (JIRA)
David Bosschaert (JIRA)
David Bosschaert (Updated) (JIRA)
Thomas Diesler (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

[JBoss JIRA] Created: (JBOSGI-81) Provide propper JNDI integration (RFP-84)