March 2012 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-542) DynamicImport-Package doesn't work with system bundle packages

by Mathieu ANCELIN (JIRA)

Mathieu ANCELIN created JBOSGI-542: -------------------------------------- Summary: DynamicImport-Package doesn't work with system bundle packages Key: JBOSGI-542 URL: https://issues.jboss.org/browse/JBOSGI-542 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Affects Versions: JBossOSGi 1.2.0 Environment: Mac OSX 10.6.8, JDK 1.6.0_29, Maven 3.0.4 Reporter: Mathieu ANCELIN Assignee: Thomas Diesler When an OSGi bundle use DynamicImport-Package: * to import system classes like 'javax.naming.*', 'javax.xml.parsers', it results in a NoClassDefFoundError. -- 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

13 years, 10 months

2
7
0 / 0

[JBoss JIRA] (JBOSGI-534) Invalid canonical name for legacy bundles

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-534: ------------------------------------- Summary: Invalid canonical name for legacy bundles Key: JBOSGI-534 URL: https://issues.jboss.org/browse/JBOSGI-534 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.2.0 Currently we have {code} 11:13:34,499 INFO [org.jboss.osgi.framework.internal.HostBundleState] (pool-4-thread-1) Bundle started: null:0.0.0 11:13:34,504 INFO [org.jboss.osgi.framework.internal.HostBundleState] (pool-4-thread-1) Bundle stopped: null:0.0.0 {code} -- 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

13 years, 10 months

1
4
0 / 0

[JBoss JIRA] (JBOSGI-531) Integrate standalone resolver with Framework

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-531: ------------------------------------- Summary: Integrate standalone resolver with Framework Key: JBOSGI-531 URL: https://issues.jboss.org/browse/JBOSGI-531 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.2.0 Integrate and use the standalone resolver based on the org.osgi.service.resolver API -- 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

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] (JBOSGI-519) InitialContextFactoryBuilder already registered in AS

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-519: ------------------------------------- Summary: InitialContextFactoryBuilder already registered in AS Key: JBOSGI-519 URL: https://issues.jboss.org/browse/JBOSGI-519 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Enterprise Services Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.2 In AS we see {code} 09:59:52,782 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.NamingSupport.provideJNDIIntegration(NamingSupport.java:44) at org.jboss.test.osgi.example.jndi.JNDITestCase.testOSGiNamingContext(JNDITestCase.java:91) {code} -- 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

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] (JBOSGI-527) Unique error and warning message codes for all jbosgi projects

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-527: ------------------------------------- Summary: Unique error and warning message codes for all jbosgi projects Key: JBOSGI-527 URL: https://issues.jboss.org/browse/JBOSGI-527 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.1 -- 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

13 years, 10 months

1
7
0 / 0

[JBoss JIRA] (JBOSGI-530) No logging messages from org.jboss.modules

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-530: ------------------------------------- Summary: No logging messages from org.jboss.modules Key: JBOSGI-530 URL: https://issues.jboss.org/browse/JBOSGI-530 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.1.2 jboss-modules requires the client to explicitly set the ModuleLogger, otherwise there are no logging messages. Currently the framework does not do that -- 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

13 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-487) Add an introduction to Enterprise OSGi to the Wiki

by Thomas Diesler (JIRA)

Add an introduction to Enterprise OSGi to the Wiki -------------------------------------------------- Key: JBOSGI-487 URL: https://issues.jboss.org/browse/JBOSGI-487 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Add EOSGi-4.2 coverage to https://docs.jboss.org/author/display/JBOSGI/Introduction -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] (JBOSGI-533) OSGiMetaData returns non-stable value from toString()

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-533: ------------------------------------- Summary: OSGiMetaData returns non-stable value from toString() Key: JBOSGI-533 URL: https://issues.jboss.org/browse/JBOSGI-533 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.2.0 Currently {code} @Override public String toString() { return cachedAttributes.toString(); } {code} -- 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

13 years, 10 months

1
4
0 / 0

[JBoss JIRA] (JBOSGI-522) Update felix/equinox modules for meaningful performance data

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-522: ------------------------------------- Summary: Update felix/equinox modules for meaningful performance data Key: JBOSGI-522 URL: https://issues.jboss.org/browse/JBOSGI-522 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 -- 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

13 years, 10 months

1
6
0 / 0

[JBoss JIRA] (JBOSGI-532) Externalize notion of OSGi Environment

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-532: ------------------------------------- Summary: Externalize notion of OSGi Environment Key: JBOSGI-532 URL: https://issues.jboss.org/browse/JBOSGI-532 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Currently, the BundleManager is the maintainer of all bundles. This should be generalized/externalized to the Environment, which should maintain a set of Resources. The Framework would be a client of the Environment. Other clients to the Environment (i.e. AS7) can also register Resources with the Environment, which would then be available to the Resolver. -- 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

13 years, 10 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues March 2012