Grzegorz Kossakowski wrote:
Daniel Fagerstrom pisze:
What is most complicated (and something we maybe don't have to care
about), is making the right component parameters available while
executing a pipeline.
Can you explain what are those 'component parameters' to be made available
during pipeline execution? Do they exist in 2.1?
To get it right we need something like:
Generator -> EnvironmentChanger -> Transformer -> EnvironmentChanger
-> ... -> EnvironmnetChanger -> Serializer
where the EnvironmentChanger wraps the XMLConsumer for the next
component and pops the current component parameters and push the ones
for the next component for each SAX event. See
o.a.c.environment.internal for some such code. There is also a fair
amount of environment changing code in pipelines in the abandoned VPC
code
http://svn.apache.org/repos/asf/cocoon/whiteboard/virtual-processing-components/.
Kind of complicated I'm afraid. But handling of sitemap component
parameters is one of the more complicated areas in Cocoon.
WDYT?
It looks *very* heavy, especially since it's done for *each* sax event on *each*
step of the pipeline. I'd like to avoid doing stuff like this as far as possible.
Vadim
