You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jdo-dev@db.apache.org by "Michael Bouschen (JIRA)" <ji...@apache.org> on 2018/01/12 21:39:00 UTC

[jira] [Updated] (JDO-769) Revise PMFMapMapTest test cases using two class loaders

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

Michael Bouschen updated JDO-769:
---------------------------------
    Attachment: JDO-769-patch.txt

Attached patch JDO-769-patch.txt for review. It uses the current class loader as the pmfLoader when calling JDOHelper.getPersistenceManagerFactory taking two class loaders.

> Revise PMFMapMapTest test cases using two class loaders
> -------------------------------------------------------
>
>                 Key: JDO-769
>                 URL: https://issues.apache.org/jira/browse/JDO-769
>             Project: JDO
>          Issue Type: Improvement
>          Components: api
>    Affects Versions: JDO 3.1
>            Reporter: Michael Bouschen
>            Assignee: Michael Bouschen
>             Fix For: JDO 3.2
>
>         Attachments: JDO-769-patch.txt
>
>
> The two test methods testNamedPMFWithOverridesAndTwoLoaders and testNamedPMFWithTwoLoaders of PMFMapMapTest call JDOHelper methods getPersistenceManagerFactory taking two class loaders: one to use for loading resources and 
> the other to use for loading the PMF. The changes to fix JDO-768 made clear that the test cases pass the same class loader for both arguments. It looks like the tests do not test what they intended to test.
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)