The Oracle Commerce Platform REST framework supports the JAX-RS standard with Jersey as the underlying implementation.
The Jersey configuration defines the components of the JAX-RS application, such as resource classes and components, filters, and additional metadata.
Whereas, The REST MVC framework leverages existing droplets, form handlers and components, creating an API that can be extended easily. You can build REST services in a modular format by combining model producers. URLs are explicitly defined in a registry, making access to REST URLs secure. Using access controllers defined in your applications, you can restrict who or under what conditions REST URLs can be accessed. All properties that are used in REST calls can be filtered, which reduces the amount of information that must be transferred.
Architectural Framework described in the below links
Some key capabilities of the JAX-RS framework are:
-Annotation-based resource development
-XML-based filtering and validation schema support, which is easily configured and extensible with configuration layering
-The ability to control the fields and links in the response and request representation of a resource
-User authentication using OAuth
Please mark any update as "Correct Answer" or "Helpful Answer" if that update helps/answers your question, so that others can identify the Correct/helpful update between many updates.
Thanks for the explanation.
In case of customized OOTB droplets/form handlers, how jax-rs implementation can be done as it would only invoke the OOTB components provided by JAX RS in ATG 11.3.
Any example would be helpful.
Wanted to know how to customise the request/response of OOTB JAX-RS components. Whether we need to override getRepresentationModelBuilder or is there some other approach..?