We are so much used to building Oracle JET applications with ADF BC REST services. It is true that JET is developed quickest if you use an Oracle standard REST service (such as ADF BC). But it is also true that JET’s common model architecture does support REST end-points which do not conform to Oracle standards.
Let’s see an example. An Oracle standard REST sends response in the following format: With these information available in the response, we assume that JET will take care of parsing the data and show a paginated table. This is true. If data, even if from a non-Oracle REST, is presented to JET in this format, we do not have to write any extra code to display the same on the UI. But what if the data comes in this format (and that too from a POST request): Read the complete article here.
For regular information become a member in the Developer Partner Community please register here.