Could not resolve view with name 'object/23873278237823/property' in servlet with name 'exporter' about spring-data-rest HOT 7 CLOSED

We talked the other day about how to better support the way views are rendered. It looks like it can't figure out what default view to use. You might try sending an Accept: text/uri-list header to help if resolve the view to use.

from spring-data-rest.

Jon, as always: thank you! :-)

That works. May I help you updating the docs for workarounds like that?

from spring-data-rest.

Certainly you may help with the docs! :)

from spring-data-rest.

New snapshots are now available which change the way views are resolved. It should work now without having to specify an Accept header.

I will need to document how the ContentNegotiatingViewResolver is configured so if people want to mix in their own configuration, they'll have some guidance on how to do that.

from spring-data-rest.

Great, checking out and testing directly. :-)

from spring-data-rest.

Hi Jon,
with the new relation was set and it worked fine. But I am getting:
javax.servlet.ServletException: Could not resolve view with name 'org.springframework.data.rest.empty' in servlet with name 'exporter'

What I don't understand is the reason. Because normally, as the relation was set, it should not be empty, or?

from spring-data-rest.

The MVC Configuration has changed slightly w.r.t. the ContentNegotiatingViewResolver. If you look at the configuration now in master, you'll see how that has to be configured to get the right views resolved.

from spring-data-rest.