Hi, Generally, I think the flow of execution is as follows (I'm sure it's documented somewhere but I don't have the link), and please correct if this is wrong.
Here goes: Given a URL, Turbine parses it to determine: 1. action (with event) 2. screen 3. name/value pairs as request parameters If there is an action, then it its code gets executed either via a default doPerform(..) or doYourMethod(..). Next comes the "renderable screen", which Turbine/Velocity would locate template .vm files (if applicable) for and merges them into the various page components (Page, Layout, Screen, Navigation, etc.), including the code from your corresponding screen class. Regards, Daniel On Thu, 8 Jul 2004, Jeffery Painter wrote: > > sounds correct to me... > > On Thu, 8 Jul 2004, Ryan Gantt wrote: > > > So the execution DOES go straight to the action class, and you have to > > manually provide the calls to the Intake service, etc? > > > > If I'm reading this correctly, there is *no* middle man class between > > the form submission and the call to the action class. Is that correct? > > > -- > Jeffery Painter > President > Kiasoft, Inc. (910) 352-3699 > 3205 Randall Parkway, Suite 119 > Wilmington, NC 28403 > > - -- > [EMAIL PROTECTED] http://kiasoft.com > PGP FP: 9CE8 83A2 33FA 32B1 0AB1 4E62 E4CB E4DA 5913 EFBC > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > > iD8DBQE/qEQE5Mvk2lkT77wRAnMJAJ9vJ6qOkg/mvqqIpz7troCEQJ8bFACglu/U > YNXabx7DZOV2Hd9LwSTmGpY= > =dWiu > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
