Ryan Gantt <[EMAIL PROTECTED]> writes:
>Hello,
>I've been wading through pages and pages of the scattered documentation
>for Turbine (with Velocity), and while there are some things that make
>so much sense, there are still aspects of the application that baffle
>me.
>My biggest question at this point is: What is actual flow of execution
>for Turbine once a user submits a form? I'm running the intake service
>on the forms, so I don't know if it hits Intake first or goes directly
>to my action class.
It goes directly to your action class. If you need input validation, you
must perform this in your action class.
There is not hardwired flow like e.g. struts has (at least not for 2.3).
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honorable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
