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.
so the is-logged attribute that is the critical change in your use-case is set inside an action. This could be the problem because cocoon evaluates the pipeline cache keys and validities *before* it executes any pipeline components.
You said in your previous email that you can't systematic reproduce the problem, this is wierd. Have you tried using a different validity than the CheckIntervalValidity like a NOPValidity.SHARED_INSTANCE for example (caches forever).
Jorg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
