(Unicode C) Extract Files from Binary SOAP MTOM MIME

This example demonstrates how to extract files from a binary SOAP MTOM MIME document.

Chilkat C/C++ Library Downloads
MS Visual C/C++ Linux/CentOS C/C++ Alpine Linux C/C++ MAC OS X C/C++	armhf/aarch64 C/C++ C++ Builder iOS C/C++ Android C/C++	Solaris C/C++ MinGW C/C++

#include <C_CkMimeW.h>
#include <C_CkStringBuilderW.h>

void ChilkatSample(void)
    {
    HCkMimeW mime;
    BOOL success;
    int numParts;
    HCkStringBuilderW sbFilename;
    const wchar_t *name;
    int i;
    HCkMimeW mp;
    int numReplaced;

    // This example requires the Chilkat API to have been previously unlocked.
    // See Global Unlock Sample for sample code.

    mime = CkMimeW_Create();

    // In this example, we have a MIME file containing 8bit (non-encoded) binary data,
    // and it is what I call "headless".  MIME is headless when it omits
    // the top-level header.  The file we have here begins with the first
    // boundary string.

    // The structure the MIME to be loaded is:

    // multipart/mixed (inferred because it is headless)
    //     application/xop+xml
    //     image/jpeg
    //     image/gif
    //     image/gif
    // 

    success = CkMimeW_LoadMimeFile(mime,L"qa_data/mime/headless_binary_soap_mtom_mime.mim");
    if (success != TRUE) {
        wprintf(L"%s\n",CkMimeW_lastErrorText(mime));
        CkMimeW_Dispose(mime);
        return;
    }

    // The MIME file loaded in this example contains this:

    // --uuid:e74486f4-52b0-44b6-b829-156810fae20d
    // Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml"
    // Content-Transfer-Encoding: binary
    // Content-ID: <root.message@cxf.apache.org>
    // 
    // <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body> ... </soap:Body></soap:Envelope>
    // --uuid:e74486f4-52b0-44b6-b829-156810fae20d
    // Content-Type: image/jpeg
    // Content-Transfer-Encoding: binary
    // Content-ID: <beee83b7-166c-494c-890a-def990e9887b-1496@cxf.apache.org>
    // Content-Disposition: attachment;name="-2049913191"
    // 
    // BINARY DATA HERE...
    // 
    // --uuid:e74486f4-52b0-44b6-b829-156810fae20d
    // Content-Type: image/gif
    // Content-Transfer-Encoding: binary
    // Content-ID: <beee83b7-166c-494c-890a-def990e9887b-1497@cxf.apache.org>
    // Content-Disposition: attachment;name="-2049913188"
    // 
    // BINARY DATA HERE...
    // 
    // --uuid:e74486f4-52b0-44b6-b829-156810fae20d
    // Content-Type: image/gif
    // Content-Transfer-Encoding: binary
    // Content-ID: <beee83b7-166c-494c-890a-def990e9887b-1498@cxf.apache.org>
    // Content-Disposition: attachment;name="-2049913185"
    // 
    // BINARY DATA HERE...
    // 
    // --uuid:e74486f4-52b0-44b6-b829-156810fae20d--

    // Get the number of MIME sub-parts.
    numParts = CkMimeW_getNumParts(mime);

    // The 1st part at index 0 is the application/xop+xml.  We're just going to extract the JPG and GIF image files..
    sbFilename = CkStringBuilderW_Create();

    i = 1;
    while (i < numParts) {
        mp = CkMimeW_GetPart(mime,i);

        // By looking at the MIME above, the "name" attribute of the Content-Disposition header field seems
        // to be the only possible name we can use for each image..
        CkStringBuilderW_Append(sbFilename,L"qa_output/");
        name = CkMimeW_getHeaderFieldAttribute(mp,L"Content-Disposition",L"name");
        CkStringBuilderW_Append(sbFilename,name);
        CkStringBuilderW_Append(sbFilename,L".");
        CkStringBuilderW_Append(sbFilename,CkMimeW_contentType(mp));
        numReplaced = CkStringBuilderW_Replace(sbFilename,L"image/",L"");
        CkMimeW_SaveBody(mp,CkStringBuilderW_getAsString(sbFilename));
        wprintf(L"output file: %s\n",CkStringBuilderW_getAsString(sbFilename));

        CkMimeW_Dispose(mp);
        CkStringBuilderW_Clear(sbFilename);
        i = i + 1;
    }

    wprintf(L"Success.\n");


    CkMimeW_Dispose(mime);
    CkStringBuilderW_Dispose(sbFilename);

    }