Completely control SOAP XML Request Body Swagger EPCIS GS1
0
Hey there, When developing a published web service, I found out that Mendix pre-populates a number of attributes in the soap request and response. For example, when adding a single text attribute, the SOAP request looks like this: <soap:Envelope xmlns:tns="http://www.example.com/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <soap:Header/> <soap:Body> <tns:MRO_Add> <SingleAttribute>exampleString</SingleAttribute> </tns:MRO_Add> </soap:Body> </soap:Envelope> For a client I am investigating whether it is possible to completely control the SOAP request body, so as to be able to conform to a standard (EPCIS) defined by GS1. This standard defines that the request body should look like this: <?xml version="1.0" encoding="UTF-8"?> <!--Sample XML file generated by XMLSpy v2021 (x64) (http://www.altova.com)--> <epcis:EPCISDocument xmlns:cbvmda="urn:epcglobal:cbv:mda" xmlns:rail="https://gs1.org/cbv/rail" xmlns:epcis="urn:epcglobal:epcis:xsd:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:n1="http://www.altova.com/samplexml/other-namespace" xmlns:sbdh="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader" schemaVersion="0" creationDate="2001-12-17T09:30:47Z" xsi:schemaLocation="urn:epcglobal:epcis:xsd:1 EPCglobal-epcis-1_2-railMRO-noext.xsd"> <EPCISBody> <EventList> <ObjectEvent> <eventTime>2001-12-17T09:30:47Z</eventTime> <eventTimeZoneOffset>+01:00</eventTimeZoneOffset> <epcList> <epc>urn:epc:id:giai:1234567.7911bg</epc> </epcList> <action>ADD</action> <bizStep>urn:epcglobal:cbv:bizstep:commissioning</bizStep> <disposition>urn:epcglobal:cbv:disp:active</disposition> <readPoint> <id>geo:41.6725,-86.255278</id> </readPoint> <extension> <ilmd> <rail:additionalTradeItemID tradeItemIDTypeCode="BUYER_ASSIGNED">(SAPEAM)11804102</rail:additionalTradeItemID> </ilmd> </extension> </ObjectEvent> </EventList> </EPCISBody> </epcis:EPCISDocument> Question: is there a way to get rid of/adapt the standard SOAP request body so we can conform to the standard? Thanks for thinking along! Best regards, Wouter