[jboss-dev-forums] [JBoss OSGi Development] - Re: Handle potential bundle:// protocol with VFS
alesj
do-not-reply at jboss.com
Fri Nov 13 03:54:45 EST 2009
"thomas.diesler at jboss.com" wrote : Anybody can do
|
| | InputStream is = sysContext.getBundle(someId).getResource("/some-resource.txt").openStream()
| |
|
No.
e.g.
* I don't have access to system bundle / context -- remember your KernelLocator hack ;-)
* I don't wanna depend on OSGi api -- my code is 100% portable
"thomas.diesler at jboss.com" wrote :
| What is the use case where the URL format actually matters?
|
OK, you could use direct vfsx protocol, but then. like I alredy said, you're by-passing bundle's restrictions.
Instead you pass around bundle protocol based url, knowing the restrictions apply.
User could still of course do direct access, but the framework shouldn't encourage him to do so,
hence a custom protocol that works more closely with the framework.
Currently this is a simple prototype, but I guess this could/will come in handy when you need to pass resource access around
to other pieces of the OSGi env; e.g. compendium, your interceptors, ...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265428#4265428
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4265428
More information about the jboss-dev-forums
mailing list