|Anonymous | Login | Signup for a new account||10-26-2021 01:26 PDT|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details [ Jump to Notes ]||[ View Advanced ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0001589||[Resin]||minor||always||01-26-07 09:22||05-23-07 11:24|
|Summary||0001589: jstl sql validation|
(rep by Josh Rehman)
BTW I'm running into more problems with JSTL support (the SQL tags
this time). I will post when I have a good test case.
Well, I don't know what actually causes this, but it turns out that if
your deployment descriptor is 2.3 and you try to use the JSTL SQL tags
(any implementation) you get weird runtime errors:
DataSource invalid:"java.sql.SQLException: No suitable driver"
This was a really weird problem because it has nothing to do with not
being able to find a class on the classpath. I spent 4 hours today
testing various combinations of servers before I realized the version
attribute of my deployment descriptor was to blame. The same error
occured in Tomcat 5.5, too.
It would be nice if the JSTL tags made some assertion about their
environment, but that's hardly a Resin bug, except insofar as it's
internal "fast" implementation should probably do the same. If the
tags had failed fast I would have been saved a lot of frustration!
|There are no notes attached to this issue.|
|01-26-07 09:22||ferg||New Issue|
|05-23-07 11:24||ferg||Assigned To||=> ferg|
|05-23-07 11:24||ferg||Status||new => closed|
|05-23-07 11:24||ferg||Resolution||open => fixed|
|05-23-07 11:24||ferg||Fixed in Version||=> 3.1.2|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
26 total queries executed.|
24 unique queries executed.