OK I understand what you've written. But I don't understand how you plan to return both the JSON and the PDF to the original caller. What is your idea here?
XOP refers to XML binary Optimized Processing, about which you can read here. In short, this standard was defined as part of the SOAP-related specifications, as a way to allow transmission of a SOAP document, which contains a binary image (like a PDF, PNG, ZIP etc) in an optimized manner.
XOP describes how to format a single HTTP message, which contains multiple parts. One part is an XML document, another part is the binary file. The XML document refers to the binary attachment via an agreed-upon mechanism. That's XOP. The benefit of XOP is you no longer need to base64-encode the binary blob directly into the XML document. You can instead insert a reference element into the XML document, which points to the binary attachment. The IBM tech article describes this well here.
There is no analogue, that I know of, that describes how to package JSON and a binary attachment in an HTTP message.
I understand you have said "I want to convert the XML to JSON, and send the JSON and the PDF attachment to the caller." But how? What form do you expect the response message to take? Do you have an idea here?
EDIT: 2021 Jul 12 1407
As a start, I've modified the callout to add a new capability: It processes the XOP Package, base64 encodes the attachment, and embeds that encoded data into the XML document. An example follows.
The input, which is a "XOP Package", looks like this:
--MIME_boundary
Content-Type: application/soap+xml; charset=UTF-8
Content-ID: <rootpart@soapui.org>
<S:Envelope xmlns:S='http://schemas.xmlsoap.org/soap/envelope/'>
<S:Body>
<GenericRequest xmlns='http://www.oracle.com/UCM' webKey='cs'>
<Service IdcService='CHECKIN_UNIVERSAL'>
<Document>
<Field name='dDocType'>Application</Field>
<Field name='dDocTitle'>filename.zip</Field>
<File name='primaryFile' href='5D7541BA-04FD-4FF8'>
<Contents>
<Include
xmlns='http://www.w3.org/2004/08/xop/include' href='cid:0b83cd6b-af15-45d2-bbda-23895de2a73d'/>
</Contents>
</File>
</Document>
</Service>
</GenericRequest>
</S:Body>
</S:Envelope>
--MIME_boundary
Content-Type: application/zip
Content-Transfer-Encoding: binary
Content-ID: <0b83cd6b-af15-45d2-bbda-23895de2a73d>
...binary zip data...
--MIME_boundary--
and the output looks like this:
<S:Envelope xmlns:S='http://schemas.xmlsoap.org/soap/envelope/'>
<S:Body>
<GenericRequest xmlns='http://www.oracle.com/UCM' webKey='cs'>
<Service IdcService='CHECKIN_UNIVERSAL'>
<Document>
<Field name='dDocType'>Application</Field>
<Field name='dDocTitle'>filename.zip</Field>
<File name='primaryFile' href='5D7541BA-04FD-4FF8'>
<Contents>....base64 content here....</Contents>
</File>
</Document>
</Service>
</GenericRequest>
</S:Body>
</S:Envelope>
You could do THAT, then follow it with an XMLToJSON policy to transform a XOP package into a readable JSON message. It would look like this:
{
"Envelope": {
"Body": {
"GenericRequest": {
"webKey": "cs",
"Service": {
"IdcService": "CHECKIN_UNIVERSAL",
"Document": {
"Field": [
{
"name": "dDocType",
"": "Application"
},
{
"name": "dDocTitle",
"": "multipart-handler-master.zip"
}
],
"File": {
"href": "af75b881-f028-4781-8c3e-35c1c2403444",
"name": "primaryFile",
"Contents": "...base64 encoded content here..."
}
}
}
}
}
}
}
If you use this, The caller will need to base64-decode the correct field in the JSON to get the attached file.
LinkedIn
Twitter
