M
mjacobs
Guest
Maybe some technical background will help you choose the right path. You could build the REST service's .war file easy enough with ANT, using the sources located in $DLC/rest/lib and $DLC/rest/server directories. However, that would be missing the REST service's description file(s) (.paar) that contains all of the Service Interface's definition for HTTP message parts, datatypes, defaults, and AppServer procedure/parameter mapping. Without theREST service description file, the .war file you generated with ANT will not function. The generation of a REST service description file requires creating 4 (complex) .xml files with all of the interface definition information. That is the role that only PDS can play - which is to generate the REST service description file(s) from the .p/.cls sources (with their annotations) and PDS's REST mapper tool. Not something anyone could do in any reasonable amount of time manually, but PDS does in a matter of milliseconds. For automated build processes, release 11.3 introduced the 'restgen.bat' command line utility that allows you to generate the .war or REST service description file from a PDS REST project. But I think that utility does not solve what you want to do because it still requires you to develop using PDS. In the final analysis, you will require PDS to create and deploy REST or Mobile services to access an AppServer. I hope this information helps.
Continue reading...
Continue reading...