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
Investigate lazy bundle activation for runtime bundles
------------------------------------------------------
Key: JBOSGI-105
URL: https://jira.jboss.org/jira/browse/JBOSGI-105
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Runtime
Reporter: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta3
OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked into.
In theory this should bring startup time very close to boot time. i.e. the 'all' profile might start in < 1sec
If this is true we can put the web console into the 'default' profile without negatively effecting the startup time.
--
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
Implements URLStreamHandlerService
----------------------------------
Key: JBOSGI-75
URL: https://jira.jboss.org/jira/browse/JBOSGI-75
Project: JBossOSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Through the URLStreamHandlerService bundles can provide their own URL stream and content handlers
http://www.osgi.org/javadoc/r4v41/org/osgi/service/url/URLStreamHandlerSe...
Use this instead of setting the sysprop
java.protocol.handler.pkgs=org.jboss.net.protocol|org.jboss.virtual.protocol
Felix-1.6.0 defaults to
private static final String DEFAULT_STREAM_HANDLER_PACKAGE = "sun.net.www.protocol|com.ibm.oti.net.www.protocol|gnu.java.net.protocol|wonka.net|com.acunia.wonka.net|org.apache.harmony.luni.internal.net.www.protocol|weblogic.utils|weblogic.net|javax.net.ssl|COM.newmonics.www.protocols";
--
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
Implement persistent file storage
---------------------------------
Key: JBOSGI-207
URL: https://jira.jboss.org/jira/browse/JBOSGI-207
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 Alpha3
Verify that BundleContext.getDataFile("config") creates a directory in the server data directory
--
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
Handle potential bundle:// protocol with VFS
--------------------------------------------
Key: JBOSGI-201
URL: https://jira.jboss.org/jira/browse/JBOSGI-201
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jboss-osgi-microcontainer
Affects Versions: JBossOSGi 1.0.0 Beta4
Reporter: Ales Justin
Assignee: Ales Justin
Fix For: JBossOSGi 1.0.0 Beta5
We should be able to handle bundle:// protocol.
e.g. bundle://<bundle_id>/<resource_path>
--
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