Vadim, My parade was to do achieve the following:
1. Excite a final decision on whether the SQLTransformer is deprecated or not 2. Excite an effort (if not) to clean both SQLTransformer and ESQL if not (SQLTransformer is *slow*) It sounds like the answer is there is a need still for SQLTransformer. Once I'm done with the tasks I'm working on right now, I'll look into working to combine their sharable codebases and make them prettier/faster. -Andy Vadim Gritsenko wrote: >>From: Luca Morandini [mailto:[EMAIL PROTECTED]] >>Sent: Saturday, July 13, 2002 1:29 PM >>To: [EMAIL PROTECTED] >>Subject: RE: [PROPOSAL] Remove SQLTransformer in 2.1 >> >> >>Vadim & Andrew, >> >>first: >>thanks. >> >>second: >>I don't want to rain on your parade, but... >> >> > >It's not my parade, it's Andrew's: I merely stating possibilities :) > > > > >>from an architectural point of view: is >> >> >"resolver.resolve("cocoon://dynamic- > > >>sql")" in XSP so much better than "document()" in XSLT ? >> >> > >No. > > > > >>Yes, the first is cached, and I agree (up to a point, though) that SQL >> >> >queries > > >>belong to generation rather than transformation, but >>this resolver breaks the beauty of the sitemapm: having all pipelines >> >> >pieces > > >>in one place. >> >> > >SQLTransformer also could be made cacheable, by configuring expiration >time for different SQL queries or pages. > > >Vadim > > > > >>Anyway, I think that this concern may be overcome when the URI is >> >> >passed to > > >>the resolver via a sitemap parameter... I should try >>this. >> >>Best regards, >> >>P.S. >>A personal note, I use SQLTransformer not because "ESQL is more hidden >> >> >in the > > >>documentation" but because it supported stored >>procedures long before EQSL. >> >>--------------------------------------------- >> Luca Morandini >> GIS Consultant >> [EMAIL PROTECTED] >>http://utenti.tripod.it/lmorandini/index.html >>--------------------------------------------- >> >> >> >> >>>-----Original Message----- >>>From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] >>>Sent: Saturday, July 13, 2002 4:27 PM >>>To: [EMAIL PROTECTED] >>>Subject: RE: [PROPOSAL] Remove SQLTransformer in 2.1 >>> >>> >>> >>> >>>>From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]] >>>> >>>>Vadim Gritsenko wrote: >>>> >>>> >>>> >>>>>>From: Luca Morandini [mailto:[EMAIL PROTECTED]] >>>>>> >>>>>>Andrew, >>>>>> >>>>>>do you mind terribly showing an example of an ESQL feeded by >>>>>>a dynamic query produced by XSLT ? >>>>>> >>>>>> >>>>>I don't mind. Moreover, something tells me I already answered >>>>> >>>>> >similar > > >>>>>question on user list... >>>>> >>>>>Will it help you if I answer? >>>>> >>>>> >>>>> >>>>If he isn't interested in your answer than I am! So please fire >>>> >>>> >away > > >>>>:-) (Then I'll document it in a couple days) >>>> >>>> >>>Here it is (untested, from the top of my head): >>> >>><xsp:logic> >>> String query; >>> Source source; >>> try { >>> source = resolver.resolve("cocoon://dynamic-sql"); >>> BufferedReader r = >>> new BufferedReader( >>> new InputStreamReader(source.getInputStream())); >>> StringBuffer sb = new StringBuffer(); >>> for (String s=r.readLine(); s != null; s=r.readLine()) >>> sb.append(sb); >>> } finally { >>> source.recycle(); >>> } >>></xsp:logic> >>> >>>Then follows your esql code (syntax of esql I do not know 'cause >>> >>> >never > > >>>used it ;). >>> >>>PS Snippet above could be a prototype for <util:include-uri >>>as="string"/> >>> >>>PPS I assume here that cocoon://dynamic-sql has text serializer. >>> >>>Vadim >>> >>> >>> >>> >>> >>> >--------------------------------------------------------------------- > > >>>To unsubscribe, e-mail: [EMAIL PROTECTED] >>>For additional commands, email: [EMAIL PROTECTED] >>> >>> >>> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, email: [EMAIL PROTECTED] >> >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, email: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
