[jira] Updated: (DERBY-2559) recreating a datasource using javax.naming.Reference from a ClientDataSource40 fails

["Kristian Waagan (JIRA)" <ji...@apache.org>]

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

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

           Derby Info:   (was: [Patch Available])
    Affects Version/s: 10.4.0.0

Committed 'derby-2559-1a.diff' to trunk with revision 617492.
This commit is an incremental fix. More thought must be put into how the object factory is to be well behaved.
The factory will now create all the client data source objects, but it might/will fail if another type of object (or null) is passed as the first argument.

I'm also thinking about porting the fix to 10.3.

> 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.4.0.0
>
>         Attachments: derby-2559-1a.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.