Thanks to David,

really, that was helpful! I also found out that I have to remove <esql:results>.
Then everything works fine.

I was near to cancelling the use of cocoon and mySQL for my project.

Now I only need a good user authentification against the database.
I'm planning to create sessions in Cocoon2/Tomcat4 and use session
variables to store user login information and then construct the <esql:dburl>
from these values. Is this a good idea? Any comments?

Uwe Stelzer


----- Original Message ----- 
From: "David Rosenstrauch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 26, 2001 6:28 PM
Subject: Re: Cocoon2 & mySQL database update query with success/failure differentiation


> Try using:
> 
> <esql:error-results>
>      <esql:get-message/>
> </esql:error-results>
> 
> 
> DR
> 
> 
> 
> At 05:42 PM 12/26/01 +0100, you wrote:
> >Hello everybody,
> >
> >I have the following problem and for me it is hard to tell where the reasons are:
> >
> >I am trying to send an insert query to mySQL from an XSP-Page processed  by
> >Cocoon 2.
> >
> >If successful the resultpage shall yield some hopebringing comment, for
> >example which values have been inserted.
> >
> >If the update fails (because of a SQLException) I need to tell it to the user.
> >
> >Therefore I have tried to use the <esql:results> and <esql:no-results> tags
> >from the esql-taglib (this once worked fine with Cocoon 1 and Oracle 8). But
> >with mySQL and Cocoon 2 it just won't work. Either I get always only success
> >messages even if the query fails, or no text at all.
> >
> >Has anybody experiences with this or knows an answer that could help?
> >
> >Thanks,
> >Uwe Stelzer
> >
> >
> >Here is the source of my XSP page:
> >
------------ snip --------------


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

Reply via email to