Initial OSGi / CDI Integration
-------------------------------
Key: JBOSGI-445
URL: https://issues.jboss.org/browse/JBOSGI-445
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Other
Reporter: Thomas Diesler
Assignee: David Bosschaert
Fix For: JBossOSGi 1.0.x
Provide an example test that shows CDI integration
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Initial Enterprise OSGi JPA implementation
------------------------------------------
Key: JBOSGI-260
URL: https://jira.jboss.org/jira/browse/JBOSGI-260
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jboss-osgi-jpa
Reporter: Thomas Diesler
Fix For: JBossOSGi 1.0.x
--
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
OSGi Core 4.3 support
---------------------
Key: JBOSGI-497
URL: https://issues.jboss.org/browse/JBOSGI-497
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Core Framework
Affects Versions: Core Framework 1.0.0
Reporter: David Bosschaert
Assignee: David Bosschaert
Make the framework Core 4.3 compliant
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Make resolver core 4.3 compliant
--------------------------------
Key: JBOSGI-498
URL: https://issues.jboss.org/browse/JBOSGI-498
Project: JBoss OSGi
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: jboss-osgi-jmx
Affects Versions: JBossOSGi 1.0.0
Reporter: David Bosschaert
Assignee: David Bosschaert
Update the Felix Resolver to be core 4.3 compliant
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Thomas Diesler created JBOSGI-520:
-------------------------------------
Summary: 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: Enterprise Services
Reporter: Thomas Diesler
Assignee: David Bosschaert
Fix For: JBossOSGi 1.0.2
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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Thomas Diesler created JBOSGI-525:
-------------------------------------
Summary: Define and implement a repository content exchange format
Key: JBOSGI-525
URL: https://issues.jboss.org/browse/JBOSGI-525
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Enterprise Services
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.2
The repository spec defines an XML based exchange format. Provide an initial impl for 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
Run OSGi CT with AS7
--------------------
Key: JBOSGI-499
URL: https://issues.jboss.org/browse/JBOSGI-499
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: David Bosschaert
Assignee: David Bosschaert
The OSGi CT is currently run with the JBoss OSGi framework standalone. It should also be possible to run the CT with the AS7 integration.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/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