DO NOT REPLY [Bug 31600] - [PATCH] Caching support for XIncludes

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31600>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31600





------- Additional Comments From oliver.powell@tvnz.co.nz  2005-09-16 04:37 -------
Copied from cocoon-users list:

Oliver Powell wrote:
it would be nice to use a standard-compliant include 
component. All we really need is for it to include 
the EventValidity we place on our initial data generator step. From 
the comments in bugzilla, it looks like your patch will do this.

Jason Johnston wrote:
> Yes it should, if I'm understanding your setup.  Any included source that 
> provides a SourceValidity will be added to the transformer's aggregated 
> validity, and all the pieces will be checked for validity each successive time 
> the pipeline is set up.

Oliver Powell wrote:
Another question about the cacheable XIncludeTransformer. I assume the 
Xpath parameter is used to form the cache key?

> Actually, no, but it shouldn't matter... the thinking is that if the source 
> file as a whole is valid then any fragments within it will also be valid.
>
> Come to think of it, the keys for the individual sources aren't even used; we 
> just get all the Validity objects from all the sources and create a 
> MultiSourceValidity from them, which is used as the transformer's validity.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.