I have already read the Turbine docs and do understand the details of the system flow. My question was more on the design approach. Anyway, what I do conclude now is that let Action classes come into play only when there has been a form submit. and screen class handle the view code. (The only reason I was thinking of building the view in an action method was due to the fact that I saw some code in Jetspeed action classes that had some view methods like buildNormalContext())
Regards
Akshay
At 11:24 AM 1/10/2003 +1100, you wrote:
On Fri, 10 Jan 2003 11:05, you wrote: > On Fri, 10 Jan 2003 10:09, you wrote: > > It took me a while and the help from Quinton McCombs, Rodney > > Schneider and Scott Eade to come to appreciate what Turbine is > > doing, though my understanding is still not complete yet. > > > > According to my understanding, Turbine follows a structured > > sequence in displaying a page. It always look for a java class file > > to execute prior to the display/action, if it fails that, it will > > execute the Default.class file as pre-defined in the TR.props file. > > The best way to understand Turbine's execution path is to read this > document, especially the "System Flow" section: > http://jakarta.apache.org/turbine/turbine-22/fsd.htmlAlso, I recommend stepping through the Turbine code in a debugger... this will aid your understanding of the Turbine internals immensely. -- Rodney -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
