--- [EMAIL PROTECTED] wrote: > 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. >
the whole point of the pull model is that you're NOT stuffing data anywhere. You write the function getStuff() once, in your pull tool, and then anytime your front-end designer needs to get that Stuff in his template, he makes a call to the function. If you only need the data once, the function only gets called once. There is no code duplication. Plus, if you later find the need to use the same data elsewhere, you don't need to rewrite any java code. -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]
