Hi John,
Section 4.2.4 lists the types that all JAX-RS implementations must handle out of the box. It also points to section 11.2.6-7 referring to JSON-P and JSON-B, but that section does seem to imply that these providers are only required if the implementation provides those APIs.
So my opinion would be that all JAX-RS client implementations must handle the basic set of return types / media types, but the JSON support is optional - and thus non-portable. That said, I think most of the major vendors support JSON-P/B, so the portability shouldn’t be too much of an issue.
Hope this helps,
Andy
Hi All,
I'm wondering, if anyone can give me some opinions.
When using JAX-RS Client API, there is no requirement for any providers to be registered by default when you invoke ClientBuilder.newClient() right? e.g. its non-portable, platform specific if a JSON-B, JSON-P provider is registered right?
John
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
