I know you can use pull model to stuff data into context and let template decide which one to pick. But it doesn't cure all. The problem is what and when do you stuff data into context? In some cases the data is only associated with that screen. The most logical place to populate the data is in the associated class. Anywhere else (actions etc) will result in code duplication.
> > This posed a big problem because major content > > rendering logic could be and > > should be implemented in B.java. > > Check out the pull model. In this approach you pull > all the data into each template therefore eliminating > the need to put any content rendering logic in a > screen. my turbine app uses the pul model and the > only code in any screens is for security purposes. > > Push vs. Pull: > http://jakarta.apache.org/turbine/turbine-2.2.1/pullmodel.html > > Pull HowTo: > http://jakarta.apache.org/turbine/turbine-2.2.1/howto/pullmodel-howto.html > > -Lou > > __________________________________ > Do you Yahoo!? > SBC Yahoo! DSL - Now only $29.95 per month! > http://sbc.yahoo.com > > --------------------------------------------------------------------- > 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]
