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. 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 was confused by the subject line, which suggested you wanted to apply the "reference:" semantics (ie. not copying the contents but accessing it directly) to non-"file:" schemes. Changing it from an exception to a message is OK with me - anyone else want to chip in? Thanks, > Sahoo > -- Cheers, Stuart
