M
mjacobs
Guest
As Mike said, the REST adapter can map [almost] anything in a HTTP message/response to a procedure/class method parameter list. Some restrictions apply... I'll supply some background information that may be useful to you before getting started. The process for generating a pure REST API to an AppServer is similar in nature to what happens with a Mobile project. The Mobile tooling simply enforces a bunch of static mapping rules (like not being able to configure your own parameters) to make REST transparent and simple, just like it is suppose to do. When you create your own REST API the PDSOE tooling cannot make any assumptions regarding any of the mapping. You, the developer, are in 100% control of very aspect of the mapping and therefore have to manually configure it all. Some of the penalty for any-to-any mapping ability I guess. As Mike also said, you lose the value gained by using the JSDO in your clients. Your client will then be expected to manually generate the correct HTTP requests and handle the HTTP responses. In the 11.2/11.3 OpenEdge Development: Web Services you will find information about REST applications, annotating your ABL code, parameter mapping to HTTP request/response, and JSON structuring. It is worth reviewing that before diving straight into the PDSOE project. You can start with your Mobile project and add REST 'service interfaces' and use PDSOE's mapping tool. I often do this so that one web application deployment can be used for both types of clients. You do not have to start a new project just to add REST support. That decision is yours. Hope this helps.
Continue reading...
Continue reading...