Per Kreipke wrote: >>>Personally I much prefer esql to SQLTransformer because I can control >>>the caching in an xsp. >>> >>>Anyway it isn't quite true that you can't do "transformation" in an xsp: >>>I have SQL which is dynamically generated from an xslt transformer which >>>I then feed into my esql. I use the resolver to grab the output of the >>>transformation pipeline. >>> >>> >>> >>> >>Which is what I thought. There doesn't seem to be a use case that can't >>be acomplished one way or the other. >> >> > >Right. But it requires Java coding. The SQL Transformer can be handled by >people without Java skills. > >
Not really. You can use it entirely with XML and some esql tags. you do not *have* to embed any java. -Andy >Per > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, email: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
