On Thu, 11 Jul 2002, Brian Kirsch wrote:
> Date: Thu, 11 Jul 2002 13:59:06 -0700
> From: Brian Kirsch <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: Struts Users Mailing List <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED]
> Subject: RE: Altering Configuration from command line
>
> Thanks for the responses,
> I did see the reload feature of the ActionServlet.
>
And it's not going to work in 1.1 anyway.
> However, we are looking to avoid going through an http interface to do the reload.
> For security reasons we want the reload functionality to only be run
> from the local system console.
>
That's pretty easy to deal with, using security constraints or adding a
request filter that only accepts HTTP requests to the manager webapp from
127.0.0.1. See the section on "Request Filters":
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/context.html
> We also want a way if possible to add new classes (Action, FormBean,
> Business Logic) with out rebooting the server and have the ActionServlet
> recognized them as well.
>
This is why it became pointless for Struts to attempt to act like a
container -- there's nothing you can do to force the recognition of new
classes in any portable way. It's much better to let the container do
this, because it already knows how to load and unload webapps dynamically.
> The goal is to be able to alter / upgrade our struts web application features
> with out requiring downtime.
>
Not a problem (depending, of course, on your app server's capabilities).
>
> Any suggestions?
>
If you're using Tomcat, my suggestion stands. If you're using some other
server, check out it's capabilities for dynamic webapp reloading
(including appropriate security precautions).
> Thanks,
> Brian Kirsch
>
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
