Try OpenEdge Now
skip to main content
Web Services
Creating OpenEdge SOAP Web Services : Building Clients for OpenEdge SOAP Web services : Mapping relational data : Defining DATASET (static ProDataSet) parameters
Defining DATASET (static ProDataSet) parameters
DATASET parameters pass only the data, because the static ProDataSet's schema is known at WSDL generation. In the WSDL, OpenEdge Web services map a DATASET definition to a <complexType> consisting of a <sequence> of elements that represent the ProDataSet's temp-tables. Each temp-table element includes a <complexType> describing the temp-table's fields. The definition also includes elements describing the data relations and indexes.
For all SOAP formats, client interfaces typically represent dataset parameters as follows:
*For every dataset, each temp-table is represented by an object.
*Every dataset parameter is represented as arrays of the constituent temp-table objects.
*For an ABL client, the WSDL Analyzer transforms the WSDL definition of a ProDataSet parameter into a matching ProDataSet.
By default, a ProDataSet parameter includes only the current data. You must specify in ProxyGen the ProDataSet parameters for which you want to include before-image data. If the ProDataSet parameter includes before-image data, the before-image data is serialized in a proprietary OpenEdge datasetChanges document.
The following snippet shows the general format for DATASET parameters in SOAP messages:

DATASET parameters—general SOAP format

    <Buffer1Name> <!--- TEMP-TABLE-1 row instance 1 --> </Buffer1Name>
    <Buffer1Name> <!--- TEMP-TABLE-1 row instance 2 --> </Buffer1Name>    
<Buffer2Name> <!--- TEMP-TABLE-2 row instance 1 --> </Buffer2Name>

    <Buffer2Name> <!--- TEMP-TABLE-2 row instance 2 --> </Buffer2Name>