This was not a bug. I observed that caching pipelines produce this only if they end in an XML serialization. This behaviour was strange and misleading. However, the cause was the 'cacheKey' the generator returned was the "simpleCacheKey" which had been sitting there from the examples. Replacing SimpleCacheKey by ParameterCacheKey solved the problem. Have a look at the routine! Maybe this removes your problem. I suggested to replace this in the examples.
Hope this helps, Jos On Mon, 2010-03-22 at 21:33 +0100, Johannes Lichtenberger wrote: > I think it could be related to the bug Jos Snellings posted some time > ago where always the first execution in pipeline with type="xml" > serializers is beeing executed. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org > For additional commands, e-mail: users-h...@cocoon.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
