cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylv...@apache.org>
Subject Re: [RT] Modernizing CForms
Date Tue, 20 Mar 2007 15:33:22 GMT
Daniel Fagerstrom wrote:
> Sylvain Wallez skrev:

<snip/>

>> A very concrete example: within a Wicket application, we needed to have
>> areas of the screen be the result of the transformation of some XML
>> document. We ended up doing coding pipelines in plain Java. If Cocoon
>> had provided a simple way to use its pipeline machinery, we would have
>> used it.
>
> Although it could be even easier and most definitively should require
> less dependencies it is not that hard to use the pipeline standalone:
> http://svn.apache.org/repos/asf/cocoon/whiteboard/java-sitemap/src/main/java/org/apache/cocoon/javasitemap/JavaSitemapServlet.java.
>
>
> For the dependencies we have done some work on splitting up Cocoon so
> that you can use just the pipeline part (see
> http://svn.apache.org/repos/asf/cocoon/trunk/core/). The main thing
> left to do is to de-Avalonize a number of core components.

Very cool!

>> All this to say that by trying to address too many concerns, Cocoon
>> dilutes the message of where its strengths are, and leads potential
>> newcomers to simply look somewhere else.
>
> We clearly need to have a more focused message. But I think that
> saying that we should not provides a webapp framework anymore but just
> some components would be to go far to long. We need to find the right
> balance.
>
>> A way to address this would be to have several subprojects in the Cocoon
>> top-level project, ensuring a greater technical separation, giving a
>> clear view of the various features the top-level project provides and
>> thus allowing people to pick-up what they need, and ultimately use more
>> and more of what this project provides.
>
> We are going in this direction. Both the cocoon-spring-configurator
> and the cocoon-servlet-service-fw (and maybe some more) are intended
> to be separate Cocoon sub projects. Lots of work left to do though.

IMO this is key for the future of Cocoon: showing that it's not (or no
more) a take-it-all-or-nothing beast, but a component statck where you
can pick up only what you need.

Sylvain

-- 
Sylvain Wallez - http://bluxte.net


Mime
View raw message