Re: "Configuration is frozen" exception thrown for actionMapping.setScope

2005-11-07 Thread Hubert Rabago
On 11/7/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi Hubert, > > Thanks for the suggestion. I tried the second option > > 2) Override the default ActionMapping class and set its default "scope" > value to request. > > Extended the ActionMapping class and in the CustomActionMapping > cons

RE: "Configuration is frozen" exception thrown for actionMapping.setScope

2005-11-07 Thread khan.sajid
however is there any known issues in using this method OR Anything else also needs to done Thanks Sajid -Original Message- From: Hubert Rabago [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 02, 2005 8:31 PM To: Struts Users Mailing List Subject: Re: "Configuration is fro

Re: "Configuration is frozen" exception thrown for actionMapping.setScope

2005-11-02 Thread Hubert Rabago
On 11/2/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi All, > > In our application, we have decided to force all the actions to use the > request scope. So instead of adding scope ="request" in the > element in struts-config.xml for each action, we extended the > RequestProcessor class as

Re: "Configuration is frozen" exception thrown for actionMapping.setScope

2005-11-02 Thread Frank W. Zammetti
Hi Sajid, One way to get around this would be to modify the ActionConfig class's freeze() method... just remove configured=true; and you should be all set (I'm going from memory here, but I think I'm remembering right). But, the configs are frozen for a reason, so you may not want to do that. An

"Configuration is frozen" exception thrown for actionMapping.setScope

2005-11-02 Thread khan.sajid
Hi All, In our application, we have decided to force all the actions to use the request scope. So instead of adding scope ="request" in the element in struts-config.xml for each action, we extended the RequestProcessor class as below 1.Extend the RequestProcessor class and add the config entry