commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33006] - [chain] Proposal: DispatchChain
Date Sat, 08 Jan 2005 05:13:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33006>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33006





------- Additional Comments From slough@gmail.com  2005-01-08 06:13 -------
As a new user the whole concept of DispatchAction seems odd to me for use in
Chain.  I understand the appeal of clustering common operations and decreasing
the number of classes, but it seems like allowing arbitrary method calls from
within external commands will muddy the distinction between a group of commands
(a chain) and the more fundamental command.  (Moreover, should users be viewing
hard-coded commands as fundamental units of work, or is my view a bit off?)

For example, if we have CommandOne that uses the method work() that CommandTwo
wants to access, why not break work() into its own command and make CommandOne
and CommandTwo chains?

Or alternatively, why couldn’t one just extend an "AbstractCommand" containing
common methods, such as work()?

Concerning the clustering of common operations, might there be a way to use
inner classes for some commands instead trying to implement method sharing? 
This would preserve the single execute method philosophy of one class per
command, while grouping similar commands into a common hierarchy.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message