cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20088] - XIncludeTransformer: xml:base does not work with Cocoon's pseudo protocols
Date Thu, 22 May 2003 21:31:18 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20088>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20088

XIncludeTransformer: xml:base does not work with Cocoon's pseudo protocols





------- Additional Comments From bruno@outerthought.org  2003-05-22 21:31 -------
Thinking a bit more about this: since the format of hierarchical URL's is
standarized, it is not necessary to move this logic to individual sources. We
can leave it in the SourceResolver.

The only reason to move it would be for the cocoon and context protocols. But
since these are really exceptional cases, I'd consider hardcoding them in the
SourceResolver.

As for the use of java.net.URL: as said before, this class only works for
protocols supported by the JDK. Since cocoon has its own mechanisms for
registering new protocols, and since we would need to implement an URL-parsing
class anyhow to handle the cocoon and context protocols, I think we'd better
have our own code for this.

For the SourceHandlerImpl class pointed out by Vadim: the concept was indeed
there, but e.g. the cocoon source resolved relative URL's simply by
concatenating the strings. I think we can do better.

All the above IMHO, as always ;-)

Mime
View raw message