cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@sundn.de>
Subject AW: cvs commit: xml-cocoon2/webapp/docs/samples samples.xml
Date Wed, 23 May 2001 11:13:55 GMT
> Giacomo Pati wrote:
>
> Quoting Carsten Ziegeler <cziegeler@sundn.de>:
> > > Giacomo Pati wrote:
> > >
> > > Quoting cziegeler@apache.org:
> > >
> > > >   Index: cocoon.xconf
> > > >
> > ===================================================================
> > > >   RCS file: /home/cvs/xml-cocoon2/webapp/cocoon.xconf,v
> > > >   retrieving revision 1.5
> > > >   retrieving revision 1.6
> > > >   diff -u -r1.5 -r1.6
> > > >   --- cocoon.xconf	2001/05/16 10:15:49	1.5
> > > >   +++ cocoon.xconf	2001/05/23 09:40:53	1.6
> > > >   @@ -156,8 +156,6 @@
> > > >      <!-- this component is used as a PoolController for the sitemap
> > > > component pools  -->
> > > >      <pool-controller
> > > >
> > > class="org.apache.avalon.excalibur.component.DefaultComponentPoolC
> > > ontroller"/>
> > > >
> > > >   -  <sax-connector
> > > >
> > class="org.apache.cocoon.components.saxconnector.CIncludeSAXConnector"/>
> > > >   -
> > >
> > > Instead of removing stuff from the cocoon.xconf file wouldn't it
> > > be wiser to put
> > > them into a comment (this applies to the cocoon.rolses as well)?
> > >
> > Generally speaking you are right.
> >
> > But as we have decided to remove the transparent content aggregation and
> > use transformers instead I think it is rather dangerous to have this
> > line
> > even comment there.
> >
> > The next step is to remove the XInclude and the CInclude connectors and
> > create the transformers instead.
>
> I wasn't able to follow the list these days closely. Do you have
> a way how a
> Transformer can request internal C2 pipelines yet?
>
The new SourceResolver is able to use the URLFactory using a component
called URLResolver. This URLResolver is instantiated by the handler of the
sitemap.
So it should be possible to pass the handler to the URLResolver and from
there on to the URLFactory.

I didn't have time to have a closer look at this, but I will do it if I
have time again. All I know now is: It is possible with the current
architecture.

Carsten

> Giacomo
>
> >
> > If we have a usuable SAXConnector (for debugging or profiling for
> > example)
> > then we should add the line to the cocoon.xconf and comment it.
> >
> > Carsten
> >
> > > Giacomo
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message