Ah -
In my enviroment, its more the case of one
developer working on lots of apps at the same time;
and in my case neither memory or servers are cheap!
(unfortunately) and acquiring either requires more
beauracracy than you want to hear about.
So.. back to the first question - how to easily add in
a new "component" (terminology?) such as the new
Hibernate/Spring petstore without "messing" the
existing environment?
Derek
>>> [EMAIL PROTECTED] 2004/06/25 02:51:14 PM >>>
Il giorno 25/giu/04, alle 14:31, Derek Hohls ha scritto:
> to it... do you not end up with lots and lots of
> different "Cocoon projects", and lots of Cocoon
> instances on the server, in the way you do it?
I usually strive for self-contained projects. Ideally, if a new
developer joins our team, all he should have to do is:
[snip]
And yes, this means having lots of different "Cocoon projects", but
each developer is (hopefully) working on one at a time and besides,
they all use the same infrastructure. In development, each developer
has his own Jetty instance that is included in the CVS module and hosts
only a single, default webapp.
In production, if we host many webapps in the same container, we make a
different context for each one, and each one has its own copy of
Cocoon's JARs. This guarantees isolation, no conflicts due to different
releases of Cocoon used, the possibility of
adding/removing/stopping/restarting each application without impacting
the others. This also probably means more memory is needed, but so
what? Memory is cheap and we can always add one more server to scale
horizontally.
Ugo
--
Ugo Cei - http://beblogging.com/
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
