RE: a re-deploy does not refresh ApplicationResources in Apache

2004-09-21 Thread Hollaway, Shedrick CIV (TRFKB C600)
Thomas, 

You will need to make the Tomcat context reloadable. Open the project
properties and select Tomcat (if not present install Sysdeo Eclipse Tomcat
Launcher plugin). In the 'General' tab, check the both 'Can update
server.xml file' and 'Mark this context as reloadable (reloadable=true).'

Shed.

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 20, 2004 6:11 PM
> To: [EMAIL PROTECTED]
> Subject: a re-deploy does not refresh ApplicationResources in Apache
> 
> 
> 
> 
> 
> 
> 
> I'm running eclipse 3.0, myeclipse 30b2, apache 5.0.27 and struts 1.1
> 
> if I change the ApplicationResources.properties file then 
> redeploy it to
> tomcat, my struts web app does not see
> the change.  I need to stop/start tomcat to see a change in 
> the properties
> file.
> 
> My question, is there a struts or tomcat configuration value 
> that will make
> the properties file active without
> recycling tomcat?
> 
> Thanks for your help
> 
> Tom Perry
> 
> 
> 
>  
> This message is intended for the recipient only and is not 
> meant to be forwarded or distributed in any other format. 
> This communication is for informational purposes only.  It is 
> not intended as an offer or solicitation for the purchase or 
> sale of any financial instrument, or security, or as an 
> official confirmation of any transaction.  Putnam does not 
> accept purchase or redemptions of securities, instructions, 
> or authorizations that are sent via e-mail.   All market 
> prices, data and other information are not warranted as to 
> completeness or accuracy and are subject to change without 
> notice.  Any comments or statements made herein do not 
> necessarily reflect those of Putnam, LLC (DBA Putnam 
> Investments) and its subsidiaries and affiliates.  If you are 
> not the intended recipient of this e-mail, please delete the e-mail.
> 
> -
> 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]



RE: a re-deploy does not refresh ApplicationResources in Apache (resend - mailer returned it to me)

2004-09-20 Thread David G. Friedman
Tom,

I agree with Wendy.  I play around on Tomcat 5.0.28, Struts (1.1 and 1.2.4),
Eclipse v3.0 (now 3.0.1 as of last night).  I use the Sysdeo tomcat plug-In
and have to make the application reload (a simple menu option) to see any
resource changes like the properties file.  I could make it restart all of
Tomcat but there is no need.  I'm sure your Eclipse plug-in has something
similar for per-application restarting versus full-tomcat restarting.

Fyi... For my plug-In in Eclipse, in the Java perspective, I right click on
my project, go to "Tomcat project" and choose the menu option "reload this
context" to force Tomcat to reload ONLY my webapp.  Using the buttons the
Sysdeo plug-In puts on the menu bar, that would restart the whole Tomcat
server, which I don't want to do.  The sysdeo plugIn is available at:
http://www.sysdeo.com/eclipse/tomcatPlugin.html

Regards,
David

-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Monday, September 20, 2004 7:19 PM
To: Struts Users Mailing List
Subject: Re: a re-deploy does not refresh ApplicationResources in Apache


From: <[EMAIL PROTECTED]>
> if I change the ApplicationResources.properties file then redeploy it to
> tomcat, my struts web app does not see
> the change.  I need to stop/start tomcat to see a change in the properties
> file.
> My question, is there a struts or tomcat configuration value that will
make
> the properties file active without recycling tomcat?

(Apache 5.0.27?  I assume you mean Tomcat, which is an Apache project by way
of Jakarta.)

I hesitate to say for sure because I'm not on Tomcat 5 or Eclipse.  But...
you shouldn't have to restart Tomcat entirely, just the individual webapp.
I do it with Ant targets, first 'install' then 'reload'.

If that's one of the files that gets read once when the webapp starts up,
the only way to get it to be read again is to reload (or stop and start) the
webapp (context).

--
Wendy Smoak


-
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]



Re: a re-deploy does not refresh ApplicationResources in Apache

2004-09-20 Thread Wendy Smoak
From: <[EMAIL PROTECTED]>
> if I change the ApplicationResources.properties file then redeploy it to
> tomcat, my struts web app does not see
> the change.  I need to stop/start tomcat to see a change in the properties
> file.
> My question, is there a struts or tomcat configuration value that will
make
> the properties file active without recycling tomcat?

(Apache 5.0.27?  I assume you mean Tomcat, which is an Apache project by way
of Jakarta.)

I hesitate to say for sure because I'm not on Tomcat 5 or Eclipse.  But...
you shouldn't have to restart Tomcat entirely, just the individual webapp.
I do it with Ant targets, first 'install' then 'reload'.

If that's one of the files that gets read once when the webapp starts up,
the only way to get it to be read again is to reload (or stop and start) the
webapp (context).

-- 
Wendy Smoak


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



a re-deploy does not refresh ApplicationResources in Apache

2004-09-20 Thread Thomas_Perry





I'm running eclipse 3.0, myeclipse 30b2, apache 5.0.27 and struts 1.1

if I change the ApplicationResources.properties file then redeploy it to
tomcat, my struts web app does not see
the change.  I need to stop/start tomcat to see a change in the properties
file.

My question, is there a struts or tomcat configuration value that will make
the properties file active without
recycling tomcat?

Thanks for your help

Tom Perry



 
This message is intended for the recipient only and is not meant to be forwarded or 
distributed in any other format. This communication is for informational purposes 
only.  It is not intended as an offer or solicitation for the purchase or sale of any 
financial instrument, or security, or as an official confirmation of any transaction.  
Putnam does not accept purchase or redemptions of securities, instructions, or 
authorizations that are sent via e-mail.   All market prices, data and other 
information are not warranted as to completeness or accuracy and are subject to change 
without notice.  Any comments or statements made herein do not necessarily reflect 
those of Putnam, LLC (DBA Putnam Investments) and its subsidiaries and affiliates.  If 
you are not the intended recipient of this e-mail, please delete the e-mail.

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