[ 
http://issues.apache.org/jira/browse/DERBY-1897?page=comments#action_12442977 ] 
            
Myrna van Lunteren commented on DERBY-1897:
-------------------------------------------

The same problem occurs without the 'old' test harness, i.e. when I run:

j9 -jcl:foun10 -Xbootclasspath/a:c:\wctme5.7\ive\lib\jdbc.jar 
junit.textui.TestRunner 
org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite 

I see the same error:

Failed to invoke suite():java.lang.NoClassDefFoundError: 
javax.sql.PooledConnection

In actual fact, indeed the javax.sql.PooledConnection isn't in the jdbc.jar I 
have for/from this product.
Should it be there? 

Myrna



> junit test jdbcapi/_Suite fails with wctme5.7_foundation (j9 -jcl:foun) with 
> NoClassDefFoundError: javax.sql.PooledConnection
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1897
>                 URL: http://issues.apache.org/jira/browse/DERBY-1897
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.2.1.6, 10.3.0.0
>         Environment: windows with wctme5.7's jcl:foun implementation of JSR 
> 169 - j9_foundation or wctme5.7_foundation.
>            Reporter: Myrna van Lunteren
>            Priority: Minor
>
> Running the jdbcapi/_Suite with the test harness with wctme5.7_foundation 
> results in the following error:
> 0 add
> > Failed to invoke suite():java.lang.NoClassDefFoundError: 
> > javax.sql.PooledConnection
> Test Failed.
> This is the only information available.
> This error is especially strange because wctme5.7_foundation should support 
> javax.sql.PooledConnection (in contrast to wctme5.7, which is not JDBC3.0 
> complient).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to