Generate PUT also to PATCH

[nilskasseckert]

Hello,
I have an old SEGW service. This has entities / sets which have the attribute “acutalizable”. Now, unfortunately, only a PATCH request is generated from it.
However, only a PUT (i.e. update) is implemented in the service. The GET single, which is needed for a PATCH, does not exist in the service.
Furthermore, you have to enter the ID in the body of the PUT, which the PATCH request does not allow.
Is there a way to generate PUT in addition to PATCH? A classic ODATA API supports both.

We use the Java version of the transformation.

Regards,
Nils

[HeikoTheissen]

Do you mean "generate PUT instead of PATCH"? Because you say that the service does not implement PATCH.

[nilskasseckert]

Hi @HeikoTheissen,
The problem is that in an old SEGW you can't say: PATCH or PUT. You only have a “Updateable” tick in the SEGW. Therefore PATCH and PUT should always be generated.

PUT, however, with the ID of the entity.

[ralfhandl]

You can choose which verb to use with this XSLT parameter:

odata-openapi/tools/V4-CSDL-to-OpenAPI.xsl

Line 51 in 3bfbe7e

<xsl:param name="update-verb" select="'patch'" />

Note: requiring the ID in the PUT request body is not specification-compliant. If the implementation used by you deviates from the OData specification, corresponding changes to the OpenAPI generator have to be made in a fork of this repository. This repository is vendor-neutral.

[paetzeltaov]

@ralfhandl i have similar problem like the author.
I don't understand where to use your example XSLT Parameter.

I got a SAP System where i get the metadata.xml from. Then i do a conversion to openapi with odata-openapi3
https://www.npmjs.com/package/odata-openapi

All update commands from the metadata are as "PATCH" in the openapi spec. But Patch is not implemented :( it should be PUT.

[ralfhandl]

@paetzeltaov For OData services implemented in ABAP, especially OData V2 services, the XSLT-based tools are a better match.