Skip to content
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

PUT/PATCH does not consider custom Jackson field naming strategy [DATAREST-556] #931

spring-projects-issues opened this issue May 26, 2015 · 1 comment


Copy link

@spring-projects-issues spring-projects-issues commented May 26, 2015

Michael Phlebas opened DATAREST-556 and commented

  1. git clone
  2. use
  3. PUT/PATCH fails. will remove valid property names required by the objectMapper later on.

If one posts camelCase properties instead, the objectMapper will ignore them.

Possible fix is to simply not remove properties so eagerly (Line 170) and let the objectMapper decide.

Affects: 2.2.2 (Evans SR2)

Referenced from: commits 1e223bd, 018fa22, a07697e

Backported to: 2.3.1 (Fowler SR1), 2.2.3 (Evans SR3)

Copy link

@spring-projects-issues spring-projects-issues commented May 26, 2015

Oliver Drotbohm commented

Good catch! I've revised the property handling in DomainObjectMerger and ported the fix back to Evans and Fowler maintenance branches. Snapshots available, feel free to give them a spin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants