Uploaded image for project: 'Spring Tool Suite'
  1. Spring Tool Suite
  2. STS-3197

STS 3.2.0.M2 does show invalid Spring-Data-JPA error marker (@NoRepositoryBean)

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 3.1.0.RELEASE, 3.2.0.M2
    • None
    • DATA
    • None
    • Windows7 64bit
      jdk 7 update 7

    Description

      We have been following the "Adding custom behaviour to all repositories" reference
      http://static.springsource.org/spring-data/data-jpa/docs/current/reference/html/#repositories.custom-behaviour-for-all-repositories
      and now have a Custom Repository Interface. After a few tweaks the implementation is working and we can use this in our web application as expected. But the tooling in STS claims that there is an error.

      "Invalid derived query! No property save found for type java.lang.Object CacheAwareRepository.java"
      affected are the following three methods only:

      • T saveAndFlush(final T entity);
      • void deleteAllInBatch();
      • void deleteInBatch(final Iterable<T> entities);

      Please see the attached screenshot

      With STS 3.1.0.Release this error message was also present but only visible in the editor window, not in the package explorer, so we simply ignored it.

      With todays update to STS 3.2.0.M2 it also pops up in the package explorer view and in the marker views.

      There are two things here which are odd:

      1.) Our custom implementation is not even in the same package as the real repositories.

      2.) Our custom implementation is using the (useful/useless?) @NoRepositoryBean annotation which we thought would help tooling to suppress to treat it like a special Spring Data JPA interface.

      Attachments

        Activity

          People

            thon Terry Denney
            philippj Philipp J
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: