Niclas Hedhman wrote:
On Thursday 18 August 2005 19:19, Daniel Fagerstrom wrote:
AFAICT, the specification (R3) does not require the returned URL to be
globally resolvable,
If you mean globally resolvable within the current OSGi instance I
interpret 4.23.3.11 in the spec as that the returned URL should be
resolvable in any bundle that has the right AdminPermission.
I mean "Globally" as serialize the URL to a String, send it by mail to another
OSGi instance on the other side of the planet to an OSGi instance (which have
the protocol(s) installed) and open the stream.
Ok, it is certainly not global in that sense.
I don't think that is required, which means that a jar:file:/// URL could be
returned by the framework.
Sure
Note that Oscar doesn't have the org.osgi.service.url installed by default, so
it does not use bundle: AFAICT.
bundle: seem to be Knopflerfish specific. The conclusion is that as long
as the "instalation repository", not is standardized in OSGi one have to
be careful while handling URLs from the different resource resolvers in
OSGi.
OT --> Hopefully improve our (esp your) understanding, which somewhere down
the line probably pays off in better stuff in Cocoon :o).
If we succeed to remember this discussion ;) it will save us some time
when we migrate from Knopflerfish to Oscar.
/Daniel
