Issue Details (XML | Word | Printable)

Key: DERBY-2559
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Kristian Waagan
Reporter: Myrna van Lunteren
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Derby

recreating a datasource using javax.naming.Reference from a ClientDataSource40 fails

Created: 17/Apr/07 09:26 PM   Updated: 10/Mar/08 02:43 PM
Return to search
Component/s: Network Client
Affects Version/s: 10.3.1.4, 10.4.1.3
Fix Version/s: 10.3.3.0, 10.4.1.3

Time Tracking:
Not Specified

File Attachments:
  Size
File Licensed for inclusion in ASF works derby-2559-1a.diff 2008-01-30 03:39 PM Kristian Waagan 3 kB
File Licensed for inclusion in ASF works derby-2559-2a-defenses.diff 2008-02-15 12:24 PM Kristian Waagan 2 kB
File Licensed for inclusion in ASF works derby-2559-3a-documentation.diff 2008-02-15 12:24 PM Kristian Waagan 6 kB
File Licensed for inclusion in ASF works derby-2559-3b-documentation.diff 2008-02-18 09:05 AM Kristian Waagan 6 kB

Resolution Date: 10/Mar/08 02:43 PM


 Description  « Hide
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).

     

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
No work has yet been logged on this issue.