I'm trying to create a simple web service to handle attachments between a
Perl SOAP:LITE implementation and Axis (latest version).
I managed to send attachment to the Perl web service, but I have the
following problem when I invoke
a method on the Perl webservice that returns a Base64 attachment.
The tcp monitor shows that the PERL webservice reply to my java client
correctly
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:xsd="http://www.w3.org/1999/XMLSchema";
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";><SOAP-ENV:Body><n
amesp3:getAttachmentsResponse
xmlns:namesp3="SOAP_MIME_Test"/></SOAP-ENV:Body></SOAP-ENV:Envelope>
------------=_1066846133-13334-5
Content-Type: application/pdf; name="spic3.pdf"
Content-Disposition: attachment; filename="spic3.pdf"
Content-Transfer-Encoding: base64
Content-Id: <1234>
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)
JVBERi0xLjEKJeLjz9MNCjIgMCBvYmoKPDwKL0xlbmd0aCAyMjA4Ci9GaWx0 ZXIgL0xaV0RlY29kZQo+PgpzdHJlYW0NCoAMBBAoEUiOChkICVAxAaoGLhkN
I am wondering how this can work - without a reference from SOAP to the mime part? (I admit I never tried it that way.)
This is what I am doing (also with SOAP::Lite): my base64 encoded data is contained within the soap body like:
<content xsi:type="xsd:base64Binary"> ... </content>
Works just fine for me.
HTH, Eddie
