QueryDslPredicateExecutor more subclass friendly about spring-data-jpa HOT 3 CLOSED

Could you please open a ticket at https://jira.springsource.org/browse/DATAJPA? We usually start quite conservative with the API we expose but there's actually nothing the speaks against opening that up a little. Making createQuery(…) protected should do the trick if I got you correctly, right?

If you're just looking for help implementing repositories manually take a look at QueryDslRepositorySupport as well as the according QueryDslRepositorySupportTests for example usage.

Cheers,
Ollie

from spring-data-jpa.

Thanks for the reply. I will open a ticket. Making createQuery() protected
would perfectly work for my use case.

Isn't QueryDslRepositorySupport only usable when I try to add behaviour to a
single repository? Or can I use it for adding behaviour to all repositories?

Thanks for the help
Ralph

On Fri, Mar 25, 2011 at 1:35 PM, olivergierke <
[email protected]>wrote:

Could you please open a ticket at
https://jira.springsource.org/browse/DATAJPA? We usually start quite
conservative with the API we expose but there's actually nothing the speaks
against opening that up a little. Making createQuery() protected should do
the trick if I got you correctly, right?

If you're just looking for help implementing repositories manually take a
look at QueryDslRepositorySupport as well as the according
QueryDslRepositorySupportTests for example usage.

Cheers,
Ollie

Reply to this email directly or view it on GitHub:
#2 (comment)

from spring-data-jpa.

Considering:

A) QuerydslJpaPredicateExecutor now has createQuery() protected (as suggested by @odrotbohm),

and

B) QuerydslRepositorySupport has everything protected as well, meaning you can really control everything you need

...I think we can close this ticket.

To answer the last question, is it possible to apply QuerydslRepositorySupport to multiple repositories at once, perhaps. You can extend QuerydslRepositorySupport and plug in all the parts as needed, but leave the Class<?> domainClass portion open. This doesn't totally take it off your hands, but should make things operate as desired.

from spring-data-jpa.