The bigger question is why you would want to do this. In Struts 1, it was one of the few ways to pass configuration information to an Action. In Struts 2, you can pass values directly to an action via setters, which is a better solution imo.
Don On 8/9/07, Ian Roughley <[EMAIL PROTECTED]> wrote: > Have you tried overriding the struts.configuration property with a new > Confguration class that builds and returns your new ActionConfig? > > > Vinod Singh wrote: > > Any clues?? > > > > Thanks, > > > > Vinod > > -------- Original Message -------- > > Subject: Extending ActionConfig in Struts2 > > From: Vinod Singh <[EMAIL PROTECTED]> > > To: user@struts.apache.org <user@struts.apache.org> > > Date: Tuesday, August 07, 2007 3:05:36 PM > >> Hi All, > >> > >> The Struts 1.x provides a facility to extend the ActionMapping by > >> defining it in web.xml in following manner- > >> > >> <init-param> > >> <param-name>mapping</param-name> > >> <param-value>CustomActionMapping</param-value> > >> </init-param> > >> > >> In Struts 2.x I don't see anyway to extend ActionConfig. > >> > >> The ActionConfig class is hard coded in addAction(...) method of > >> com.opensymphony.xwork2.config.providers.XmlConfigurationProvider. > >> > >> Can anyone guide me in extending ActionConfig, if I am missing > >> something? > >> > >> Thanks, > >> > >> Vinod > >> > >> > >> > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
