I recently attended the Kendo UI Builder 2.0 webinar (many thanks for this). It was mentioned that there is limited read ODATA support. Is this supported in OpenEdge via a new version of the JSDO?
What are the plans for extending ODATA to CRUD, etc?
We are looking at building a standard REST API to expose our application and REST seems to be more a series of guidelines and good practice rather than a fixed standard, eg. filtering, paging, etc.
Any thoughts appreciated.
Thanks for mentioning ODATA, I've not really looked into it previoiusly and it's worth a look as we are in the same position in respect of being ready to start building a REST API on top of our ERP solution.
I've been more focused at looking at RAML and Swagger as potential products to be used for documenting any API, so would be interested in knowing if Progress are going to be doing anyhting in this area?
Can see two possible directions of integration;
1 - Can a Openedge REST API (e.g. Webspeed web handler) be parsed and the maching Swagger or RAML generated ?
2 - Can we parse a Swagger or RAML definition and generate a Openedge handler stub, including matching prodataset definition etc. ?
I'd also be interested in knowing if you are going to be using Openedge REST or Openedge Webspeed handlers for implementing your API's? The latter Webspeed route seems to be much lighter config wise with no downsides ?
We are using WebHandlers so that we can use all the REST verbs such as Patch. Only downside is it will take us longer to generate generic coding as a Class than using procedural.
|
It takes longer as I have not used Eclipse much or OO much so I have a learning curve. It took me 3 hours this morning to get the environment setup in the first place. I am not saying OO is slower in general but it is when you have to get up to speed.
Thanks Peter.
I know that Mike Fechner / SmartComponents has been working on a Swagger / Business Entity integration which I will be looking into shortly. The ideal from my point of view would be Swagger generates the webhandlers and then roundtips changes to the webhandlers and any annotations.
For a public API a self-generating document is very appealing, with the ability to run sample requests and use codegen then to generate the client side to consume the endpoints.
[mention:b4bd74b70d11452599ed9355a1d5195e:e9ed411860ed4f2ba0265705b8793d05] and [mention:4540e31b6b80426ab2d3d7441b7899aa:e9ed411860ed4f2ba0265705b8793d05] - Here is the post (code included) which perhaps solves your purpose -> community.progress.com/.../3389
isn’t that something Martyn was working on, or that’s more tailored to the SF extensions?
Martyn's work was primarily targeted for the SmartComponent Library back end. But can with some changes be applied to PSC's in the box Business Entities as well.
All clear now, just to avoid confusion though… openapi (oas) formerly known as swagger specs it not the same thing as odata, I do feel the odata model based approach makes more sense in 4gl business entities world than the services (api) approach in swagger ;)
