Thanks for your replies, Wendy and Bill.

Yes I could reload the webapp but, and this is a big but, the start-up of my
server takes a good while longer than reloading the struts config. There are
things going on that are not contained within my struts config (Such as web
services instantiation, XSL transformation of data to html etc etc).

No worries if it can't be done anymore, I have accepted it for months... it
was just a question thrown innocently to see if anyone knew of the way that
had been replaced. My question has actually been answered:

"My understanding is that the reload action was dropped because it sometimes
left things in an unpredictable state."

That's fine, although I wonder if it could have been looked at and worked on
instead of just dropped.

I am not a contributor but I think it's high time I did some 'give back' as
my old Big Blue would have said. If anyone has some detail on where to start
with looking at this code and the problems that left it in an unstable state
I would be interested to see them. On the other hand if this action was not
useful to anyone except me I will keep quiet ;)

-----Original Message-----
From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Sent: 03 March 2005 22:52
To: Struts Users Mailing List
Subject: Re: Reloading Configuration File

From: "Mark Benussi" <[EMAIL PROTECTED]>

> This action "went" in Struts 1.2 and I never found a replacement.
> Any ideas anyone?

I'm not entirely sure what you're asking.  The discussion you quoted seems
to start from a false premise:  that you have to stop and start Tomcat to
get config changes to take effect.

All you have to do is reload the individual webapp that had changes.  I do
it with 'ant reload'.  (Tomcat ships with Ant tasks that interact with its
manager app.)  You can also use the HTML version of the manager app-- click
reload, and you're done.

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

Reply via email to