RE: Re[2]: xerces and xalan in WEB-INF/lib is not good and needs to be changed....

Hi Jake,

> I still don't think that the Barracuda webapp should exist in
> an auto-deploy directory specified by Tomcat.  It should exist
> elsewhere

I agree with this...

> and the build should install/reload/start/stop/remove/deploy/
> undeploy itself from wherever it exists.  Driving all this using
> the build's own Ant manager tasks provides finer grained control
> over the server and you never have to shut down the server itself.

...and I would like to get to this, too (using the ccf.xml file, right?)

But I'd like to wait for Shawn to get back before we actually do something,
since he knows the server setup better than I do. He'll be back on Tuesday.
So I'm not sure if we want to dive into it now, or wait until then and let
him play catch-up...

So in the meantime, do you have any resources (links) I could look at to
come up to speed on how the ccf.xml stuff works? Or would it be easier just
to look at your examples?

Christian
----------------------------------------------
Christian Cryder [[email protected]]
Internet Architect, ATMReports.com
Barracuda - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Jacob Kjome
> Sent: Friday, January 17, 2003 10:54 AM
> To: Christian Cryder
> Subject: Re[2]: [Barracuda] xerces and xalan in WEB-INF/lib is not good
> and needs to be changed....
>
>
> Hello Christian,
>
> Friday, January 17, 2003, 10:32:41 AM, you wrote:
>
> CC> Ok, so I've updated the build.xml to NOT put xerces and xalan
> jars in the
> CC> WEB-INF/lib dir when the 'install' target is run.
>
> nice :-)
>
> CC> Per your comments on cleaning up the jars in /lib, I've added
> that to the
> CC> clean target. Note however that if Tomcat is running Ant may
> not be able to
> CC> delete these jars because Tomcat locks jars in the /lib dir...
>
> This shouldn't be much of an issue.  That is always true in any
> build where you do a clean.  I still don't think that the
> Barracuda webapp should exist in
> an auto-deploy directory specified by Tomcat.  It should exist
> elsewhere and the build should
> install/reload/start/stop/remove/deploy/undeploy itself from wherever it
> exists.  Driving all this using the build's own Ant manager tasks
> provides finer grained control over the server and you never have
> to shut down
> the server itself.
>
> Instead of bouncing Tomcat for every modification, we should just be
> running the builds catalina targets appropriately.  Tomcat itself
> can be up
> 100% of the time.  Only if you want to modify libs in Tomcat's library
> folders or other Tomcat internals should there be a need to shutdown
> Tomcat itself.  This avoids interruption of other apps on the server.
>
> What do you think?
>
> Jake
>
> _______________________________________________
> Barracuda mailing list
> [email protected]
> http://barracudamvc.org/lists/listinfo/barracuda