Exposing custom repositories about spring-data-rest HOT 9 OPEN

The exporter currently only exports query methods, not customly implemented ones. Jon and me have already discovered the "issue" and a fix will be part of the next release.

from spring-data-rest.

Oliver, thanks a lot to both of you. I am waiting for it! :-)

from spring-data-rest.

Any news on this enhancement?

from spring-data-rest.

@olivergierke and @jbrisbin, I opened this issue ten months ago. Any chance that it will be included in a further release?

from spring-data-rest.

There is significant work involved in "abstracting the abstractions" to allow for this, particularly in spring-data-commons. A community contribution would be very welcome in this area (and probably the absolute fastest path to implementation).

from spring-data-rest.

I am a bit hesitant on this one and vote to not have a quick shot for it. Here's the rationale:

Currently we expose two major aspects of the repositories. The first one is CRUD methods. This can be done as they map onto HTTP verbs nicely. The second ones are declarative query methods as we can derive a resource identifier as well as the appropriate HTTP method to be used (GET). While we can definitely build up an identifier for the manually implemented method but we cannot derive the appropriate HTTP method by default.

What I can imagine is some sort of annotation that allows to define which method to use (@RequestMapping might be a candidate as well as @RestResource although the latter already seems to suffer from semantic overload depending on where it is used) and the exporter expecting the method to be present.

SD Commons already exposes RepositoryInformation instances through the Repositories helper class. The former already has an isCustomMethod(…) method to detect whether the method to handle is a custom one. Depending on how much time we find in the 1.1.0 timeframe, this might be a candidate for inclusion into this release. But as I said, right now you can simply declare a controller, wire the repo into it and manually map and execute the call, so it's not really a hit the wall scenario.

from spring-data-rest.

Hi,
I would be fine with @olivergierke's suggestion regarding the manual creation of a controllers and afterwards linking the repository methods into it. What would be really helpful to complete the API "style" is that these manually created controllers would be referenced in host:8080/api. Essentially that what I pointed out here: #92

from spring-data-rest.

Having you tried creating a ResourceProcessor<Resource<Link>> to modify the list of repositories?

from spring-data-rest.

Nope, not yet. What would be the way to go here?

from spring-data-rest.