[
https://jira.jboss.org/jira/browse/JBOSGI-201?page=com.atlassian.jira.plu...
]
David Lloyd commented on JBOSGI-201:
------------------------------------
However this is done, it shouldn't use the host name field (recall the problems with
vfsmemory URLs). Personally I think the best solution would be to have a global VFS
location where bundles can be found by ID, e.g. file:///osgi/bundles/by-id/[id]/[path] in
VFS3 or the equivalent in VFS2.
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