Hi, we don't use java on the client side, we use gSOAP (C++). The
issue with having the server accept a DataHandler is that there is, as
far as I can tell, no defined mapping from a DataHandler to any
combination of C++ or C# types. If you define a WSDL file using
this type, no non-java toolkit
Yes, Base64 encoding increases the size of the binary data by 33% over the
pure binary encoding that axis will use for multipart or DataHandler encoding.
It's a tradeoff -- use Base64 and interoperate with all SOAP clients (but
increase server coding effort and message size), use DIME and intero
If you care about interoperability with clients like gSOAP (c++) or MS .NET
your best bet is to not use DataHandlers, DIME, or multipart. For any kind
of binary data / BLOB use old reliable base64Binary objects
We had the fun of interfacing to an axis server that exported image files
as DataHa
Hi,
I'm trying to connect a C++ client to (someone else's) Axis server to
retrieve a file object. The server wsdl for the service uses the
DataHandler datatype from the http://xml.apache.org/xml-soap namespace but
I have not been able to find an XSD or WSDL for the apache datatypes
anywhere a
