Hi,
there is a class org.apache.cocoon.EngineWrapper. I found
it in the cocoon java api doc.
I'm going to use it in a screen class, which extends the
org.apache.turbine.modules.screens.TemplateScreen.
In this class I'll implement the method
"public ConcreteElement buildTemplate( RunData data )"
and return the output I receive from cocoon.
Do you think that approach is to dirty ?
Thanks,
Thomas
> -----Original Message-----
> From: Leon Messerschmidt [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, May 13, 2001 2:26 PM
> To: [EMAIL PROTECTED]
> Subject: Re: turbine + cocoon
>
>
> Hi Thomas,
>
> I'm not so sure about the cocoon integration, but we're using Turbine with
> an xml + xsl approach together with Velocity. Basically it works the same
> as the HTML version of Velocity except that templates are xml and
> that we do
> an xsl translation at the end.
>
> It is checked into Turbine, although less well documented. If you need to
> get it up and running I could write some docs. (I need to do it sooner or
> later :-)
>
> ~ Leon
>
> > Hi,
> >
> > has someone already gathered any information how
> > to integrate cocoon into the turbine framework.
> >
> > I would like to use the xml + xsl approach to
> > develop the static pages of an application.
> >
> > Thomas
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
