cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Irv Salisbury <>
Subject Re: Running cocoon as a war archive
Date Wed, 06 Jul 2005 05:40:43 GMT
Thank you for your comments.

I would say, yes, this would normally belong in  However, having been around the cocoon lists
for over 2 years now and my last 8 or 9 posts not getting answered on
the users list, I tend to pose the "hard" questions to dev.  (Yes I
view this as hard) Sorry if I have offended anyone.  I really wanted
the developers insight into the technical hurdles of doing this.  As
you might have seen from my weblogic posts (which went unanswered on
the users list), the dev list has a different take on things.  I
understand these are busy lists, and that also means there are
developers who do not answer on the users list.  This is a critical
time for this project and cocoon's place in it.  I would really like
it to work.

Once again, sorry.  I will pose the list to the users next time.  I
still welcome any and all thoughts on running cocoon as a war archive
versus as an expanded web directory.


On 7/5/05, Andrew Franz <> wrote:
> Irv Salisbury wrote:
> >I have always run cocoon as an expanded war directory.  Our current
> >customer is requesting we run as a war file.  Are there any resources
> >or problems people have found with this strategy?
> >
> >Thanks,
> >
> >Irv
> >
> >
> >
> >
> I had occasion to deal with an individual who insisted on this approach.
> It stems from a desire to 'lock down' production servers to prevent any
> changes. In practice, no software is perfect and there are times when a
> simple one-line change will immediately fix the problem. When you need
> to do this, you don't want to be making a one-line change in a staging
> environment and then re-deploying a 50Mb war file. Also you can't be
> totally certain that no other changes have been made in the staging
> environment. I would argue from a management perspective that deploying
> an expanded servlet is less risky and allows more responsive support. If
> the individual insists on the .war file approach, one possible approach
> is to run a staging servlet (expanded) in parallel with the production
> servlet (war file) - this has the advantage of the identical
> environment, available to test under production conditions & available
> as a backup in an emergency.
> On the technical level, there are issues with anything that needs to be
> written to, such as HSQLDB.
>     See
> Doesn't this belong in

View raw message