JAX-RS RESTful services considerations and limitations

Following is a list of considerations and limitations when using HATS support for JAX-RS RESTful Web services:

• HATS runtime support for RESTful Web services requires the respective runtime/server included in the JAX-RS support and no additional feature packs are necessary. For more details, see "System Requirements for Host Access Transformation Services" at https://www.ibm.com/support/pages/node/320035.
• HATS supports both JAX-RS 1.X and JAX-RS 2.X, however the version is decided depending on the runtime selected by user for the HATS project to be deployed. For example, WebSphere Application server V8 and V8.5 includes JAX-RS 1.X and WebSphere Application server V9 by default includes JAX-RS 2.X.
• HATS JAX-RS RESTful services are not compatible with Portal.
• By default, HATS provides IoJsonProvider to de-serialize JSON input, however to create your own customized JSON provider or any other providers, you must follow the JAX-RS specification. For more details, see the "JAX-RS: Java™ API for RESTful Web Services" versions 1.1 and 2.0 at http://download.oracle.com/otn-pub/jcp/jaxrs-1.1-mrel-eval-oth-JSpec/jax_rs-1_1-mrel-spec.pdf and http://download.oracle.com/otn-pub/jcp/jaxrs-2_0-fr-eval-spec/jsr339-jaxrs-2.0-final-spec.pdf.
• To create customized providers, you must follow the JAX-RS specification, see https://jcp.org/aboutJava/communityprocess/final/jsr311/index.html, and refer to the Apache Wink implementation, seehttp://wink.apache.org/.