Hey there,
I'm curious. Why were actions and action events were
decided to be two different parameters? It seems a
simpler approach would have been to have one parameter
named "action" with a possible value of
<action classpath>/<action classname>.<action method
name>
This seems simpler. Also the current convention may
force you to name your action class methods like
doLongmethodname as opposed to
doLongMethodName
The second being more of a standard method naming
scheme.
If I wanted to change this behaviour/add this
functionality it looks like I would affect the Turbine
servlet itself and the class that parses the action
events (whereever that is :-) ).
Is this true?
Peter
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
