You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@sundn.de> on 2001/04/19 14:44:14 UTC
AW: cvs commit: xml-cocoon/src/org/apache/cocoon/xml ContentHandlerWrapper.java
Wow, great work, Giacomo!
One simple question, which serializer should I use for the aggregated parts?
E.g, should the pipeline for "header" have the xml serializer at the end or does
this play no role (I already tried to aggregate pipelines which serialize as
html and it worked)?
Carsten
Open Source Group sunShine - b:Integrated
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de mailto: cziegeler@sundn.de
================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: AW: cvs commit: xml-cocoon/src/org/apache/cocoon/xml
ContentHandlerWrapper.java
Posted by giacomo <gi...@apache.org>.
On Thu, 19 Apr 2001, Carsten Ziegeler wrote:
> Wow, great work, Giacomo!
>
> One simple question, which serializer should I use for the aggregated parts?
Doesn't matter. The serializer (i.e. StreamPipeline) are thrown away.
For the aggregator only the EventPipeline matters.
> E.g, should the pipeline for "header" have the xml serializer at the end or does
> this play no role (I already tried to aggregate pipelines which serialize as
> html and it worked)?
Yes, the serializer is has no effect when the resource is used in a
aggregation.
BTW: Hold on a second because the Aggregator doesn't handle namespaces
correctly. I'm still fixing it.
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org