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 38343] - [extras] ParameterListActionDispatcher
Date Tue, 28 Feb 2006 20:10:50 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=38343>.
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=38343


paul4christ79@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|Unknown                     |1.3.0




------- Additional Comments From paul4christ79@yahoo.com  2006-02-28 21:10 -------
I have included two proposals: ParameterMappingDispatchAction (older) and
ParameterListActionDispatcher (newer). The second one I strongly prefer and use
myself, but I understand there that there are some differences in design
philosophy among the Struts developers. 

It is my opinion that having multiple action implementations *just* for
controlling dispatching is inelegant. When it comes to team development in which
there may be a shared base class, but different types of dispatching is wanted
per use case, the two requirements conflict and cannot be reconciled easily.
Hence, I think the ActionDispatcher class in Struts 1.2.7 solves this problem by
separating the Action from its dispatch methodology. This cleanly allows
everyone to subclass from one Action and choose the type of dispatching as needed. 

I recommend this is "the way to go" (as it is the correct design pattern) and,
furthermore, no more XXXXDispatchAction classes should be considered. Having
XXXXDispatchAction classes are convienent -- no doubt -- but I really believe
these two philosophies are at right edges.

You could create subclasses for every new ActionDispatcher that comes along, but
that should be, imo, a private developer decision and not supported with custom
classes in Struts.

-- 
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: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message