axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mhuffman <>
Subject Sanity Check
Date Tue, 02 Feb 2010 19:58:53 GMT

I've written a web-service in Axis2/C based on an "Echo" example.  Based on
this this page:

I've got the echo service working with attachments.  However, I ran into a
problem using axutil_base64_decode(); it would only decode the first 50 some
characters of the message. After some trial and error, I figured out it was
having problems with '\r' and '\n' characters in the "char *data"; and after
stripping out all whitespace from the character string, I was able to decode
the attachment completely...

I'm making a few assumptions, (1) the Pear::Soap implementation that I'm
using to test my server is inserting the '\r\n' characters into the mime
attachment, despite the client & server both run in a UNIX environment (I
would imagine this is per the mime spec?); (2) AXIS2/C doesn't contain a
function that I'm missing to strip out the line-endings from the encoded
attachment before passing off to the decoder?

Is this a standard way of going about decoding attachments, or is there a
more AXIS2/C preferred (easier) way? And will/would this work differently
with streaming?

View this message in context:
Sent from the Axis - Dev mailing list archive at

View raw message