cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <ralph.go...@dslextreme.com>
Subject Re: Cocoon and Sling
Date Wed, 08 Apr 2009 13:54:53 GMT
I think it makes sense to evolve Cocoon to have a central portion of  
it revolve around pipeline processing and various ways of doing it.   
It would make sense to just come to one place rather than to have to  
go to two.


On Apr 7, 2009, at 3:32 AM, Juan José Vázquez Delgado wrote:

> Hi all,
>
> As discussed in a previous thread [1], some people think it would be a
> good idea to take advantage of Cocoon´s pipelining and Sling request
> processing capabilities working together.
>
> We (Sling team) have implemented a first approach to this cooperation
> using Cocoon 3 pipeline engine [2] and the W3C XProc recomendation [3]
> in order to specify the pipelines to be performed. At least in the
> beginning, the Cocoon sitemap concept has been discarded because of
> quite overlapping between this one and Sling resource resolution.
>
> The code is available here [4] and details about how it works here  
> [5].
>
> From now on, I wonder whether Sling is the right place to keep on
> implementing W3C XProc or it´s Cocoon instead. Is this stuff
> interesting to Cocoon community and team?.
>
> Regards,
>
> Juanjo.
>
> [1] http://markmail.org/message/owefsfj4eqbc4ifq#query:OSGi 
> %20integration
> [2] http://cocoon.apache.org//3.0/
> [3] http://www.w3.org/TR/xproc/
> [4] http://svn.apache.org/repos/asf/incubator/sling/trunk/contrib/scripting/xproc/
> [5] http://cwiki.apache.org/confluence/display/SLINGxSITE/XSLT+Processing+Pipeline


Mime
View raw message