> From: Stephen Ng [mailto:[EMAIL PROTECTED]]
>
> Vadim,
>
> >
> > 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.
>
> Sounds good to me but I have absolutely no idea how to do this :-(.
Can
> you give me a pointer?
Pointer: this list archive or dev list archive, this week, something
about resolver.
> > Have you considered SQL transformer? It works best here.
>
> Hmmm, no, will check this out.
Please do, it is more suitable for you.
> > > 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.
> >
>
> Sorry, you are right; that's what I meant. I am having some trouble
> though which is probably related to your first suggestion.
>
> I found this code in the archives:
>
> String myParam = "";
>
> try{
> myParam = parameters.getParameter("GeneratedSQL");
> System.out.println("param is: " + myParam);
> }
> catch (Exception e)
> {}
>
> And so I plug in:
>
> <map:generate type="serverpages"
> src="FileWithCIncludedXspRightNow.xsp">
> <map:parameter name="GeneratedSQL"
> value="cocoon:/generatedSQL.sql"/>
> </map:generate>
>
> But all I get on the console is:
>
> param is: cocoon:/generatedSQL.sql
Yes sure, what you put there is what you get.
And no, (answering your next email), this won't be substituted, never.
Vadim
> Thanks for your help,
>
> 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]>
