Arby
2009-02-19 19:54:43 UTC
Hello, I have been digging through the mailing list archives to find an
answer to my problem but I finally decided to send off an email instead. I
am using a JSR181 Web Service to transfer files between the Java service and
a C++ client. At first, I was encoding all the messages in a Base64 String
to achieve interoperability but this approach does not work for transferring
large files because the entire file needs to be read into buffer before
being encoded, which could cause OutOfMemory Exceptions. As a result, I
switched over to using MTOM to transfer files. This works wonderfully if I
am using a Java client because the web service simply results a DataHandler
to my attachment file. But I am unable to read the response in my C++
client. Is there any way to convert the DataHandler to a Base64 string or a
byte array so that I can read the response in a C++ client? Is anyone
familiar of any interoperability issues between XFire and gSOAP when it
comes to using MTOM? Any help would be appreciated.
Thanks.
answer to my problem but I finally decided to send off an email instead. I
am using a JSR181 Web Service to transfer files between the Java service and
a C++ client. At first, I was encoding all the messages in a Base64 String
to achieve interoperability but this approach does not work for transferring
large files because the entire file needs to be read into buffer before
being encoded, which could cause OutOfMemory Exceptions. As a result, I
switched over to using MTOM to transfer files. This works wonderfully if I
am using a Java client because the web service simply results a DataHandler
to my attachment file. But I am unable to read the response in my C++
client. Is there any way to convert the DataHandler to a Base64 string or a
byte array so that I can read the response in a C++ client? Is anyone
familiar of any interoperability issues between XFire and gSOAP when it
comes to using MTOM? Any help would be appreciated.
Thanks.