Re: DispatchAction

[Michael McGrady]

I probably should have noted that SimpleDispatchAction is a complete 
substitute for and works in all cases for whatever we do with 
DispatchAction, LookupDispatchAction, and MappingDispatchAction.  That 
might be another reason for making it the superclass, if you really want 
to connect them.

Maybe it should be in another lineage entirely?
I probably should not have named it "SimpleDispatchAction".  Again, the 
only logic in common is the reflection that calls the methods, which, of 
course, is not really "logic" at all. 

The real "meat" of DispatchAction is that it allows you to get "update" 
from value of the request parameter (requestParam = update) via the 
ActionMapping parameter.  This is not, in my view, a "feature" but a 
problem.  The real "meat" of SimpleDispatchAction is that it gets the 
name of the request parameter (update.x=) and leaves the value of the 
request parameter and the parameter property of the ActionMapping free 
for other service entirely.

Michael McGrady


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]