[jira] [Reopened] (ISIS-2020) DataNucleus Federated Datastore functionality not used in query
[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber reopened ISIS-2020: -- Assignee: Andi Huber As Brian pointed out there is at least two parts to this issue, where one was just fixed on DN's side, while the other could be a bug with Isis. I can reproduce the 'listAll' not working part, as demonstrated with the github example [1] and as described with steps to reproduce from the user mailing list. 1) create some instances of HelloOtherWorldObject from the "Other" menu: "1", "2", and "3" 2) then 'listAll' HelloOtherWorldObject instances via the "Other" menu, shows no result [1] [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1] > 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 >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > 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)
[jira] [Updated] (ISIS-2020) DataNucleus Federated Datastore functionality not used in query
[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-2020: - Fix Version/s: (was: 1.16.3) 2.0.0-M2 > 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 >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > 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)
[jira] [Commented] (ISIS-2020) DataNucleus Federated Datastore functionality not used in query
[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677341#comment-16677341 ] Brian Kalbfus commented on ISIS-2020: - I updated [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1] with substituting the latest datanucleus-core 5.2 jar. It makes use of a dependency exception and redeclaring the datanucleus maven plugin in the child pom. The findByName action works, but listAll does not work with this code - Please advise on how to get listAll to work. > 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)
[jira] [Comment Edited] (ISIS-2020) DataNucleus Federated Datastore functionality not used in query
[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677251#comment-16677251 ] Brian Kalbfus edited comment on ISIS-2020 at 11/6/18 9:32 PM: -- 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. To 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 was (Author: bkalbfus): 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)
[jira] [Commented] (ISIS-2020) DataNucleus Federated Datastore functionality not used in query
[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (ISIS-2028) Bundled Jetty cannot launch with new Byte-Buddy 1.9.2 in place
[ https://issues.apache.org/jira/browse/ISIS-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676676#comment-16676676 ] ASF subversion and git services commented on ISIS-2028: --- Commit ffe34e02eefeead799d6b06fbb71f584b46b99cf in isis's branch refs/heads/v2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=ffe34e0 ] ISIS-2028: examples: override incode properties Task-Url: https://issues.apache.org/jira/browse/ISIS-2028 > Bundled Jetty cannot launch with new Byte-Buddy 1.9.2 in place > -- > > Key: ISIS-2028 > URL: https://issues.apache.org/jira/browse/ISIS-2028 > Project: Isis > Issue Type: Bug > Components: Core >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > Jetty fails to launch due to discovery of a module-info.class in the > byte-buddy jar. > Updating the Jetty version [1] to 9.4.12 might do the trick. > [1] https://www.eclipse.org/lists/jetty-announce/msg00124.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ISIS-2028) Bundled Jetty cannot launch with new Byte-Buddy 1.9.2 in place
[ https://issues.apache.org/jira/browse/ISIS-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676677#comment-16676677 ] ASF subversion and git services commented on ISIS-2028: --- Commit ffe34e02eefeead799d6b06fbb71f584b46b99cf in isis's branch refs/heads/v2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=ffe34e0 ] ISIS-2028: examples: override incode properties Task-Url: https://issues.apache.org/jira/browse/ISIS-2028 > Bundled Jetty cannot launch with new Byte-Buddy 1.9.2 in place > -- > > Key: ISIS-2028 > URL: https://issues.apache.org/jira/browse/ISIS-2028 > Project: Isis > Issue Type: Bug > Components: Core >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > Jetty fails to launch due to discovery of a module-info.class in the > byte-buddy jar. > Updating the Jetty version [1] to 9.4.12 might do the trick. > [1] https://www.eclipse.org/lists/jetty-announce/msg00124.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ISIS-2028) Bundled Jetty cannot launch with new Byte-Buddy 1.9.2 in place
[ https://issues.apache.org/jira/browse/ISIS-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676619#comment-16676619 ] ASF subversion and git services commented on ISIS-2028: --- Commit 9c575cb7d92eacd0483f44dc754e96b6502f2ed7 in isis's branch refs/heads/v2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=9c575cb ] ISIS-2028: bump bundled jetty 9.4.3->9.4.12 Task-Url: https://issues.apache.org/jira/browse/ISIS-2028 > Bundled Jetty cannot launch with new Byte-Buddy 1.9.2 in place > -- > > Key: ISIS-2028 > URL: https://issues.apache.org/jira/browse/ISIS-2028 > Project: Isis > Issue Type: Bug > Components: Core >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > Jetty fails to launch due to discovery of a module-info.class in the > byte-buddy jar. > Updating the Jetty version [1] to 9.4.12 might do the trick. > [1] https://www.eclipse.org/lists/jetty-announce/msg00124.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ISIS-2028) Bundled Jetty cannot launch with new Byte-Buddy 1.9.2 in place
[ https://issues.apache.org/jira/browse/ISIS-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676620#comment-16676620 ] ASF subversion and git services commented on ISIS-2028: --- Commit 9c575cb7d92eacd0483f44dc754e96b6502f2ed7 in isis's branch refs/heads/v2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=9c575cb ] ISIS-2028: bump bundled jetty 9.4.3->9.4.12 Task-Url: https://issues.apache.org/jira/browse/ISIS-2028 > Bundled Jetty cannot launch with new Byte-Buddy 1.9.2 in place > -- > > Key: ISIS-2028 > URL: https://issues.apache.org/jira/browse/ISIS-2028 > Project: Isis > Issue Type: Bug > Components: Core >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > Jetty fails to launch due to discovery of a module-info.class in the > byte-buddy jar. > Updating the Jetty version [1] to 9.4.12 might do the trick. > [1] https://www.eclipse.org/lists/jetty-announce/msg00124.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ISIS-2028) Bundled Jetty cannot launch with new Byte-Buddy 1.9.2 in place
[ https://issues.apache.org/jira/browse/ISIS-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber reassigned ISIS-2028: Assignee: Andi Huber > Bundled Jetty cannot launch with new Byte-Buddy 1.9.2 in place > -- > > Key: ISIS-2028 > URL: https://issues.apache.org/jira/browse/ISIS-2028 > Project: Isis > Issue Type: Bug > Components: Core >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > Jetty fails to launch due to discovery of a module-info.class in the > byte-buddy jar. > Updating the Jetty version [1] to 9.4.12 might do the trick. > [1] https://www.eclipse.org/lists/jetty-announce/msg00124.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
