> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 27, 2003 8:31 AM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] proposed small change to ww 1.3 > > > hi dick, > like someone noticed on the list, if you have a method > ActionContext.setRequest(), then i think it should set the > request object for the entire request scope. like when you > set the request in a Filter, og in the RequestDispatcher. > > if you do not think its a good idea to allow this, then i > propose to remove the method from the ActionContext so as not > to cause confusion. > > as for my own little problem it wouldn't help to make a new > include tag since the values never reaches the jsp page where > the tag would be. > > i guess i could reaarange my architecture around it, but my > point is more that it is an inconsistency to have a method > that has no effect :-) > > sincerely > morten wilken
I does have an effect, just not what you're looking for. What it's there for is to set the request into the ActionContext by the dispatcher. It has to do with the fact that ActionContext is really just a map put into a threadlocal. I would suggest instead making setRequest() throw an IllegalStateException if you try to set it and a request has already been set. Jason ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
