1.0.0.RC1 - View Resolvers about spring-data-rest HOT 5 CLOSED

I've fixed the visibility of contentNegotiatingViewResolver() by making all the bean methods public. Sorry for the oversight there. That change will be in the next snapshot.

The results pages do not embed linked entities, they only provide links. This is by design. If there was no corresponding Repository for a linked entity, however, it would render the entity directly into the result document as-is and not as a link.

The data passed to the view is always a Link object, not the entity, so even overriding the view won't get you any closer to rendering entities directly into the result document.

We're always open to discussion, though, so it's not set in stone.

from spring-data-rest.

I'm experimenting with a URL parameter that can turn this behaviour on and off. If you include "returnLinks=false" as a parameter, it will send back the entity rather than generating a link for it. Would that suit your use case better?

from spring-data-rest.

Hi,
first of all thanks for the answer: i think this param can be a very useful solution for my issue.

However i experimented another problem when i try to use your tip:

If there was no corresponding Repository for a linked entity, however, it would render the entity directly into the result document as-is and not as a link.

because trying to exclude from my project one repository, the system seem to ignore the FetchType.LAZY directive on entity relationship involing the entity related to that repository.
This is a serious problem, because my application crash down trying to fetch a large set of data.

I'm evaluating the use of spring data rest web exporter in a project including a large set of jpa repository with a lot of relationship, using hibernate.

from spring-data-rest.

I'm making some changes right now that will actually render the entity directly into the response by default, so this will be one change that might make your use case easier.

As to the eager loading of dependent entities: I haven't extended the support for paging into child relationships yet. I'm hopeful I can get that addition into the next release (probably an RC2).

from spring-data-rest.

It's ok.
This project seem to be very interesting, but only HATEOAS approach in REST doesn't allow the full use in a standard application context for getting a normal list of entities with attributes.
So we expect for a new release
Tks

from spring-data-rest.