Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <446CE002.6030000@apache.org>
Date: Thu, 18 May 2006 22:58:42 +0200
From: Sylvain Wallez <sylvain@apache.org>
User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Flowscript in Spring
References: <446C62BB.1080608@apache.org>
 <25EEE697-2368-4B08-9895-4B62B810E20B@betaversion.org>
In-Reply-To: <25EEE697-2368-4B08-9895-4B62B810E20B@betaversion.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Pier Fumagalli wrote:
> On 18 May 2006, at 13:04, Sylvain Wallez wrote:
>
>> FYI: http://www.theserverside.com/news/thread.tss?thread_id=40522
>
> ??? Isn't Spring supposed to be a container manager a-la Avalon ???

The component container is the original Spring, which has grown a lot to
be more a galaxy of subprojects. Spring has the container, lots of
components and helper classes (kindof Excalibur) and even a webapp MVC
framework and a page-flow engine named webflow.

This JS webflow doesn't seem to be part of the official Spring project,
and is a reaction to the huge pile of XML that's needed to use webflow.
The result is really Cocoon's flowscript adapted to a different
environment [1], just like there's already has been Struts-flow [2].

Once again, our ideas are reused. We can be proud to have opened new
ways in webapp development, but it would be better if our components
rather than our ideas were reused, and unfortunately this really isn't
easy because of the very specific APIs used in Cocoon's foundations,
that once weere so useful but now seem like a ball and chain...

Sylvain

[1] http://rhinoinspring.sourceforge.net/webflow.html
[2] http://struts.apache.org/struts-sandbox/struts-flow/

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