Results 1 to 2 of 2

Thread: "Invalid derived query" error not working for Neo4j repositories

  1. #1
    Join Date
    Oct 2004
    Location
    Sydney, Australia
    Posts
    46

    Default "Invalid derived query" error not working for Neo4j repositories

    Hi,

    I just upgraded from STS 3.1.0 to STS 3.2.0 and have noticed that invalid derived queries in Neo4j repositories no longer generate an error. This looks similar to STS-3107. The fix for that issue (commit 307a3a96a4a01c8957eafee075c4f7fb88006f8f) involved specifically adding a check for the "org.springframework.data.jpa.repository" package, so I'm guessing that another will be needed for the "org.springframework.data.neo4j.repository" package, plus more for any other Spring Data projects that use this error and whose repositories follow this package naming pattern.

    Geoff

  2. #2
    Join Date
    Sep 2008
    Location
    Hamburg, Germany
    Posts
    1,638

    Default

    Hey Geoff!

    You are absolutely right, I created this JIRA ticket for this:
    https://issuetracker.springsource.com/browse/STS-3264

    Should be fixed for 3.3.0.M1... :-)

    Thanks for reporting!
    -Martin
    Martin Lippert
    SpringSource, a division of VMware
    SpringSource Tools Team
    http://www.springsource.com
    http://twitter.com/martinlippert

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •