Re: Caching and aggregate

[Jorg Heymans]

confusing :|

Oscar Picasso wrote:

Alternatively (and maybe more easily), are you in a position to retrieve 
2.1.5 HEAD and test your case there?
Same problem with 2.1.5 HEAD.
ok then that should rule out my suspicion about the old bug resurfacing 
again.
The log-on component is a VelocityGenerator subclass.
The key is based on some request attributes that are
chosen upon configuration of the component.
should work, i have a similar cachingrequestgenerator in 2.0.4
example:
<map:generator usecache="false" label="content"
               logger="xenata"  caching-attributes="is-logged"
               name="loggin-velocity"
              
src="org.apache.cocoon.generation.RequestAttributesCacheableVelocityGenerator"/>

The relevant attribute is 'caching-attributes'
which means in this case that the RequestAttributesCacheableVelocityGenerator
will look for a request attribute named 'is-logged' to compute
the key. (It uses also the name of the velocity template).
so this caching-attributes is a comma separated list of both request and 
pipeline-set attributes that should be used during key calculation?

The 'is-logged' attribute is a Boolean that is set upper in the pipeline 
inside an action. The action sets correctly the 'is-logged'
attribute. 

In RequestAttributesCacheableVelocityGenerator you set String[] 
cachingAttributeNames in configure(), are you aware that configure is 
called only once during component setup and never afterwards? Could this 
be affecting your logic?

Jorg

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]