Skip to content

Documentation improvement: JAXB/Jackson vs JAXB/JSON #554

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

Closed
behrangsa opened this issue Mar 20, 2017 · 0 comments
Closed

Documentation improvement: JAXB/Jackson vs JAXB/JSON #554

behrangsa opened this issue Mar 20, 2017 · 0 comments

Comments

@behrangsa
Copy link

Hi,

In the docs, there's a section (emphasis mine):

JAXB / JSON integration

As representations for REST web services are usually rendered in either XML or JSON the natural choice of technology to achieve this is either JAXB, JSON or both in combination. To follow HATEOAS principles you need to incorporate links into those representation. Spring HATEOAS provides a set of useful types to ease working with those.

However, JAXB is an API while JSON is a data interchange format. I think this section should be changed to something like this:

JAXB/Jackson integration

As representations for REST web services are usually rendered in either XML or JSON the natural choice of technology to achieve this is either JAXB, Jackson or both in combination. To follow HATEOAS principles you need to incorporate links into those representation. Spring HATEOAS provides a set of useful types to ease working with those.

gregturn added a commit to gregturn/spring-hateoas that referenced this issue Mar 20, 2017
gregturn added a commit to gregturn/spring-hateoas that referenced this issue Mar 20, 2017
odrotbohm pushed a commit that referenced this issue Mar 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants