cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <>
Subject [jira] [Commented] (COCOON3-102) The org.apache.cocoon.sax.component.XIncludeTransformer is not cacheable
Date Wed, 20 Jun 2012 15:51:44 GMT


Francesco Chicchiriccò commented on COCOON3-102:

Javier, I've actually tried to port the approach you're following for COCOON3-100 to XIncludeTransformer,
but it seems to me that it is unsuccessful as well.

With your approach, the first call to constructCacheKey() will return a CompoundCacheKey that
will be populated with URLs during execution; however, I've experimented that during second
call, CachingPipeline will not be able to recognize the CacheKey in Cache as the same returned
by a new call to constructCacheKey() and this will result in a new entry in the Cache, completely
unrelated with the first.

Your approach seems very close to C2.1's and C2.2's but I guess that there it used to be working
because components were recycled while in C3 - due to Spring's prototype scope - are always
> The org.apache.cocoon.sax.component.XIncludeTransformer is not cacheable
> ------------------------------------------------------------------------
>                 Key: COCOON3-102
>                 URL:
>             Project: Cocoon 3
>          Issue Type: Improvement
>          Components: cocoon-sax
>    Affects Versions: 3.0.0-alpha-3
>            Reporter: Simone Tripodi
>            Assignee: Francesco Chicchiriccò
>             Fix For: 3.0.0-beta-1
>         Attachments: COCOON3-102.patch
> The org.apache.cocoon.sax.component.XIncludeTransformer is not a cacheable pipeline component,
it would be great to implement it as cacheable

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message