JD This was *exactly* my post to the mailing list a few days back - I have previously used XSP to do all the DB stuff (in my case, it was all there was a while back) - and now that JXT is available, I would like to "refactor" or just move forward with the new (recommended?) approach.
However, it does not appear there are guidelines to do so? Let me ask you - have *you* found a way to do this and maybe we can work up some docs for others in this area? Thanks Derek PS Are you using Woody and Flow for DB-type work as well - I need to get going with this very soon - do you have any "hints and tips" as to a good learning path? >>> [EMAIL PROTECTED] 2004/05/04 01:18:54 PM >>> Nacho Jimenez wrote: > >> Other than the CPA, we would show other options. For example, if a >> newbie >> were reading up on JXTemplates, rather than saying that you can use >> Jexl or >> JXPath, we would choose our CPA (for example, JXPath), but have a >> link to a >> homologous page that explains the same things, but for Jexl. This would >> reduce one more variable, and thus one more possible source of delay or >> confusion to a newbie. So new users will be able to get up and >> running much >> faster, and once they have more experience, will be able to go over the >> alternative approaches. >> >> > This is just an example of what I think we should avoid... The > average user does not give a shiling about JXTemplates, JXPath, JEXL > or whatever load of letters we decide to acronymize today. > > The user wants to know how can he set up his ubercool website > accessing XML documents and SQL data with the mimimum of fuss, and > hence, the document he is looking for is a step by step guide to do that. > > In one of those steps, he's shown how to get a needed parameter > from the context, using our recommended method (JXTemplateTransformer, > through a JXPath expression). There, on a side note, you can have an > overview on what JXTemplateTranformer is, why is it our preferred > method to access the parameter he needs and wich alternatives he could > use, and pointers to the wikiPages of the related tecnologies for a > deeper study if he needs it. > I have to disagree a bit here.... When I started with cocoon, I wanted to load a simple result set from a database into an xml file and transform it. simple enough. I wanted to use jxtemplate .. it was what everyone suggested. but no one it seemed, could tell me why both ${var} and #{var} both worked.. and in fact in my use case, one didn't. So I was faced with learning 2 expression syntaxes, with a deadline facing me. This was a week long agony for me and I ended up using xsp because there was a n00b tutorial up and I could make it work. Now, most of my stuff is based on xsp for the datbase queries. I have moved into other advancements since then like woody and flow, but now I have to look at refactoring from xsp if I want to keep up with cocoon develpment. ( Don't get me wrong here, basically xsp exists to use esql in my mind.. the rumblings of change there are a good idea ) JD --------------------------------------------------------------------- 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]