[JBoss JIRA] (JBOSGI-626) Upgrading EAP6 JBOSGI Implementation
by Daniel Chapman (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-626?page=com.atlassian.jira.plugin... ]
Daniel Chapman closed JBOSGI-626.
---------------------------------
Resolution: Rejected
Sorry I meant this for community forum, not a Jira!
> Upgrading EAP6 JBOSGI Implementation
> ------------------------------------
>
> Key: JBOSGI-626
> URL: https://issues.jboss.org/browse/JBOSGI-626
> Project: JBoss OSGi
> Issue Type: Release
> Security Level: Public(Everyone can see)
> Components: Core Framework
> Affects Versions: JBossOSGi 1.1.1
> Environment: eap 6.0.0 and jboss 7.1.2.Final
> Reporter: Daniel Chapman
> Assignee: Thomas Diesler
> Priority: Minor
> Labels: osgi
>
> I've been having problems with OSGI and from forums it is clear there is a lot of activity and fixes with forthcoming jbosgi implementations. Additionally - capabilities everyone is using generally specify versions 0.4 of aries and felix bundles.
> Can I update my 7.1.2.Final version of jboss as to use 'better' versions of jbosgi and capabilities? Are there compatibility issues? Project page says framework version supported for 7.1.2.Final is at most 1.1.1. That true or could I upgrade. Is there a central area showing me modules/versions I'd need to install and an updated capabilities list?
> Been trying to upgrade aries/felix on my own and this seems to load fine, but I can't get aries jmx and blueprint bundles to start, and there are no messages to help.
> <capabilities>
> <capability name="javax.servlet.api:v25"/>
> <capability name="javax.transaction.api"/>
> <capability name="org.jboss.osgi.logging" startlevel="1"/>
> <capability name="org.apache.felix:org.apache.felix.log:1.0.1" startlevel="2"/>
> <capability name="org.apache.felix:org.apache.felix.configadmin:1.6.0" startlevel="2"/>
> <capability name="org.jboss.as.osgi.configadmin" startlevel="2"/>
> <capability name="org.ops4j.pax.web:pax-web-jetty-bundle:1.1.2" startlevel="1"/>
> <capability name="org.ops4j.pax.web:pax-web-jsp:1.1.2" startlevel="1"/>
> <capability name="commons-io:commons-io:2.4" startlevel="1"/>
> <capability name="org.apache.geronimo.bundles:json:20090211_1" startlevel="1"/>
> <capability name="commons-fileupload:commons-fileupload:1.2.1" startlevel="1"/>
> <capability name="org.apache.felix:org.apache.felix.webconsole:4.0.0" startlevel="3"/>
> <capability name="org.apache.aries:org.apache.aries.util:1.0.0"/>
> <capability name="org.apache.aries.jmx:org.apache.aries.jmx:1.0.0" startlevel="2"/>
> <capability name="org.jboss.osgi.jmx:jbosgi-jmx:1.1.0.Final"/>
> <capability name="org.apache.aries.proxy:org.apache.aries.proxy:1.0.0" startlevel="3"/>
> <capability name="org.apache.aries.blueprint:org.apache.aries.blueprint:1.0.0" startlevel="2"/>
> </capabilities>
--
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
13 years, 3 months
- 1
- 0
[JBoss JIRA] (JBOSGI-626) Upgrading EAP6 JBOSGI Implementation
by Daniel Chapman (JIRA)
Daniel Chapman created JBOSGI-626:
-------------------------------------
Summary: Upgrading EAP6 JBOSGI Implementation
Key: JBOSGI-626
URL: https://issues.jboss.org/browse/JBOSGI-626
Project: JBoss OSGi
Issue Type: Release
Security Level: Public (Everyone can see)
Components: Core Framework
Affects Versions: JBossOSGi 1.1.1
Environment: eap 6.0.0 and jboss 7.1.2.Final
Reporter: Daniel Chapman
Assignee: Thomas Diesler
Priority: Minor
I've been having problems with OSGI and from forums it is clear there is a lot of activity and fixes with forthcoming jbosgi implementations. Additionally - capabilities everyone is using generally specify versions 0.4 of aries and felix bundles.
Can I update my 7.1.2.Final version of jboss as to use 'better' versions of jbosgi and capabilities? Are there compatibility issues? Project page says framework version supported for 7.1.2.Final is at most 1.1.1. That true or could I upgrade. Is there a central area showing me modules/versions I'd need to install and an updated capabilities list?
Been trying to upgrade aries/felix on my own and this seems to load fine, but I can't get aries jmx and blueprint bundles to start, and there are no messages to help.
<capabilities>
<capability name="javax.servlet.api:v25"/>
<capability name="javax.transaction.api"/>
<capability name="org.jboss.osgi.logging" startlevel="1"/>
<capability name="org.apache.felix:org.apache.felix.log:1.0.1" startlevel="2"/>
<capability name="org.apache.felix:org.apache.felix.configadmin:1.6.0" startlevel="2"/>
<capability name="org.jboss.as.osgi.configadmin" startlevel="2"/>
<capability name="org.ops4j.pax.web:pax-web-jetty-bundle:1.1.2" startlevel="1"/>
<capability name="org.ops4j.pax.web:pax-web-jsp:1.1.2" startlevel="1"/>
<capability name="commons-io:commons-io:2.4" startlevel="1"/>
<capability name="org.apache.geronimo.bundles:json:20090211_1" startlevel="1"/>
<capability name="commons-fileupload:commons-fileupload:1.2.1" startlevel="1"/>
<capability name="org.apache.felix:org.apache.felix.webconsole:4.0.0" startlevel="3"/>
<capability name="org.apache.aries:org.apache.aries.util:1.0.0"/>
<capability name="org.apache.aries.jmx:org.apache.aries.jmx:1.0.0" startlevel="2"/>
<capability name="org.jboss.osgi.jmx:jbosgi-jmx:1.1.0.Final"/>
<capability name="org.apache.aries.proxy:org.apache.aries.proxy:1.0.0" startlevel="3"/>
<capability name="org.apache.aries.blueprint:org.apache.aries.blueprint:1.0.0" startlevel="2"/>
</capabilities>
--
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
13 years, 3 months
- 1
- 0
[JBoss JIRA] (JBOSGI-625) Start level not valid message
by Daniel Chapman (JIRA)
Daniel Chapman created JBOSGI-625:
-------------------------------------
Summary: Start level not valid message
Key: JBOSGI-625
URL: https://issues.jboss.org/browse/JBOSGI-625
Project: JBoss OSGi
Issue Type: Feature Request
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
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
13 years, 3 months
- 1
- 0