April 2011 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-179) Setup JBoss OSGi on jboss.org

by Thomas Diesler (JIRA)

Setup JBoss OSGi on jboss.org ----------------------------- Key: JBOSGI-179 URL: https://jira.jboss.org/jira/browse/JBOSGI-179 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta5 The current homepage is http://www.jboss.org/community/wiki/JBossOSGi another good source of information is http://jbossosgi.blogspot.com/ The entry point however should be a project on jboss.org http://www.jboss.org/projects/matrix -- 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

12 years, 11 months

2
13
0 / 0

[JBoss JIRA] Created: (JBOSGI-192) Access an OSGi service from EJB3

by Thomas Diesler (JIRA)

Access an OSGi service from EJB3 -------------------------------- Key: JBOSGI-192 URL: https://jira.jboss.org/jira/browse/JBOSGI-192 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Integration (JBoss) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Allow access of OSGi services from a SLSB and possibly others. -- 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

12 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-313) OSGi service invocation from EE6 WebApp

by Thomas Diesler (JIRA)

OSGi service invocation from EE6 WebApp --------------------------------------- Key: JBOSGI-313 URL: https://jira.jboss.org/jira/browse/JBOSGI-313 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 Please investigate how we access an OSGi service from an existing EE6 webapp. This will eventually boil down to class space consistency at a layer common to both programming models. For the Native Framework this is related to the idea of ServiceMix. Please also investigate if this can be done with existing 3rd party frameworks (i.e. Felix or Equinox) -- 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

12 years, 11 months

1
3
0 / 0

[JBoss JIRA] Moved: (JBOSGI-441) Allow for OSGi style Class Filtering

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-441?page=com.atlassian.jira.plugin... ] Thomas Diesler moved MODULES-83 to JBOSGI-441: ---------------------------------------------- Project: JBoss OSGi (was: JBoss Modules) Key: JBOSGI-441 (was: MODULES-83) Affects Version/s: (was: 1.0.0.Beta13) Security: Public Fix Version/s: JBossOSGi 1.0.0 JBossOSGi 1.0.x (was: 1.0.0.Beta18) > Allow for OSGi style Class Filtering > ------------------------------------ > > Key: JBOSGI-441 > URL: https://issues.jboss.org/browse/JBOSGI-441 > Project: JBoss OSGi > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: David Lloyd > Fix For: JBossOSGi 1.0.0, JBossOSGi 1.0.x > > > 3.6.7 Class Filtering > An exporter can limit the visibility of the classes in a package with the > include and exclude directives on the export definition. The value of each of > these directives is a comma-separated list of class names. > The following example shows an export statement, and a list of files with > their visibility status. > Export-Package: com.acme.foo; include:="Qux*,BarImpl";exclude:=QuxImpl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-440) "VFS was unable to set the URLStreamHandlerFactory. This will have unpredictable results"

by David Bosschaert (JIRA)

"VFS was unable to set the URLStreamHandlerFactory. This will have unpredictable results" ------------------------------------------------------------------------------------------ Key: JBOSGI-440 URL: https://issues.jboss.org/browse/JBOSGI-440 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-vfs Affects Versions: JBossOSGi 1.0.0 Beta10 Reporter: David Bosschaert Priority: Minor When the OSGi subsystem is triggered in AS the following warning shows up. I think it's harmless but it looks worrying and unprofessional. 10:27:50,419 WARN [org.jboss.vfs] (MSC service thread 1-3) VFS was unable to set the URLStreamHandlerFactory. This will have unpredictable results -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-438) Exception when starting Blueprint component

by David Bosschaert (JIRA)

Exception when starting Blueprint component ------------------------------------------- Key: JBOSGI-438 URL: https://issues.jboss.org/browse/JBOSGI-438 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-blueprint Affects Versions: JBossOSGi 1.0.0 Beta10 Environment: Fedora 14, JBoss OSGi inside AS7 Reporter: David Bosschaert Attachments: ascii-pics-api-bundle-1.0.0-SNAPSHOT.jar, ascii-pics-consumer-bundle-1.0.0-SNAPSHOT.jar When starting my Blueprint component an exception appears on the console. The attached bundles can be installed to reproduce. This is the exception: (pool-11-thread-1) Unable to start blueprint container for bundle ascii-pics-consumer-bundle: java.lang.IllegalArgumentException: Invalid object class in: [org.osgi.service.blueprint.container.BlueprintContainer] at org.jboss.osgi.framework.bundle.ServiceState.<init>(ServiceState.java:109) at org.jboss.osgi.framework.plugin.internal.ServiceManagerPluginImpl.registerService(ServiceManagerPluginImpl.java:175) at org.jboss.osgi.framework.bundle.AbstractBundleContext.registerService(AbstractBundleContext.java:300) at org.jboss.osgi.framework.bundle.BundleContextWrapper.registerService(BundleContextWrapper.java:119) at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerService(BlueprintContainerImpl.java:388) [BlueprintContainerImpl.class:] at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:324) [BlueprintContainerImpl.class:] at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:213) [BlueprintContainerImpl.class:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_20] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_20] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20] at java.lang.Thread.run(Thread.java:619) [:1.6.0_20] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
8
0 / 0

[JBoss JIRA] Created: (JBOSGI-405) Update to jboss-msc-1.0.0.Beta3

by Thomas Diesler (JIRA)

Update to jboss-msc-1.0.0.Beta3 ------------------------------- Key: JBOSGI-405 URL: https://jira.jboss.org/browse/JBOSGI-405 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.0.0 Beta10 This is currently failing for some service ref tests -- 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

13 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-409) Update to jboss-modules-1.0.0.Beta7

by Thomas Diesler (JIRA)

Update to jboss-modules-1.0.0.Beta7 ----------------------------------- Key: JBOSGI-409 URL: https://jira.jboss.org/browse/JBOSGI-409 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.0.0 Beta10 This is currently failing for some service ref tests -- 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

13 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-430) Upgrade to jboss-msc Beta5

by Thomas Diesler (JIRA)

Upgrade to jboss-msc Beta5 -------------------------- Key: JBOSGI-430 URL: https://jira.jboss.org/browse/JBOSGI-430 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta10 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-417) Move felix-framework to latest felix resolver

by David Bosschaert (JIRA)

Move felix-framework to latest felix resolver --------------------------------------------- Key: JBOSGI-417 URL: https://jira.jboss.org/browse/JBOSGI-417 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Bosschaert Once the felix resolver is updated (JBOSGI-404) the felix-framework component also needs to be updated. -- 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

13 years, 1 month

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues April 2011