New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Insufficient check for the presence of a PersistentProperty in MappedProperties [DATAREST-575] #949
Comments
Petar Tahchiev commented I forgot to mention I'm on
and I can see that it succeeds for 5 times, but the sixth execution has |
Ben Madore commented This looks like the same issue as i reported just last night. https://jira.spring.io/browse/DATAREST-574 - check it out does that seem to match your use case? |
Oliver Drotbohm commented
|
Petar Tahchiev commented
|
Petar Tahchiev commented OK, it fails when trying to PATCH a property of type
and the exception is:
because on that line the
I will come up with a simple repository to reproduce this problem later today or tomorrow |
Bryan M. Kramer commented It would be really nice if after line 174 in spring-data-rest/spring-data-rest-webmvc/src/main/java/org/springframework/data/rest/webmvc/json/DomainObjectReader.java I am seeing this a lot, but regardless of the cause, an exception with the field name would make it so much easier to debug |
Oliver Drotbohm commented Bryan M. Kramer — Care to elaborate how It'd be really cool to see a test case that actually reproduces said behavior |
Oliver Drotbohm commented Nevermind. The culprit are properties that are Jackson ones, but not Spring Data persistent properties (e.g. ones with |
Oliver Drotbohm commented That's in place, feel free to give the snapshots a try |
Petar Tahchiev opened DATAREST-575 and commented
Hello,
I just issued a PUT request towards my
/rest/variant/564477030778624
and I got the following exception:Affects: 2.4 M1 (Gosling)
Issue Links:
("is duplicated by")
Referenced from: commits a516d8e, 6d1dc36, c5948e6
Backported to: 2.5.5 (Hopper SR5), 2.4.7 (Gosling SR7)
1 votes, 5 watchers
The text was updated successfully, but these errors were encountered: