Stuart McCulloch wrote:
2009/6/8 Sahoo <[email protected]>
Stuart McCulloch wrote:
I guess I'm not seeing why you want to use the reference: scheme with
non-file URLs?
do you just want to avoid copying the remote content locally or is there
another reason?
Good question. I want to modify the content as it is read. e.g., I want to
process the MANIFEST.MF by having my own URL handler for a custom protocol.
All these work as long as I don't use reference scheme.
Ah, ok - I think I understand now.
You want to have "reference:" in the URL and have Felix ignore it for
non-"file:" schemes.
Not really.
ie. log a warning / info / debug and continue as if the URL was not a
"reference:" instead
of throwing an exception as it currently does.
I just want Felix to read the content off the JarInputStream when it
encounters a non-file URL after reference:. Is there a reason why Felix
must copy? Is performance the reason? What if the custom url handler is
already backed by a JarFile object?
Let's put it this way. How can we have directory deployment of bundles
with support for content filtering?
Thanks,
Sahoo
