Aggregation & Caching (again)

[David LAGARDERE <dl...@yahoo.fr>]

Hi.

I still don't know why my content is generated
even if my part elements are all cacheable.
The key and validity of my aggregated
elements remain the same and I can see in the log
that they are holded in memory.
So what did I do wrong ? Could
somebody give me a clue on the algorithm which is
employed to generate the validity of a
ContentAggregator ? I've been investigating throught 
the source but it didn't solve my problem.

Thanks in advance.

David

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>

Re: Aggregation & Caching (again)

[Vadim Gritsenko <va...@verizon.net>]

David LAGARDERE wrote:

>Hi.
>
>I still don't know why my content is generated
>even if my part elements are all cacheable.
>

All transformers must be cacheable as well for pipeline to be cacheable.

Vadim



>The key and validity of my aggregated
>elements remain the same and I can see in the log
>that they are holded in memory.
>So what did I do wrong ? Could
>somebody give me a clue on the algorithm which is
>employed to generate the validity of a
>ContentAggregator ? I've been investigating throught 
>the source but it didn't solve my problem.
>
>Thanks in advance.
>
>David
>  
>




---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>