For 1.1, I believe you'd use: <action-mappings type="pkg.SecureActionMapping"> <action .../> ... </action-mappings>
The "mapping" init-parameter is deprecated in 1.1. You could also customize the actions on an individual basis with: <action-mappings> <action className="pkg.SecureActionMapping" .../> ... </action-mappings> Quoting James Childers <[EMAIL PROTECTED]>: > Ladies and gents, > > Having an issue with migrating our application over from 1.0.2 to 1.1. > Specifically, we have a problem in the following line from our > ActionServlet: > > ModuleConfig modCfg = RequestUtils.getModuleConfig(request, > getServletContext()); > SecureActionMapping secAMapping = (SecureActionMapping) > modCfg.findActionConfig(path); > > The second line gives a ClassCastException whenever a request is made. The > hierarchy for SecureActionMapping is: > > ActionConfig > +- ActionMapping > +- SecureActionConfig > +- PackagingActionMapping > +- SecureActionMapping > > Further, the "mapping" init-param in web.xml points to this > SecureActionMapping class. The class type being returned by the > findActionConfig(String) method is ActionConfig, although the servlet appears > to be configuring itself properly during the initModuleConfig(String, String) > method of ActionServlet. > > So my question is this: Is there a different mechanism for specifying the > default ActionMapping class than doing so in web.xml? > > Thanks in advance, > > -= James -- 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]
