Andrew Stevens wrote:
or in your pipeline
Then implement Parameterizable. The conf parameter will be passed to
the parameterize method.
Or finally in your pipeline do:
I think you'll find that should be map:transform, not map:transformer...
Andrew.
Of course. Thanks for
From: Ralph Goers <[EMAIL PROTECTED]>
Date: Sun, 20 Nov 2005 19:03:02 -0800
Stefan Pietschmann wrote:
The elements in the pipeline shall have attributes like
I don't believe you can do that. Instead you need to either do:
src="com.whatever.MyTransformer">
someID
No actually you got it right, but the point is that every element can have
that attribute, so I'd have to write such an action around every element in
the pipeline. We have quite a long pipeline, so this seems a bit bulky to me
and I'd want a more elegant solution.
Stefan
| -Ursprüngliche Na
Stefan Pietschmann wrote:
The elements in the pipeline shall have attributes like
I don't believe you can do that. Instead you need to either do:
src="com.whatever.MyTransformer">
someID
Then implement the configurable interface and int the configure method
d
Thank you for your quick response :)
| You should create a component that implements the required Avalon
| interfaces and then declare it in cocoon.xconf. You will need to assign
| it a role (faily simple - look at other components to see how they do
| it). The code that uses the component then ca
