Sorry, but the syntax you were using showed that you
did *not* seem to understand the difference between XSP and XSL;
hence my suggestion to do some background reading -
because that's where I managed to find the info needed
to work with XSP.
Also, before making sarcastic comments, please bear in mind
that not each of us has time to solve someone else's detailed
problems - but we do contribute where and how we are able.
A little common courtesy goes a long way on a mail list
like this....
>>> [EMAIL PROTECTED] 26/11/2002 05:46:14 >>>
Sorry, but that is not the kind of helpful information I am used in this
list. Yes you're right. Mostly any information can be obtained by reading
docs. And yes I know that XSp is not XSL. And yes I searched for examples.
without any succes.
So I will redefine my question. How can I use values obtained by a db query
in my esql in the cinclude statement?
Rob
----- Original Message -----
From: "Derek Hohls" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 26, 2002 3:23 PM
Subject: Re: parameters in xsp don't work
> In short; the syntax inside XSP and XSL is quite different;
> suggest you look at the docs and the Cocoon samples to
> get up-to-speed on how XSP works...
>
> >>> [EMAIL PROTECTED] 26/11/2002 04:16:20 >>>
> I must create an dynamic variable based (from db content) cinclude
> path.
> But this doens't work. Do you know why?
> ...
> <esql:results>
> <esql:row-results>
> <xsl:variable name="id"><esql:get-string
> column="i.id"/></xsl:variable>
> <xsl:variable name="stylesheet-path"><esql:get-string
> column="t.stylesheet"/></xsl:variable>
> <cinclude:include
> src=""/>
> </esql:row-results>
> </esql:results>
> ....
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
>>> [EMAIL PROTECTED] 26/11/2002 05:46:14 >>>
Sorry, but that is not the kind of helpful information I am used in this
list. Yes you're right. Mostly any information can be obtained by reading
docs. And yes I know that XSp is not XSL. And yes I searched for examples.
without any succes.
So I will redefine my question. How can I use values obtained by a db query
in my esql in the cinclude statement?
Rob
----- Original Message -----
From: "Derek Hohls" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 26, 2002 3:23 PM
Subject: Re: parameters in xsp don't work
> In short; the syntax inside XSP and XSL is quite different;
> suggest you look at the docs and the Cocoon samples to
> get up-to-speed on how XSP works...
>
> >>> [EMAIL PROTECTED] 26/11/2002 04:16:20 >>>
> I must create an dynamic variable based (from db content) cinclude
> path.
> But this doens't work. Do you know why?
> ...
> <esql:results>
> <esql:row-results>
> <xsl:variable name="id"><esql:get-string
> column="i.id"/></xsl:variable>
> <xsl:variable name="stylesheet-path"><esql:get-string
> column="t.stylesheet"/></xsl:variable>
> <cinclude:include
> src=""/>
> </esql:row-results>
> </esql:results>
> ....
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
