Forum Discussion
May 05, 2011
Actually, the methods that use parameters with char[] data types will result in a SOAP type of base64Binary. Looking at a soap trace on the download_file method, the resulting data looks something like this:
< E:Envelope
xmlns:E="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:A="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:s="http://www.w3.org/2001/XMLSchema-instance"
xmlns:y="http://www.w3.org/2001/XMLSchema"
xmlns:iControl="urn:iControl"
E:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" >
< E:Body >
< m:download_fileResponse xmlns:m="urn:iControl:System/ConfigSync" >
< return s:type="iControl:System.ConfigSync.FileTransferContext" >
< file_data s:type="y:base64Binary" >YXV0aCBwYXJ0aXRpb24gQ29tbW9uIHsKICAgIGRlc2N...."< /file_data >
< chain_type s:type="iControl:Common.FileChainType" >FILE_FIRST_AND_LAST< /chain_type >
< /return >
< file_offset s:type="y:long" >7656< /file_offset >
< /m:download_fileResponse >
< /E:Body >
< /E:Envelope >
SOAP::Lite sees the "base64Binary" type and knows to decode it. Maybe I'm missing something...
-Joe