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 13329] - merge XIncludeTransformer and CIncludeTransformer
Date Thu, 22 May 2003 13:20:07 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=13329>.
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=13329

merge XIncludeTransformer and CIncludeTransformer





------- Additional Comments From bruno@outerthought.org  2003-05-22 13:20 -------
How far can you go integrating the two?

I think that the result of the XInclude process on a document should be the same
whether you do the XInclude with Cocoon or with another XInclude-compliant
processor.

So adding a few attributes to the xi:xinclude element to control caching options
is pretty harmless, since that doesn't change the end-result.

OTOH, adding extra elements in the xi:include element to specify URL parameters
etc. will yield different results.

And BTW, what do you mean with "moving xpointer some stairs up"? It's already a
seperate, reusable package. You want to move it outside of Cocoon or something?

Mime
View raw message