Most of my xsp data views relied on the esql:error-results for displaying useful information for the user (error type, means to fix it, etc.), But now, the XSP seems to handle the SQL Exception and convert it to a "java.lang.RuntimeException: Error executing statement" so the error-results tag does not get executed.. Is there some way to avoid this? I'm thinking about trycatching the xsp files, but that'd complicate them too much..
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
