January 2013 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-628) resteasy-jackson-provider exported org.jboss.resteasy.plugins.providers

by Arthur Tsang (JIRA)

Arthur Tsang created JBOSGI-628: ----------------------------------- Summary: resteasy-jackson-provider exported org.jboss.resteasy.plugins.providers Key: JBOSGI-628 URL: https://issues.jboss.org/browse/JBOSGI-628 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Distribution Affects Versions: JBossOSGi 1.1.1 Environment: JBoss 7.1.1.Final Reporter: Arthur Tsang Assignee: Thomas Diesler resteasy-jackson-provider exported org.jboss.resteasy.plugins.providers which it has no class in that package. Bundle importing org.jboss.resteasy.plugins.providers might bind to resteasy-jackson-provider instead of resteasy-jaxrs resulting in class not found exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-625) Improve log message when bundle start level not valid for start

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin... ] Thomas Diesler commented on JBOSGI-625: --------------------------------------- The fix is about the subject of this jira only. For the other issue we need a different jira. > Improve log message when bundle start level not valid for start > --------------------------------------------------------------- > > Key: JBOSGI-625 > URL: https://issues.jboss.org/browse/JBOSGI-625 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Affects Versions: JBossOSGi 1.1.1 > Environment: Jboss as 7.1.2.Final > JDK6 > EAP 6.0.0 > Reporter: Daniel Chapman > Assignee: Thomas Diesler > Priority: Minor > Fix For: JBossOSGi 1.2.0 > > > When I set org.jboss.osgi.framework to DEBUG, I get messages like the following: > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Starting bundle: org.apache.aries.blueprint:1.0.0 > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Start level [2] not valid for: org.apache.aries.blueprint:1.0.0 > I'd like more information on this message. I've seen it during various startup configurations in messing with my capabilities and it seems to matter little when fixing real issue. > What I'm doing above is clicking the Start Bundle button in the osgi console. It prints these two messages as DEBUG, nothing else is printed, and net result is console refreshes and no changes have been made to the status of the bundle. > So is this message really relevant, if so - then why DEBUG only. Second - what do I do when I got to start a module, nothing is printed to logs (except above) and the bundle doesn't actually start? > Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-625) Improve log message when bundle start level not valid for start

by Daniel Chapman (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin... ] Daniel Chapman commented on JBOSGI-625: --------------------------------------- So does your fix resolve the issue where the framework can get into a state where things cannot be started and there are no error messages? And only way to fix is by blowing away the tmp and/or data directory? > Improve log message when bundle start level not valid for start > --------------------------------------------------------------- > > Key: JBOSGI-625 > URL: https://issues.jboss.org/browse/JBOSGI-625 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Affects Versions: JBossOSGi 1.1.1 > Environment: Jboss as 7.1.2.Final > JDK6 > EAP 6.0.0 > Reporter: Daniel Chapman > Assignee: Thomas Diesler > Priority: Minor > Fix For: JBossOSGi 1.2.0 > > > When I set org.jboss.osgi.framework to DEBUG, I get messages like the following: > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Starting bundle: org.apache.aries.blueprint:1.0.0 > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Start level [2] not valid for: org.apache.aries.blueprint:1.0.0 > I'd like more information on this message. I've seen it during various startup configurations in messing with my capabilities and it seems to matter little when fixing real issue. > What I'm doing above is clicking the Start Bundle button in the osgi console. It prints these two messages as DEBUG, nothing else is printed, and net result is console refreshes and no changes have been made to the status of the bundle. > So is this message really relevant, if so - then why DEBUG only. Second - what do I do when I got to start a module, nothing is printed to logs (except above) and the bundle doesn't actually start? > Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-520) Remove dependency on blueprint from aries-jndi

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-520?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-520: ---------------------------------- Assignee: (was: David Bosschaert) Available for reassignment > Remove dependency on blueprint from aries-jndi > ---------------------------------------------- > > Key: JBOSGI-520 > URL: https://issues.jboss.org/browse/JBOSGI-520 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JNDI > Reporter: Thomas Diesler > Fix For: JBossOSGi 2.0.0 Alpha1 > > > aries-jndi-0.3.1 cannot be used without blueprint being installed. The two techs are unrelated however. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-582) Update Aries JMX to 1.1.0

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-582?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-582: ---------------------------------- Assignee: (was: David Bosschaert) Available for reassignment > Update Aries JMX to 1.1.0 > ------------------------- > > Key: JBOSGI-582 > URL: https://issues.jboss.org/browse/JBOSGI-582 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX > Reporter: David Bosschaert > Fix For: JBossOSGi 2.0.0 Alpha1 > > > The JMX integration should be updated to version 1.1.0 which maps to the jmx-next work done in Apache Aries. > The jmx-next work implements the OSGi Enterprise 5.0 JMX specification. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

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

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-522?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-522: ---------------------------------- Assignee: (was: David Bosschaert) Available for reassignment > 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) > Components: Distribution > Reporter: Thomas Diesler > Fix For: JBossOSGi 1.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

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

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated JBOSGI-81: --------------------------------- Assignee: (was: David Bosschaert) Available for reassignment > 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 > Fix For: JBossOSGi 2.0.0 Alpha1 > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-500) Pass JNDI CT

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-500?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-500: ---------------------------------- Assignee: (was: David Bosschaert) Available for reassignment > Pass JNDI CT > ------------ > > Key: JBOSGI-500 > URL: https://issues.jboss.org/browse/JBOSGI-500 > Project: JBoss OSGi > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JNDI > Reporter: David Bosschaert > Fix For: Approved / Unscheduled > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-541) Document how bundle configurations can be edited

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-541?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-541: ---------------------------------- Assignee: (was: David Bosschaert) Available for reassignment > Document how bundle configurations can be edited > ------------------------------------------------ > > Key: JBOSGI-541 > URL: https://issues.jboss.org/browse/JBOSGI-541 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Thomas Diesler > Fix For: JBossOSGi 1.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

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

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-487?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-487: ---------------------------------- Assignee: (was: David Bosschaert) Available for reassignment > 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 > Fix For: JBossOSGi 1.2.0 > > > Add EOSGi-4.2 coverage to https://docs.jboss.org/author/display/JBOSGI/Introduction -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues January 2013