cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: [RT] Cocoon Web Applications
Date Tue, 26 Feb 2002 09:37:51 GMT
Antti Koivunen wrote:
> 
> Stefano,
> 
> I agree with the objectives you described, but I'd be careful not to
> turn Cocoon into a package management tool. AIU, .wars and .ears were
> designed to be self-contained deployable archives, and as such, are
> quite useful for many things, such as rolling out new versions, moving
> from testing to QA, etc.
> 
> It's likely that many users will want to continue to prepackage their
> .wars (and .ears), but I agree that for Cocoon this process could be
> facilitated, possibly with something like 'CWA's.
> 
> Based on this, and other discussion on this list, I think it could be
> useful to have some kind of installation/configuration tool for Cocoon.
> It shouldn't be too difficult to implement with a clear definition of
> core libraries, optional modules and dependencies (within the same
> Cocoon distribution). At first, it could be a simple client app that
> just does the following:
> 
>    1. Download a set of files describing the Cocoon distribution.
>    2. Select the desired modules (in addition to the core fileset).
>    3. Check the dependencies (file-level, within the same distribution).
>    4. Create the directory structure and download the required files.
>    5. Create a sample sitemap and xconf for the selected modules.
> 
> The tool could of course also be used locally and it would be relatively
> easy to later add support for "CWA modules". Implementing the above
> should also be pretty straightforward. Would this be a good first step?

Well, yes, but that's not what I want.

What you describe above is a sort-of apt-get for cocoon. Sure, apt-get
is way cool, but it's a packaging solution, not a component model.

What I want is polymorphic behavior of webapp modules!

There is *no* technology in the world that gives me this for the web!
ASAIK, at least.

Sure, once you have polymorphic behavior for webapp modules, you have to
have some sort of 'package manager' (in the apt-get sense): doing it by
hand is a horrible task.

But a package manager alone would not something that would please my
search for a viable way to make cocoon web applications easily reused
between different projects.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------


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


Mime
View raw message