My only opinion on this matter is that we should do whatever 1.3 does -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francisco Hernandez Sent: Wednesday, November 12, 2003 1:43 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] [WW2] ActionContext.getContext().getParameters().put() fails under Tomcat
I thought it was decided to put ActionMessages into ActionSupport, I could have even sworn there was an open issue for this.. this is something I think alot of people implement and makes sense to included, should be exactly like ActionErrors Jason Carreira wrote: > I'm open to this... There was some feeling before that this should be > implemented by people's own base action classes... > > >>-----Original Message----- >>From: Olaf Bergner [mailto:[EMAIL PROTECTED] >>Sent: Wednesday, November 12, 2003 4:20 PM >>To: [EMAIL PROTECTED] >>Subject: RE: [OS-webwork] [WW2] >>ActionContext.getContext().getParameters().put() fails under Tomcat >> >> >>I was trying to pass some properties down a chain of actions >>as indicated in my other post. Right now I am trying to get >>rid of my workaround by using the ChainingInterceptor as you >>suggested. Sorry, must have missed this one in the docs. >>Thanks for the hint. >> >>One more question, though: Presumably I am not the only one >>who from time to time finds it useful to tell his users about >>what's going on. Something along the lines of "Congrats, you >>successfully issued rm -rf / on this venerable unix box! Help >>yourself to a nice cup of tea." that is not necessarily an >>error. Since the actionErrors property in ActionSupport does >>such a good job, why not add another actionMessages property >>as I did in my derived class? Should be a matter of five >>minutes and might be useful for some. Just my 2 ct. >> >> >>>-----Original Message----- >>>From: [EMAIL PROTECTED] >>>[mailto:[EMAIL PROTECTED] >> >>Behalf Of >> >>>Jason Carreira >>>Sent: Wednesday, November 12, 2003 9:16 PM >>>To: [EMAIL PROTECTED] >>>Subject: RE: [OS-webwork] [WW2] >>>ActionContext.getContext().getParameters().put() fails under Tomcat >>> >>> >>>It looks like at least in Tomcat it is... I forget if this >> >>is part of >> >>>the standard... >>> >>>What are you trying to do? Maybe there's another way to do it... >> >> >> >>------------------------------------------------------- >>This SF.Net email sponsored by: ApacheCon 2003, >>16-19 November in Las Vegas. Learn firsthand the latest >>developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, >>and more! http://www.apachecon.com/ >>_______________________________________________ >>Opensymphony-webwork mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork >> > > > > ------------------------------------------------------- > This SF.Net email sponsored by: ApacheCon 2003, > 16-19 November in Las Vegas. Learn firsthand the latest > developments in Apache, PHP, Perl, XML, Java, MySQL, > WebDAV, and more! http://www.apachecon.com/ > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
