[
https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829604#comment-16829604
]
Andi Huber commented on ISIS-2020:
----------------------------------
If you do worry about our announcement of dropping JDO support with v2, well we
are also discussing the possibility to postpone this step to version 3. Things
are not cut in stone yet.
The 'v2' Milestone 2 release, apart from some minor known issues, appears to be
solid enough for production use. So we are thinking about making v2 final,
which also requires to cleanup the ascii docs. Then do the JDO drop (replaced
by Spring Data) with version 3.
> Experimental Support for DataNucleus Federated Datastore
> --------------------------------------------------------
>
> Key: ISIS-2020
> URL: https://issues.apache.org/jira/browse/ISIS-2020
> Project: Isis
> Issue Type: New Feature
> Components: Core: Objectstore: JDO
> Affects Versions: 1.16.2, 2.0.0-M1
> Reporter: Brian Kalbfus
> Assignee: Andi Huber
> Priority: Minor
> Fix For: 2.0.0
>
> 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)
