Craig, I am also curious for the reasons for a frozen configuration. I skimmed the ModuleConfig impl and see how every component seems to have a 'freeze'able state. But, sadly, I didn't see an 'unfreeze.' I'm guessing components are passed around via the RequestProcessor and this ensure nothing 'hokey' happens. Since we're on the topic of 'freezing', do you know if Struts-Chains can be modified at run-time to add/remove components or add chains for new action paths?
Regards, David the EVER CURIOUS! :) -----Original Message----- From: Chaikin, Yaakov Y. [mailto:[EMAIL PROTECTED] Sent: Thursday, December 16, 2004 11:21 AM To: 'Struts Users Mailing List' Subject: RE: Dynamically adding an ActionMapping Craig, What is the reason the configuration gets "frozen"? I don't mean to ask about the mechanics of how it's frozen. I am just curious as to why freeze it and not let it be dynamically updated during application lifetime? Thanks, Yaakov. -----Original Message----- From: Craig McClanahan [mailto:[EMAIL PROTECTED] Sent: Thursday, November 25, 2004 1:18 PM To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: Re: Dynamically adding an ActionMapping You will not be able to do this in a ServletContextListener, because that gets executed before the Struts servlet has initialized the data structures representing the configuration information. However, if you write to the Struts PlugIn API, the init() method of this class is called after the configuration file has been loaded, but before the configuration is frozen -- so you can add your own configuration objects at that time. Craig On Thu, 25 Nov 2004 00:04:00 -0800, Tony Li <[EMAIL PROTECTED]> wrote: > Hi all - > > I haven't been able to locate much information about dynamically adding an > ActionMapping. I would like to do this at application startup through my > StartupListener (courtesy of Matt Raible's AppFuse). I'm really only > interested in adding a few simple ForwardActions. > > Any ideas? > > Thanks, > > Tony > > --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]