[JBoss JIRA] (JBOSGI-617) Identity capability uses 'anonymous' in toString()
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-617?page=com.atlassian.jira.plugin... ]
Thomas Diesler updated JBOSGI-617:
----------------------------------
Fix Version/s: JBossOSGi 1.2.0
> Identity capability uses 'anonymous' in toString()
> --------------------------------------------------
>
> Key: JBOSGI-617
> URL: https://issues.jboss.org/browse/JBOSGI-617
> 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
>
>
> {code}
> 09:34:36,840 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) Install resource: HostBundleRevision[example-bundle:0.0.0]
> 09:34:36,840 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XIdentityCapability[atts={osgi.identity=example-bundle, type=osgi.bundle, version=0.0.0},[anonymous]]
> 09:34:36,840 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XResourceCapability[atts={osgi.wiring.bundle=example-bundle, bundle-version=0.0.0},[example-bundle:0.0.0]]
> 09:34:36,840 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XHostCapability[atts={osgi.wiring.host=example-bundle, bundle-version=0.0.0},[example-bundle:0.0.0]]
> 09:34:36,840 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageCapability[atts={osgi.wiring.package=org.jboss.as.test.integration.osgi.core},[example-bundle:0.0.0]]
> 09:34:36,840 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageRequirement[atts={osgi.wiring.package=org.osgi.framework},[example-bundle:0.0.0]]
> 09:34:36,841 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageRequirement[atts={osgi.wiring.package=org.jboss.arquillian.container.test.api},[example-bundle:0.0.0]]
> 09:34:36,841 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageRequirement[atts={osgi.wiring.package=org.jboss.arquillian.junit},[example-bundle:0.0.0]]
> 09:34:36,841 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageRequirement[atts={osgi.wiring.package=org.jboss.arquillian.osgi},[example-bundle:0.0.0]]
> 09:34:36,841 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageRequirement[atts={osgi.wiring.package=org.jboss.arquillian.test.api},[example-bundle:0.0.0]]
> 09:34:36,841 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageRequirement[atts={osgi.wiring.package=org.jboss.shrinkwrap.api},[example-bundle:0.0.0]]
> 09:34:36,841 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageRequirement[atts={osgi.wiring.package=org.jboss.shrinkwrap.api.asset},[example-bundle:0.0.0]]
> 09:34:36,841 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageRequirement[atts={osgi.wiring.package=org.jboss.shrinkwrap.api.spec},[example-bundle:0.0.0]]
> 09:34:36,841 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageRequirement[atts={osgi.wiring.package=org.junit},[example-bundle:0.0.0]]
> 09:34:36,841 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageRequirement[atts={osgi.wiring.package=org.junit.runner},[example-bundle:0.0.0]]
> 09:34:36,841 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-1) XPackageRequirement[atts={osgi.wiring.package=javax.inject},[example-bundle:0.0.0]]
> {code}
--
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, 4 months
[JBoss JIRA] (JBOSGI-625) Start level not valid message
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin... ]
Thomas Diesler updated JBOSGI-625:
----------------------------------
Fix Version/s: JBossOSGi 1.2.0
> Start level not valid message
> -----------------------------
>
> 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, 4 months
[JBoss JIRA] (JBOSGI-624) Bundle importing the package of multiple versions isn't supported
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-624?page=com.atlassian.jira.plugin... ]
Thomas Diesler edited comment on JBOSGI-624 at 1/24/13 5:11 AM:
----------------------------------------------------------------
This fundamental functionality is verified by our internal test suite and the OSGi TCK. Perhaps you are not defining the package capability version on the package directive
See OSGi-Spec 4.2
3.5.5 Export-Package
v e r s i o n – The version of the named packages with syntax as defined in Version on page 32. It defines the version of the associated packages. The default value is 0.0.0.
was (Author: thomas.diesler):
This fundamental functionality is verified by our internal test suite and the OSGi TCK. Perhaps you are not defining the package capability version on the package directive
> Bundle importing the package of multiple versions isn't supported
> -----------------------------------------------------------------
>
> Key: JBOSGI-624
> URL: https://issues.jboss.org/browse/JBOSGI-624
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Hari Ohm Prasath
> Assignee: Thomas Diesler
> Labels: OSGI
>
> I have a OSGI service bundle with Bundle-Version as "1.0.0" in which i have exported this particular package "com.example.test" and I have a OSGI web client where i am importing this package with version as "[1.0.0,2.0.0]" (i.e)
> Import-Package:com.example.test;version:[1.0.0,3.0.0]. Now when i start the client bundle after the service bundle I am getting this exception:
> 13:21:36,952 WARN [org.jboss.as.osgi] (MSC service thread 1-10) JBAS011910: Can
> not resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=com.example.test, version=[1.0.0,2.0.0]},[TestServlet:0.0.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, 4 months
[JBoss JIRA] (JBOSGI-624) Bundle importing the package of multiple versions isn't supported
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-624?page=com.atlassian.jira.plugin... ]
Thomas Diesler resolved JBOSGI-624.
-----------------------------------
Resolution: Rejected
This fundamental functionality is verified by our internal test suite and the OSGi TCK. Perhaps you are not defining the package capability version on the package directive
> Bundle importing the package of multiple versions isn't supported
> -----------------------------------------------------------------
>
> Key: JBOSGI-624
> URL: https://issues.jboss.org/browse/JBOSGI-624
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Hari Ohm Prasath
> Assignee: Thomas Diesler
> Labels: OSGI
>
> I have a OSGI service bundle with Bundle-Version as "1.0.0" in which i have exported this particular package "com.example.test" and I have a OSGI web client where i am importing this package with version as "[1.0.0,2.0.0]" (i.e)
> Import-Package:com.example.test;version:[1.0.0,3.0.0]. Now when i start the client bundle after the service bundle I am getting this exception:
> 13:21:36,952 WARN [org.jboss.as.osgi] (MSC service thread 1-10) JBAS011910: Can
> not resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=com.example.test, version=[1.0.0,2.0.0]},[TestServlet:0.0.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, 4 months
[JBoss JIRA] (JBOSGI-614) Allow Maven URLs to be configured to resolve external bundles
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-614?page=com.atlassian.jira.plugin... ]
Thomas Diesler updated JBOSGI-614:
----------------------------------
Fix Version/s: JBossOSGi 1.2.0
> Allow Maven URLs to be configured to resolve external bundles
> -------------------------------------------------------------
>
> Key: JBOSGI-614
> URL: https://issues.jboss.org/browse/JBOSGI-614
> Project: JBoss OSGi
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Repository
> Affects Versions: Continuing
> Environment: All
> Reporter: Ulrich Romahn
> Assignee: Thomas Diesler
> Priority: Critical
> Fix For: JBossOSGi 1.2.0
>
>
> Currently, JBoss OSGi allows to provide a Maven URI for a package which will then be resolved by the deployer according to the following rules:
> 1. check if the artifact is present in a local Maven repo (.m2)
> 2. if not, download the artifact from a remote Maven repo
> Currently, the class MavenArtifactRepository has two Maven repository URLs hardcoded:
> JBOSS_NEXUS_BASE = "http://repository.jboss.org/nexus/content/groups/public";
> MAVEN_CENTRAL_BASE = "http://repo1.maven.org/maven2";
> It should be possible to configure those URLs using some configuration mechanism. This is especially important in a real production environment where access to external URLs may be blocked by a firewall and an internal Nexus repo should be used to proxy a "stable set" of artifacts to be used for production.
> The following configuration options should be possible:
> 1. as it is right now
> 2. switch off external resolution completely. Only artifacts currently present on the local filesystem (.m2) should be resolved and loaded
> 3. Configure Maven URLs in addition to the hardcoded ones above
> 4. Configure Maven URLs as complete replacements to the hardcoded ones above
--
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, 4 months
[JBoss JIRA] (JBOSGI-625) Start level not valid message
by Daniel Chapman (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin... ]
Daniel Chapman updated JBOSGI-625:
----------------------------------
Issue Type: Bug (was: Feature Request)
> Start level not valid message
> -----------------------------
>
> 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
>
> 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, 4 months
[JBoss JIRA] (JBOSGI-625) Start level not valid message
by Daniel Chapman (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin... ]
Daniel Chapman commented on JBOSGI-625:
---------------------------------------
K I've found a way to recreate the issue consistently - found this while trying to get infinispan capabilities added to OSGI SubSystem.
So with a clean 7.1.3.Final EAP 6.0.1 Runtime environment - edit Standalone-full.xml osgi subsystem for following capabilities:
<capability name="javax.servlet.api:v25"/>
<capability name="javax.transaction.api"/>
<capability name="org.apache.felix.log" startlevel="1"/>
<capability name="org.jboss.osgi.logging" startlevel="1"/>
<capability name="org.apache.felix.configadmin" startlevel="1"/>
<capability name="org.jboss.as.osgi.configadmin" startlevel="1"/>
<capability name="org.jboss.marshalling"/>
<capability name="org.jboss.marshalling.river"/>
<capability name="org.jgroups"/>
<capability name="sun.jdk"/>
<capability name="javax.cache:cache-api:0.5"/>
<capability name="org.apache.aries:org.apache.aries.util:1.0.0"/>
<capability name="org.apache.aries.proxy:org.apache.aries.proxy:1.0.0"/>
<capability name="org.apache.aries.blueprint:org.apache.aries.blueprint:1.0.0"/>
<capability name="org.infinispan:infinispan-core:5.1.8.Final-redhat-1"/>
Start server - go into OSGI Console and start all the bundles. Successfully puts the checkmark next to all of them. Server restart looks good and all bundles still in started state.
Now stop server, add capability:
<capability name="org.infinispan:infinispan-cdi:5.1.8.Final"/>
Note: I chose 5.1.8.Final because that is what ships in modules dir of eap 6.0.1.
Server starts with bundle in installed state. Go into console - start the bundle, all hell breaks loose. Primary error is with missing javax.cache [0.4,1):
Caused by: org.osgi.service.resolver.ResolutionException: Unable to resolve HostBundleRevision[org.infinispan.cdi:5.1.8.Final]: missing requirement AbstractPackageRequirement[atts={osgi.wiring.package=javax.cache, version=[0.4,1)},[org.infinispan.cdi:5.1.8.Final]]
Which as you could see before I was able to have javax.cache started successfully before adding infinispan-cdi capability.
Now here's the recreate part... restart server. Blueprint disappeared. Looks installed, but not listed and not startable on console. Even after you remove the infinisipan-cdi capability. At one point I could see blueprint in the console without checkmark, but in trying to start it nothing happens, no log msgs. Just refreshes console.
I am able to fix this by blowing away the standalone/data and standalone/tmp directory... haven't done further research into which one causes problem.
So this issue is with funky starting/stopping and not being able to recover properly. But I wouldn't mind if I could get some help on enabling infinispan-cdi while we're at it.
Dan C.
> 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
11 years, 4 months