Hi. I am using OpeneEdge 10.1c to build a web service which will expose elements of an already well established ERP for use with a SOAP client.
Its been a struggle If I am honest but I managed to get a proof of concept developed before Christmas which involved the following
1. Create a SalesOrder.p. This accepts a DATASET as an input parameter which is made up of a number of linked TEMP-TABLES.
2. Ran Proxygen
3. Deployed webservice in LINUX environment
This all seems to work and the generated WSDL accurately shows how to build the XML to access the webservice based upon the DATASET input parameter.
All Good.
However the client wants the Web Service to be flexible. i.e. he cant guarantee that the users accessing the web service will be able to use the format of XML described by the web service and would like it to be flexible enough to accept the XML the client can provide, which the web service then translates into the standard, possibly using xsltproc.
My first thought here is to create a variation of SalesOrder.p which accepts one LONGCHAR input parameter; load the supplied XML into memory and then push it through xsltproc.
Is this the best way to do it (probably not!) and is it possible to do something like this and still provide a useful WSDL??
Hope all that makes sense - Very new to this side of things so forgive me if my question is nonsensical!
Its been a struggle If I am honest but I managed to get a proof of concept developed before Christmas which involved the following
1. Create a SalesOrder.p. This accepts a DATASET as an input parameter which is made up of a number of linked TEMP-TABLES.
2. Ran Proxygen
3. Deployed webservice in LINUX environment
This all seems to work and the generated WSDL accurately shows how to build the XML to access the webservice based upon the DATASET input parameter.
All Good.
However the client wants the Web Service to be flexible. i.e. he cant guarantee that the users accessing the web service will be able to use the format of XML described by the web service and would like it to be flexible enough to accept the XML the client can provide, which the web service then translates into the standard, possibly using xsltproc.
My first thought here is to create a variation of SalesOrder.p which accepts one LONGCHAR input parameter; load the supplied XML into memory and then push it through xsltproc.
Is this the best way to do it (probably not!) and is it possible to do something like this and still provide a useful WSDL??
Hope all that makes sense - Very new to this side of things so forgive me if my question is nonsensical!