On Thu, Apr 11, 2002 at 10:07:40PM -0400, Bill Burton wrote: > I'm working on a project now interfacing WW with a third party > application. However, it takes a long time for the web app to restart > after making changes to Actions or Beans. So it would be nice if it were > possible if Actions and Beans were reloadable.
Yes, this would be really nice. But isn't this a container issue? I think Jetty or Resin support class reloading and webwork IMHO uses the containers classloader. Rickard could you please enlighten us? > Another, similar enhancement would be to support reloading the action and > view mappings without a restart. I proposed this some days ago. But IIRC one must write a custom Configuration implementation and call Configuration.setImpl(customConfig). A starting point is to subclass DefaultConfiguration to reload the configuration files on every request. -billy. -- Meisterbohne Söflinger Straße 100 Tel: +49-731-399 499-0 eLösungen 89077 Ulm Fax: +49-731-399 499-0 _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
