[
https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677251#comment-16677251
]
Brian Kalbfus commented on ISIS-2020:
-------------------------------------
This issue is apparently fixed in datanucleus-core 5.2.0-m2 as of 3 days ago.
Andy patched datanucleus-core because it makes more sense there than my one-off
fix of datanucleus-api-jdo. My datanucleus test passes now.
The fix the test project using Isis, I can't simply reference 5.2.0-m2 from the
test project because it is part of isis-core-plugins-jdo-datanucleus-5. Maybe
there is a maven override that allows me to do this. Is there a newer version
of isis-core-plugins-jdo-datanucleus-5 that references the later datanucleus
build?
-Brian
> DataNucleus Federated Datastore functionality not used in query
> ---------------------------------------------------------------
>
> Key: ISIS-2020
> URL: https://issues.apache.org/jira/browse/ISIS-2020
> Project: Isis
> Issue Type: Bug
> Components: Core: Objectstore: JDO
> Affects Versions: 1.16.2, 2.0.0-M1
> Reporter: Brian Kalbfus
> Priority: Major
> Fix For: 1.16.3
>
> Attachments: datanucleus-api-jdo.patch
>
>
> Insert and Update operations work as expected, but query operations operate
> on the primary datastore. I see from stepping through the M1 code that
> Insert and Update operations use a transaction that accesses a
> FederatedDataStore. I guess that is where the difference occurs in that the
> query operations get a data store another way, failing to get the
> FederatedDataStore that is configured.
> example code created from helloworld-archetype is at
> [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
> Mailing list:
> [https://lists.apache.org/thread.html/2edea2f8d802532c3672eddc83b484bbc2e31d1cac16f2759feeb95f@%3Cusers.isis.apache.org%3E]
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
