I use ESQL, the beginning of my page is like this :
<?cocoon-process type="xsp"?>
<?cocoon-process type="xslt"?>
<?xml-stylesheet href="stylesheets/dynamic-page2html.xsl" type="text/xsl"?>
<xsp:page language="java" xmlns:xsp="http://apache.org/xsp"; 
xmlns:esql="http://apache.org/cocoon/SQL/v2";>
<page>
        <content>
                <esql:connection>
                        <esql:pool>personnel</esql:pool>
                        <esql:execute-query>
                                <esql:query>
                                        select * From AllTask Where 
wfID=<xsp-request:get-parameter name="myID"/>
                                </esql:query>                                   
                                
                                <esql:results>
...

But with this I get an error because of "<xsp-request:get-parameter name="myID"/>" 


-----Original Message-----
From: Scherler, Thorsten [mailto:[EMAIL PROTECTED]] 
Sent: Friday, December 06, 2002 4:12 PM
To: [EMAIL PROTECTED]
Subject: AW: Request parameters for SQL arguments


Is there a reason u don't use esql?

Or do you use esql?

http://enpdata.csit.fsu.edu/cocoon/documents/esql

-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 6. Dezember 2002 16:04
An: [EMAIL PROTECTED]
Betreff: RE: Request parameters for SQL arguments


If I write :
select * From AllTask Where wfID=1 
It's alright, but when I write:
select * From AllTask Where wfID=<xsp:expr><xsp-request:get-parameter 
name="myID"/></xsp:expr> Then I get following error: "typeStatus report message 
descriptionThe requested resource () is not available."

Do I have to add something in my pipeline? 
     <map:pipeline>
    <map:match pattern="workflowmax/view-workflow">
     <map:generate type="serverpages" src="workflowmax/documents/view-workflow.xsp"/>
         <map:transform type="sql">
                <map:parameter name="use-connection" value="personnel"/>
         </map:transform>
         <map:serialize/>
    </map:match>
   </map:pipeline>     

thanks
-----Original Message-----
From: Scherler, Thorsten [mailto:[EMAIL PROTECTED]] 
Sent: Friday, December 06, 2002 3:47 PM
To: [EMAIL PROTECTED]
Subject: AW: Request parameters for SQL arguments


Sorry, that is much better (use <xsp:expr/>):

select * From AllTask Where wfID=<xsp:expr><xsp-request:get-parameter 
name="myID"/></xsp:expr>


-----Ursprüngliche Nachricht-----
Von: Scherler, Thorsten 
Gesendet: Freitag, 6. Dezember 2002 15:44
An: [EMAIL PROTECTED]
Betreff: AW: Request parameters for SQL arguments


select * From AllTask Where wfID=<xsp:expr><xsp-request:get-parameter 
name="myID"/></xsp:expr>

call it like: ../view-workflow?myID=2

-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 6. Dezember 2002 15:41
An: [EMAIL PROTECTED]
Betreff: XSP: Request parameters for SQL arguments


I try to have a variable for my sql query :

select * From AllTask Where wfID=

That variable (wfID=*) is in my url, that means the page is loaded with the adress:

.../view-workflow?myID=2 or .../view-workflow?myID=5

How can I get the variable 2 or 5 and put it in my SQL query? I use a xsp page. In the 
sitemap I have the following pipeline

     <map:pipeline>
    <map:match pattern="workflowmax/view-workflow">
     <map:generate type="serverpages" src="workflowmax/documents/view-workflow.xsp"/>
         <map:transform type="sql">
                <map:parameter name="use-connection" value="personnel"/>
         </map:transform>
         <map:serialize/>
    </map:match>
   </map:pipeline>  

Thank you!

---------------------------------------------------------------------
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]>


---------------------------------------------------------------------
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]>


---------------------------------------------------------------------
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]>

Reply via email to