> From: Stephen Ng [mailto:[EMAIL PROTECTED]] > > > > > Why not generate SQL string *in* this XSP? That's would give > > the best performance. > > > > Or, other way is to obtain this SQL string into String > > programmatically, without using include.
Here I mean do not use include to include your XSLT generated SQL, but access cocoon programmatically and get this SQL into String. Then, you will have static XSP source. > > > > Okay I understand the suggestion but it doesn't work that well in my > case. The reason is that the sql string is generated as a series of > xslt transforms: Have you considered SQL transformer? It works best here. > <map:match pattern="dynamicSql.sql"> > <map:generate type="request"/> > <map:transform src="stylesheets/requestQuery.xslt"/> > <map:serialize type="text"/> > </map:match> > > And I like this approach, especially since I much prefer writing in XSLT > than in Java. But in theory I could redo my (not trivial) xslt scripts > in Java. > > Could I take the dynamic xslt-generated sql string and shove it into a > cocoon parameter, and then read the parameter inside my xslt? Do you mean "inside my XSP"? Yes, you can do something like this. Vadim > Other > place I thought about about sticking the sql was inside the session or > (shudder) inside a file. > > Steve > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
