REST Resource URI Editor allows unsupported mapping of multiple parameters directly to response body

To map multiple ABL output parameters to a REST response body, it is necessary to map each output to a separate node in the response body. However, the REST Resource URI Editor allows dragging multiple interface parameters directly to the body. If this is done, the mapping.xml shows all the mapping rules but only the last mapping actually appears in the response.

Jan 6, 2016
Knowledge

Title

URL Name

REST-Resource-URI-Editor-allows-unsupported-mapping-of-multiple-parameters-directly-to-response-body

Article Number

000182586

Environment

Product: OpenEdge Version: 11.2 and later OS: Windows

Question/Problem Description

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Defect PSC00344086

Enhancement Number

Cause

When multiple interface parameters are dragged to the response body (as opposed to separate nodes within the response body) in the REST Resource URI Editor, each mapping processed overrides the previous one. When all mappings are processed, only the last one that was processed remains.

Note that multiple mappings to the response body without defining separate nodes for each is not supported. The defect is the fact that the REST Resource URI Editor allows such mappings to be defined when the results will not actually be returned from the REST service.

Resolution

None at this time.

Workaround

Depending on application needs, do one of the following:

For a routine (interface) with only one output parameter, map the parameter directly to the body (this is supported).
To return more than one interface parameter in the response body, add a separate node for each and map each parameter its node rather than to the body itself.

This will not work:

Multiple parameters mapped to response body WILL NOT work

Do this instead:

Right-click on the Body element of the response and select "Add Node"

"Add Node..." in response Body context menu

3. In the Add Node dialog, keep "Body" as the Type, select the desired interface parameter to map from the Name drop-down list and click OK:

4. Drag a line from the new response node to the corresponding interface parameter to define the mapping:

Response node mapped to interface parameter

Response node mapped to interface parameter

5. Repeat steps 1 - 4 for additional interface parameters.

Notes

Adding nodes to the body as described in the workaround is equivalent to defining body parameters by dragging a line to the "[Drop a parameter here...]" area in the response body.

References to Other Documentation:

Progress Developer Studio for OpenEdge Online Help, Chapter 5, "Introducing OpenEdge REST > Working with the REST Expose Editor"

(Note that the tool labeled "REST Resource URI Editor" in PDS is the same tool referenced as "REST Expose Editor" in the documentation (online help).

Keyword Phrase

Last Modified Date

1/6/2016 11:18 PM

REST Resource URI Editor allows unsupported mapping of multiple parameters directly to response body

Files(0)

Was this article helpful?

Was this article helpful?

REST Resource URI Editor allows unsupported mapping of multiple parameters directly to response body

Information

Related Articles