I've got an application that uses esql in XSP pages for database access.
I use an <esql:error-results> block to collect any error messages and pass them to the user.
This works most of the time, e.g. when my XSP page has a wrong table name or there is a permissions error: the error is reported in the output of the XSP page and I'm able to show it to the user.
However, when the database is stopped, and I run an XSP page with a query, no error is reported; there are simply no rows returned. (Actually, sometimes the query just hangs and doesn't return; other times, it returns but there are no result rows.) So I don't see a way to distinguish between "your query ran successfully and the answer is an empty set" and "couldn't connect to the database". To the user, the difference is large. I've found it very mysterious to run a query and "discover" that all the data had disappeared.
Could this be due to some problem in the type of db connection I'm using? The datasource config in cocoon.xconf looks like:
<jdbc name="GEM-Ethnologue-SQLServer-reader">
<pool-controller min="5" max="10" oradb="true"/>
<dburl>jdbc:Microsoft:sqlserver://localhost:1433;DatabaseName=ethnolog;SelectMethod=Cursor;</dburl>
<user>...</user>
<password>...</password>
<autocommit>true</autocommit>
</jdbc>
Thanks...
Lars
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
