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 28724] - FragmentExtractor always returns same fragment
Date Sat, 08 May 2004 02:32:29 GMT
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=28724>.
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=28724

FragmentExtractor always returns same fragment





------- Additional Comments From joerg.heinicke@gmx.de  2004-05-08 02:32 -------
You can do this easily yourself for the moment by removing
CacheableProcessingComponent interface.

Why should a "generator not be cachable per se"? If the generator is not
cacheable the complete pipeline is not cacheable! This is why I would like to
let the FragmentExtractorGenerator being cacheable.

Has anybody an idea how to do 2). And does HashUtil.hash(SAXFragment) work for 4)?

Mime
View raw message