cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <>
Subject Re: [RT] Cocoon Integration Model
Date Mon, 15 Jul 2002 14:55:25 GMT
<snip content="increadibly relevant stuff I totally agree with"/>

>Cocoon can definitely use its own blueprint.  A Cocoon Application
>Blueprint is an essential document that we need.  There are two ways
>of using Cocoon: integrated in with a traditional J2EE environment,
>and standalone.  The blueprint will define exactly what part of the
>puzzle Cocoon supports.  It will also define which patterns work well,
>why they work well, and the antipatterns which suck all your time.
I'm doing my part. 
is intended
to be a sample webapp.  I don't want to do a total petshop as I think it 
over does it in hopes of working
every technology into it.

Next I plan to do a write up.

 Next, I hope you smart people will help refactor it into best practices.

Its about 3/4 finished.  Nicola is writing a skin for it, I'm trying to 
figure out how to pass a freaking request parameter
into an xml form from outside of the form, then I should be able to nail 
the rest of it out.

All the code minus the branding will be donated to cocoon ASL of course.

Lastly, the site will actually go live so it will be a bit more than the 

>A side-affect, and general improvement will be that Cocoon will begin
>to be shaped by the blueprint.  The proposals that are given will be
>there to enhance the model, or to overcome shortcomings.  As we state
>*how* Cocoon should be used, it's development effort will follow that
>pattern.  As of right now, the oppinions on how to get the best out
>of Cocoon are as varied as the number of developers on the list.

>"They that give up essential liberty to obtain a little temporary safety
> deserve neither liberty nor safety."
>                - Benjamin Franklin
>To unsubscribe, e-mail:
>For additional commands, email:

To unsubscribe, e-mail:
For additional commands, email:

View raw message