[ 
https://issues.apache.org/jira/browse/DERBY-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Waagan updated DERBY-2559:
-----------------------------------

    Fix Version/s: 10.3.2.2

Merged patches 1 and 2 to 10.3 with revision 632274.
Tests ran cleanly.

For 10.2, the merge also worked (except that the test changes were skipped 
because the file doesn't exist), but I got one error:
derbyall/derbyall.fail:lang/timestampArith.java.
I also got this failure without the merge as well. I don't have time to 
investigate, so I will hold back the merge to 10.2.
If anyone wants to merge the fix, please go ahead.

If this issue is still open in one week, I'll mark it resolved.

> 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.1.4, 10.4.0.0
>            Reporter: Myrna van Lunteren
>            Assignee: Kristian Waagan
>             Fix For: 10.3.2.2, 10.4.0.0
>
>         Attachments: derby-2559-1a.diff, derby-2559-2a-defenses.diff, 
> derby-2559-3a-documentation.diff, derby-2559-3b-documentation.diff
>
>
> 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.

Reply via email to