Hello,
I sent this problem about two weeks ago. In the meantime I solved the
problem myself. So, if anybody has the same or a similar problem, the
solution is to use xmlbeans for databinding. The default adb databinding
seems to have the problem of not decoding the complete base64binary
element from the SOAP response.
regards,
Ingo
Ingo Soetebier schrieb:
Hello,
I've got the following problem: There is a server application,
implemented in C++ using gSOAP, which provides a service that sends
bitmaps as base64binary elements in the SOAP messages. There are other
services provides by this server using standard data types like int,
strings etc. For the client side I created succesfully java classes
from the WSDL-file describing the services, using axis2 1.4. All
services are working fine, except the one sending the bitmaps. I
captured the the SOAP-response and the repsonse was complete and
valid. But "inside axis2" only a part base64binary element was decoded
to a bitmap. I debugged into the classes created by axis2 and it
seems, that only a part of the base64binary element was used for
decoding. The funny thing is, that the size of the decoded data
differs. Sometime it is a bit more, sometime a bit less. Is there some
kind of size-limit for base64binary elements? The client is running as
a eclipse plugin in an RCP application. The server wasn't implemented
by me, so it is some kind of "black box".
regards,
Ingo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
