This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
No announcement yet.
Several issues with "adding custom behaviour to all repositories" in spring data jpaPage Title Module
.<init>() just refers to the default constructor of the class.
OOPS. My bad. What are the other dependencies of your project? I am wondering if this could be an dependency management issue. It is kind of desperate but I cannot figure out any other reason for this.
I finally found the reason for this exception: I had forgotten to mark the intermediate interface as @NoRepositoryBean. That solved it.
P.S. I mistakenly filed a bug here https://jira.springsource.org/browse/DATAJPA-234 and realized the bug was on my side.
Same problem here. Just forgot @NoRepositoryBean. When you find the solution and you understand it you keep asking you self why didn't I think of it!! Maybe the annotation should be also included in the example in the reference documentation instead of the note.
I realy don't like this double-interface creation (one resolved by QueryDSL and one containing custom quries) for using both QuerDSL power and custom implementations. I wish there was a way creating only one interface and only one implementation class...