Is your JSP in docroot or within a web app?
I wonder if this is related to a performance change that we made that
remove the derby libraries from the launcher class loader of the app
server, and put them only in the common class loader. This was done in
revision 41690 as part of fixing issue 13612.
Tom
On 1/3/2011 2:45 PM, Doug Donahue wrote:
> When using a the <sql:query> JSTL tag in a JSP page I am seeing the
> following failure.
>
> Could not execute the query SELECT * FROM jstl_tab1
> when using jdbc:derby://localhost:1527/derbyDB;create=true,org.apache.derby.jdbc.ClientDriver,cts1,cts1
> for the dataSource attribute! The Exception that was raised is:javax.servlet.jsp.JspException: Unable to get connection, DataSource invalid: java.sql.SQLException: No suitable driver found for jdbc:derby://localhost:1527/derbyDB;create=true
>
> Now if I copy /glassfish3/javadb/lib/derbyclient.jar to
> /glassfish3/glassfish/lib/endorsed/ and run the webapp, the driver is
> found with no issues at all.
>
> Should I have to copy this jarfile into the endorsed dir?
>
> Thanks
> Doug
>
>
>
> Oracle <http://www.oracle.com>
> Doug Donahue| Principal Member of Technical Staff | +1.781.442.2089
> Oracle Java Engineering
> 35 Network Drive
> Burlington, MA 01803
> Douglas.Donahue_at_oracle.com
>
> Green Oracle <http://www.oracle.com/commitment> Oracle is committed
> to developing practices and products that help protect the environment
>
>