on 6/6/01 2:22 PM, "Peter Lynch" <[EMAIL PROTECTED]> wrote:
> 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.
How do you handle this case:
<form action="Foo">
<input type="submit" name="eventSubmit_doFoo">
<input type="submit" name="eventSubmit_doFooBar">
</form>
> 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 :-) ).
You should never need to modify the Turbine.java
The class you want is ActionEvent.java. You don't need to modify it though.
All you need to do is create your own version of it and then make your own
actions extend it.
-jon
--
"Open source is not available to commercial companies."
-Steve Balmer, CEO Microsoft
<http://www.suntimes.com/output/tech/cst-fin-micro01.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
