So, I re-read the original post and follow-ups, and it doesn't seem like this is what was being asked for at all. Maybe it's me, but it sounded like there was just some confusion about how to do *development*, not how to dynamically add actions at runtime. If that's the case, Li Xin should check out Tomcat's "Application Developer's Guide":
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/appdev/index.html Specifically, it details the use of the install, reload, and remove ant tasks that make modifying and reloading an app fairly painless without having to restart the container. As for the changes outlined in Manfred's document, I'd recommend a search of a struts-user archive (particularly for messages from Craig) as to why ReloadAction was removed from 1.1 and why config freezing is important. Quoting Manfred Wolff <[EMAIL PROTECTED]>: > Hi. > > After the discussion today I have made a litte paper how to add actions > dynamically. Enjoy. There is a step by step tutorial, what to do. At > runtime I change in this little description my actionpath from demo.jsp > to demo2.jsp. There are a few modification necessary. After that you can > configure and modify any term, that is described in the struts-config. > There are a few application that need this, but there are. > > Manfred > > http://www.manfred-wolff.de/Configuration.pdf -- Kris Schneider <mailto:[EMAIL PROTECTED]> D.O.Tech <http://www.dotech.com/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
