db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2559) recreating a datasource using javax.naming.Reference from a ClientDataSource40 fails
Date Tue, 17 Apr 2007 21:27:15 GMT
recreating a datasource using javax.naming.Reference from a ClientDataSource40 fails
------------------------------------------------------------------------------------

                 Key: DERBY-2559
                 URL: https://issues.apache.org/jira/browse/DERBY-2559
             Project: Derby
          Issue Type: Bug
          Components: Network Client
    Affects Versions: 10.3.0.0
            Reporter: Myrna van Lunteren


Consider the following code snippet from test DataSourceReferenceTest:
--------------------
        Referenceable refDS = (Referenceable) ds;
        Reference dsAsReference = refDS.getReference();
        String factoryClassName = dsAsReference.getFactoryClassName();
        ObjectFactory factory = 
            (ObjectFactory) Class.forName(factoryClassName).newInstance();  
        Object recreatedDS = 
            factory.getObjectInstance(dsAsReference, null, null, null);
---------------------

When ds is a ClientDataSource40 (i.e. when running with jdk16), recreatedDS is null.

Note, that this showed up only after converting the test to junit, because the original test
hardcoded the ds to be a ClientDataSource. I confirmed this not to be related to my changes
for DERBY-2296 (which prompted me to convert the test), by backing out my changes to ClientBaseDataSource
and client/am/Connection and rerunning the test (needed some minor adjustments of expected
values table/array).

     

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message