spring-guides / gs-accessing-data-rest Goto Github PK

Sorry to complain but I wasted 2 days trying to figure out why I was only getting 404 from my tests with MockMvc and in-container. I set up my project with the defaults, I hardly changed anything, yet the URL to the webservices is prefixed with '/data/'. It would have saved a lot of frustration if you'd mentioned it.

In the getting started guide the code examples can't be found (see image).

as the title

Hello,
I wonder how to define rules (ideally of a desclarative kind) to change what is exposed by the rest API.
Example:
Entity: id:0, name:John, surname: Doe
should be exposed via Rest-API (by ommitting the DB ID and concatenating name and surname) as
Rest: userName: "John Doe"

Is there a lightweight declarative way to define such mapping and exclusion rules (for example in the entity)?
Would be nice if you could provide a brief simple example / link. :)

I tried to post but I get an error 405 : method not allowed how can we solve that?
https://stackoverflow.com/questions/36854326/how-to-enable-post-put-method-for-spring-data-jpa-rest-error-405-method-no

I followed the tutorial without issue and then I tried to mess with things a bit.

In the "Create a Person Repository" section a note states: "@RepositoryRestResource is not required for a repository to be exported. It is used only to change the export details, such as using /people instead of the default value of /persons."

So, I tried to remove the @RepositoryRestResource and checked if the person resources were still available in the service; clearly they weren't.

So either either I don't understand the meaning of "exporting a repository" or the @RepositoryRestResource is actually necessary for Spring Data REST to do its magic.

Windows Command Prompt treats quotes differently when compared to the Unix shell and this causes an error when the developer tries to create a new person using cURL to post data.

> curl -X POST -d '{"firstName": "Bilbo", "lastName": "Baggins"}' -H 'Content-Type:application/json' localhost:8080/people
curl: (6) Could not resolve host: Bilbo,
curl: (6) Could not resolve host: lastName
curl: (3) [globbing] unmatched close brace/bracket in column 8
{"cause":null,"message":"No suitable HttpMessageConverter found to read request body into object of type class hello.Person from request with content type of application/x-www-form-urlencoded;charset=UTF-8!"}

The solution is to change the single quotes to double quotes and escape properly que double quotes inside the data:

> curl -X POST -d "{\"firstName\": \"Bilbo\", \"lastName\": \"Baggins\"}" -H "Content-Type:application/json" localhost:8080/people
{
  "firstName" : "Bilbo",
  "lastName" : "Baggins",
  "_links" : {
    "self" : {
      "href" : "http://localhost:8080/people/1"
    },
    "person" : {
      "href" : "http://localhost:8080/people/1"
    }
  }
}

The previous command works on Windows and also on the Unix shell. Also that's the way it's described in the cURL manual:

If you want the parameter to contain spaces, you must enclose the entire
parameter within double quotes ("). Within those quotes, you specify a
quote as ".

This is not a huge problem and also makes the command a little harder to read and to write, but it made review all my code from the tutorial many times, since I thought I was leaving something behind. I think this could happen to others too, since this tutorial is aimed for people who are new to Spring.

The guide discusses orders being used as rel in the _embedded section after data has been PUT to the server. However, this is a bug in Spring Data REST as it should be consistent with the customized resource rel in @RepositoryRestResource on PersonRepository.

I've filed and fixed DATAREST-261 so that we can tweak this once we shipped 2.0.1.

An ongoing task is to keep the Spring Boot version current in the build files:

To do so, update the following files:

complete/build.gradle
complete/pom.xml
initial/build.gradle
initial/pom.xml

When i am trying for http://localhost:8080/people with Headers "Accept: application/schema+json" then the application is giving stack overflow error.

the guides works fine for version 1.5.10.release;
but not work for starter-data-rest version 2.0.0.release when i try to test code by myself, got exception:

...
Caused by: java.lang.IllegalArgumentException: At least one JPA metamodel must be present!
...

and I've clone the bench upgrade-to-boot-2 then run the code but still not fine.
resolved it by add
@EnableAutoConfiguration(exclude={JpaRepositoriesAutoConfiguration.class})
in Application.java
and i'm find other solutions.

how i can make configuration in web.xml, i found only using servlet 3.0 ?

See https://twitter.com/magomi/status/793790427728150528

We should probably re-deploy the guide or something?

There seems to be a minor typo in this sentence:

Spring Data REST also has two methods on RepositoryRestConfiguration.setReturnBodyOnCreate(…) and setReturnBodyOnCreate(…) ...

I'm not sure if the intention was to refer to setReturnBodyOnUpdate(…), or some other method #

I got a 404 when I place the Person and PersonRepository files on a different packages.
@componentscan doesn't give the solution. I have an existing @RestController with /login /test endpoints. Any help on what might be the cause?

In the documentation it is mentioned that:

Spring Data REST is a Spring MVC application. The @Import(RepositoryRestMvcConfiguration.class) annotation imports a collection of Spring MVC controllers, JSON converters, and other beans needed to provide a RESTful front end. These components link up to the Spring Data JPA backend.

However @Import(RepositoryRestMvcConfiguration.class) is not used anywhere in the sample app.