You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2006/11/19 16:19:38 UTC

[jira] Resolved: (DERBY-1897) junit test jdbcapi/_Suite fails with wctme5.7_foundation (j9 -jcl:foun) with NoClassDefFoundError: javax.sql.PooledConnection

     [ http://issues.apache.org/jira/browse/DERBY-1897?page=all ]

Myrna van Lunteren resolved DERBY-1897.
---------------------------------------

    Fix Version/s: 10.2.1.8
                   10.3.0.0
       Resolution: Fixed

svn merge -r 465019:465020 https://svn.apache.org/repos/asf/db/derby/code/trunk
and committed with: http://svn.apache.org/viewvc?view=rev&revision=476838
M    java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/_Suite.java

> 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
>         Assigned To: Daniel John Debrunner
>            Priority: Minor
>             Fix For: 10.2.1.8, 10.3.0.0
>
>
> 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