Re: passing parameters or object from one action to other

2003-06-06 Thread David Chelimsky
Isn't this just action chaining using HTTP instead of within the jvm? I'm not sure I get the reasons why action chaining is inherently a bad idea, though I do get that there are potential pitfalls if misused, but that's true of many patterns. Can you explain? Or point me to an article that

RE: passing parameters or object from one action to other

2003-06-06 Thread Andrew Hill
If you take a quick look through the archives you will see it has been discussed quite a bit not all that long ago. -Original Message- From: David Chelimsky [mailto:[EMAIL PROTECTED] Sent: Thursday, 5 June 2003 20:59 To: Struts Users Mailing List Subject: Re: passing parameters or object

RE: passing parameters or object from one action to other

2003-06-05 Thread Andrew Hill
You can put them in the request as attributes and use a non-redirecting forward *but* then you are 'action chaining'. (Action chains are bad. n'kay) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, 5 June 2003 19:25 To: [EMAIL PROTECTED] Subject:

RE: passing parameters or object from one action to other

2003-06-05 Thread Andrew Hill
(Oops. Hit send too soon. Try again!) You can put them in the request as attributes and use a non-redirecting forward *but* then you are 'action chaining'. (Action chains are bad. n'kay) The other alternative - suitable for string parameters - is to make them request parameters by appending to