Use the source, Luke, use the source. ;-)
Just as an aside -- Struts "digests "the Struts config file when it
loads, using it as a "script" to create the mappings. At runtime, Struts
refers to the mappings (loaded in memory) -- not to the actual
configuration file stored on disk. (Hence, the need for the reload
administrative action.)
These actions do the same thing -- they affect the mappings stored as a
protected property of the ActionServlet.
These
"Maring, Steve" wrote:
>
> I understand what the end result of these do, but how do they do them, and
> how are they used?
> Do they modify the struts-conf.xml or just the ActionMapper?
>
> <!-- The standard administrative actions available with Struts -->
> <!-- These would be either omitted or protected by security -->
> <!-- in a real application deployment -->
> <action path="/admin/addFormBean"
> type="org.apache.struts.actions.AddFormBeanAction"/>
> <action path="/admin/addForward"
> type="org.apache.struts.actions.AddForwardAction"/>
> <action path="/admin/addMapping"
> type="org.apache.struts.actions.AddMappingAction"/>
> <action path="/admin/reload"
> type="org.apache.struts.actions.ReloadAction"/>
> <action path="/admin/removeFormBean"
> type="org.apache.struts.actions.RemoveFormBeanAction"/>
> <action path="/admin/removeForward"
> type="org.apache.struts.actions.RemoveForwardAction"/>
> <action path="/admin/removeMapping"
> type="org.apache.struts.actions.RemoveMappingAction"/>
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 737-3463.
-- http://www.husted.com/about/struts/
