Bruno Yes, I suggest you read the paper first before we continue the discussion on templates ;-)
In the meantime, perhaps you can expand on why there should not be logic in generators such as XSP and JXT and, if not there, where it should, in fact, be (short of writing custom Java code each time) ? I agree that flow control should not be in XSP; but no data manipulation? Even writing conditional SQL to bring out "part" of the data, based on input parameters, is kind of manipulation, and soon as you do something like add two values from a row result on the basis of the third value, you have added logic. Where does all this go instead?? And why are all the docs then mis-leading us about doing these type of things? Thanks in advance for any advice or "better practice" suggestions... Derek >>> [EMAIL PROTECTED] 2004/05/04 08:53:06 PM >>> On Tue, 2004-05-04 at 10:39, Derek Hohls wrote: > Bruno > > I apologise then, if I misunderstood what you said. > > I still do not think that we should use the term "template > generator" in this context. There are "generators" and there > are "templates" and I don't think their roles should be mixed. > > That's why I was arguing for two different "takes" on the current > situation - the "JXGenerator" which sits in the same place that > other generators do (eg XSP) and allows access to, and manipulation > of, the underlying data; and "JXTemplate" which is only about > the layout and "filling in the data". If you are also saying this > then we are in agreement! yep, we agree on the goal, though I still notice you persist on the fact that generators would do manipulation of the underlying data. I don't think this has ever been the purpose of generators and thus also XSP. Of course, things can always be misused. If I want I can start an HTTP server or send mail in the toString() mehod of an object. But that's hardly the intended use of toString(). Likewise, if someone implements the business logic and flow control of his/her site in XSP, we can't stop them. With JXTemplate the same: it is meant to use the data available from a few supplied contexts: most importantly the viewData from flowscript, and possibly environment data like the request and session objects. If used in that way, is it still different from the 'real templates'? (Just curious, I haven't found time yet to read the paper) -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
