Yes, Reinhard, I agree very much with the observation that everything
that influences the output must go in the cache key.
OK, I use the user group again, because I am convinced that this will be
of use to the whole cocoon community: here I go.
I write a cocoon Generator. It extends
Please put this message on hold. I might have expressed myself in haste.
First I need to perform another test!
Jos
On Tue, 2010-03-09 at 13:17 +0100, Jos Snellings wrote:
Yes, Reinhard, I agree very much with the observation that everything
that influences the output must go in the cache key.
It is herewith confirmed that pipelinecompont.setup() is called before
constructCacheKey! (see CachingPipeline.setup().
The nullpointerexception I observed stemmed from a class inheritance
(forgot super.setup() in one of the participating generators).
Cheers,
Jos
On Tue, 2010-03-09 at 13:25
Hi all,
I know you can call static java methods from xslt and even construct new java
objects. But that happens NOT to match my use case.
Short description of my use case:
I have a datasheetbuilder bean defined in my applicationContext:
bean id=datasheetBuilder
I managed to find a nice workaround actually.
Somewhere in the pipeline I need to determine image width and height based on
scanning someimage.eps boxdimension properties
So when I get to the point where I want to generate
image href=someimage.eps width=75 height=83/
I actually generate a
On Mon, 2010-03-08 at 19:15 +0100, Johannes Lichtenberger wrote:
On Mon, 2010-03-08 at 08:34 +0100, Reinhard Pötz wrote:
Johannes Lichtenberger wrote:
On Sat, 2010-03-06 at 13:19 +0100, Johannes Lichtenberger wrote:
On Sat, 2010-03-06 at 07:21 +0100, Jos Snellings wrote:
Johannes, you
