On 7/25/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
How would you differentiate actions that process one "flavor" of request (regular action) and actions that process several events (dispatch actions)? What about something like "coarse-grained handlers" and "fine-grained handles"? And which one is which?
Fine and coarse grain doesn't seem like the right shade of meaning. The individual methods remain the same grain, and only one of the methods is invoked at a time.. It's just that multiple methods are glommed onto the same handler. Generically, I might go with "container action". From an API perspective, we can call the same action with different sub-commands, like the way we can call "$ svn copy" or "$ svn delete". That the sub-commands are represented by methods on the handler is an implementation detail. The big picture is that one action mapping contains multiple commands. In s2, we refer to the alternate methods as "aliases". There is a method property on the Action so that we can map an action element directly to a method on a given class. <action name="delete" class="example.CrudAction" method="delete"> In ww2, there is support for a "action!alias" syntax that allowed any no-argument method to be used as an "execute" method, but it's being deprecrated in s2 in favor of declarative configuration/annotation or wildcards. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
