Hello, Aapo Laakkonen 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. > > I'm not sure, but this sounds like you have misconfigured > your container or it does not support hot deployment. I'm > not sure if we are talking about the same thing.
It's a web application, not an EJB one so there's nothing to misconfigure. The issue is if any classes in the WEB-INF/classes directory change, the web app needs to be reloaded. The third party application takes some time to restart. In the worst case, I suppose I could write Actions as JSP's which can be dynamically reloaded but I didn't want to implement it that way. > > Another, similar enhancement would be to support > > reloading the action and view mappings without a restart. > > This would be nice and it is very easy to implement. Stuts > uses this kind of approach on reloading actionmappings: > > <action path="/admin/reload" > type="org.apache.struts.actions.ReloadAction"/> > > That is simply an action that re-reads resource bundle > and struts-config.xml file (that includes those mappings). > > So one way to implement this is to provide some default > actions with WebWork... I'm not sure if there is one yet. One feature request was for a management console. That would be the logical place for this kind of thing. -Bill _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
