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 20:37:34 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 torstenknodt@datas-world.de  2003-05-22 20:37 -------
First, sorry not to mention you. I've specified your idea a little more. 
 
I agree that breaking the interface is a problem. 
Implementing a basic way is not needed really. The implementations can simple 
use java.net.URL. Only those who can't use this, have to implement it on their 
own. 
Another issue for me, is that SourceResolver already has an interface for 
this. But having support for schemes in the resolver is the wrong place. 
Perhaps this is our solution. When we think about what we want to do is that 
Sources are also a Resolver. So why not implementing SourceResolver in the 
Sources, which want to support it. Then the, lets call it root SourceResolver, 
only has to traverse sources and use the original method for Sources not 
implementing the right. If so, he also outputs a deprecation warning to the 
log. As the base URI, when calling the resolving function in the Source's, he 
uses a base of null. 
 
When I know how to implement it the right way, I'm thinking about 
volunteering, as I really need it. But let's see if I'm able to implement it.

Mime
View raw message