struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21769] - Multiple actions for a request
Date Tue, 22 Jul 2003 18:29:31 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21769>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21769

Multiple actions for a request

martinc@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From martinc@apache.org  2003-07-22 18:29 -------
As Craig says, chaining Action classes per se is a bad idea, and causes 
numerous problems. Trust me, I've been there, and it's no fun at all. I used to 
think chaining actions was handy, but now I'm a staunch opponent.

However, it is straightforward to create *an* Action class which can, as Craig 
puts it, "compose the execution of multiple business functions". Or you could 
create *an* Action which calls into a configurable request handler and display 
preparation handler, as I have done.

The point is that the underlying functionality - breaking up the processing of 
a single request into multiple steps - is absolutely useful, no question, but 
that chaining Action classes to achieve that is the wrong way to go about it.

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Mime
View raw message