Hi,
1. Exporting REST service in PDSOE there are 2 options: export WAR or zip incrementially? Is it any guideline which one use in what case?
2. In WAR (ZIP) file there are no source files (.cls, .i). What to do to deploy the service on the other machine?
I'd appreciate your help...
Hi Navneet,
Thank you for comprehensive and fast explanation!
Kind regards,
Marek
Hi Peter. I am using 11.6.3. Does it mean in earlier versions WAR contained .r codes?
Hi Sanjeev,
Thanks a lot for your explanation. I have one more question regarding naming convention.
In case I am using PAS OE the folder must be “<prj>/AppServer”? In demo:
www.progress.com/.../making-a-progress-openedge-application-available-as-a-rest-service
the folder is “<prj>src/AppServer”.
Kind regards,
Marek
Thanks again!
Let me ask another question if you are so kind.
If I want to expose ABL resources as REST service I must do that from ABL Web App project type or I can create OpenEdge project then add AppService folder, place classes there and do the rest (annotations, mapping etc)?
Marek
Yes, Peter but when I create OpenEdge project the AppServer folder is not created automatically, right?
It is created for ABL Web App, Dat Object, AppServer, REST project types...
So, if I have OpenEdge Project of type: OpenEdge with ABL class and then I want to expose that class as REST service - can I just add AppServer folder and do the rest: annotations, mapping etc...
- By adding a Business Entity
- By adding Data Object Annotations
- By adding required facets manually from Project Properties (Required facets: ABL AppServer, ABL Data Object Service, ABL REST Service, ABL WebApp, OpenEdge , Progress Adapters)
Thanks Sanjeev. Such information is missing in the the demo, I mentioned above.
(www.progress.com/.../making-a-progress-openedge-application-available-as-a-rest-service#sthash.AxHb5PKv.dpuf).
In this demo it seems it is enough to expose the service by Define Service Interface for particular class file.
Thanks again,
Marek