Uploaded image for project: 'Spring Data Commons'
  1. Spring Data Commons
  2. DATACMNS-1174

Improve error reporting for not supported repository interfaces

    XMLWordPrintable

    Details

      Description

      Composing a repository from Spring Data-provided interfaces that are not supported (due to their nature or not implemented by a particular store) causes confusing exceptions like

      • PropertyReferenceException: No property findAll found for type Person
      • PropertyReferenceException: No property save found for type Person

      These cases occur in following arrangements:

      • Declaring a reactive Spring Data JPA repository
      • Declaring a Querydsl repository in a store not supporting Querydsl
      • Declaring PagingAndSortingRepository in a Spring Data for Apache Cassandra repository

      In such case, we should rather report that the repository is not supported because we have no implementation for the repository interface fragment which causes the issue and not because we can't derive a query.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mp911de Mark Paluch
              Reporter:
              mp911de Mark Paluch
              Last updater:
              Spring Issues Spring Issues
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: