tomcat-taglibs-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hans Bergsten <>
Subject Re: JSTL1.1 and DataSource problems
Date Tue, 08 Jun 2004 19:57:29 GMT
Another possible cause is that EL expressions are not evaluated.
If you use JSTL 1.1, make sure you're using a Servlet 2.4 web.xml
file to enable EL evaluation:



Kris Schneider wrote:
> Huh. That's usually triggered by basic config problems like not having the
> driver available to the classloader or using a bad connection string/URL. How
> 'bout doing a quick test in your listener to be sure it's actually set up
> correctly? In other words, once the listener has the DataSource, try just
> getting a connection from it. Did you only upgrade Standard/JSTL, or did
> anything else in your environment change?
> Quoting Frank Burns <>:
>>I'm using Tomcat 5.0.16.
>>I've just upgraded from jakarta-taglibs-standard-1.0.5 to
>>I have a JSP containing this JSTL:
>><sql:query var="results" dataSource="${applicationScope.dataSource}">
>> SELECT * FROM System WHERE Id=1
>>where applicationScope.dataSource is a DataSource that I place in the
>>application scope via a listener.
>>This worked before my upgrade, but now I get this error:
>>[ServletException in:/sysAdminModule/banners/generalBanner.jsp] Unable to
>>get connection, DataSource invalid: "java.sql.SQLException: No suitable
>>Any ideas why this worked with JSTL1.0 and now, with JSTL1.1, it does not?

Hans Bergsten                                  <>
Gefion Software                       <>
Author of O'Reilly's "JavaServer Pages", covering JSP 2.0 and JSTL 1.1
Author of O'Reilly's "JavaServer Faces", covering JSF 1.0
Details at                              <>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message