OK.  Thank you for the reference to the docs.  I have read the section.
This brings up two new questions.

I am redeploying my application for testing by removing the old instance and
then deploying again via Tomcat 4.1.29 manager webapp.  On Windows, Tomcat
apparently leaves the struts.jar file open, blocking deletion of the
WEB-INF/lib directory and subsequent automatic deployment of my changed war
file.  Is there a workaround for this?  Is there a better way of redeploying
in the NT environment?  Tomcat is running on a separate machine from my
development environment.

While I do not care about the disk space used for the storage of war files,
I am concerned about the RAM consumed if each webapp on the server brings
multiple copies of the same libraries into memory.  If I do not share the
jar files among the webapps, isn't this what will happen?

Thank you,
Ed
----- Original Message ----- 
From: "Wendy Smoak" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, December 15, 2003 10:58 AM
Subject: RE: Sharing struts taglibs in Tomcat


> From: Ed Dowgiallo [mailto:[EMAIL PROTECTED]
> I am doing a lot of struts development and would like to
> place the struts jar files in the $TOMCAT_HOME/shared/lib
> directory instead of WEB-INF/lib for each individual war file.

Don't do that.  Really... Disk space is cheap, and deployment is SO much
easier when each webapp is a self-contained entity.

Besides, it's not supported.  Scroll down to section 5.5 on this page:
http://jakarta.apache.org/struts/userGuide/configuration.html
And read the stuff in the bright blue box.

-- 
Wendy Smoak
Application Systems Analyst, Sr.
ASU IA Information Resources Management


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to