You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a spring-content application with this entity
Create a new Person instance with POST /persons with an empty object
Notice that in the returned JSON, the link relation and path as specified in @RestResource is not taken into account, it falls back to the default instead. (Note that the annotation does take effect for the "mugshot" content property
Expected behavior
Of course, I expect the settings set in the @RestResource annotations to take effect
If applicable, add screenshots to help explain your problem.
Additional context
I believe the fix is to use the same function used in ContentPropertyMappingContextVisitor in RestResourceMappingBuilder.
The text was updated successfully, but these errors were encountered:
vierbergenlars
changed the title
Link relation and path configured with @RestResource ignored for properties with multiple capital letters
Link relation and path configured with @RestResource ignored for content properties with multiple capital letters
Aug 1, 2023
Describe the bug
This looks like a similar bug as #1146, except now applied to to
RestResourceMappingBuilder
instead ofContentPropertyMappingContextVisitor
.To Reproduce
Given a JPA entity with a
@RestResource
annotation:Steps to reproduce the behavior:
POST /persons
with an empty object@RestResource
is not taken into account, it falls back to the default instead. (Note that the annotation does take effect for the "mugshot" content propertyExpected behavior
Of course, I expect the settings set in the
@RestResource
annotations to take effectScreenshots
If applicable, add screenshots to help explain your problem.
Additional context
I believe the fix is to use the same function used in
ContentPropertyMappingContextVisitor
inRestResourceMappingBuilder
.The text was updated successfully, but these errors were encountered: