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 32940] - [chain] Provide a "dispatch" command
Date Wed, 05 Jan 2005 22:39:55 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=32940>.
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=32940





------- Additional Comments From Joe@Germuska.com  2005-01-05 23:39 -------
Because the digester rules for <command> include "SetProperties", any XML
attribute in the <command> element whose name is a bean-property-name of the
instantiated command will be used to set that property value with the
attribute's value.  So:

<command name="foo" className="MyDispatchSubclass" method="doFoo" />
would execute MyDispatchSubclass.doFoo(...)


I don't feel strongly about the naming of the properties.

I included the methodKey version mostly to keep consistency with other patterns
I've seen in early Chain development.  It seems similar to the Struts
DispatchAction which allows a request parameter value to be used as the
specification for dispatch.  I don't use that myself, but it seemed like some
folks might want such.  It would be possible to achieve the same but more
verbosely with a number of explicitly configured commands and a CopyCommand, so
I wouldn't argue too much over it.

-- 
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