[ http://issues.apache.org/jira/browse/AXIS2-1379?page=comments#action_12442767 ] Thilina Gunarathne commented on AXIS2-1379: -------------------------------------------
Hi Jake, It should be in the SNAPSHOT you have tried.. But to be in the safe side please try with a bit later snapshot too... if the issue persists please reopen this issue.. I'm having trouble recreating this.. Axiom to Axiom everything works fine, even without this change... What is the data binding mechanism you are using... thanks, ~Thilina > Base64 data is not encoded correctly > ------------------------------------ > > Key: AXIS2-1379 > URL: http://issues.apache.org/jira/browse/AXIS2-1379 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: databinding > Affects Versions: 1.1 > Reporter: Jake Goulding > Assigned To: Thilina Gunarathne > Attachments: attachment.txt > > > I have a web service call that specifies the following field: > <s:element minOccurs="0" maxOccurs="1" name="attachment" > type="s:base64Binary" /> > The Java generated for this takes in a DataHandler, which is set like such: > param.setAttachment(new DataHandler(new FileDataSource(file))); > However, the webservice responds with an error: > org.apache.axis2.AxisFault: Server was unable to read request. --> There is > an error in XML document (1, 394). --> > '==L3ZpdmlzaW1vLWdvdWxkaW5nMi9saWIvamF2YS9jb252ZXJ0ZXJzLmphcjovdXNyL2xvY2FsL3ZpdmlzaW1vLWdvdWxkaW5nMi9saWIvamF2YS9uY2Fjbl9ucC5qYXI6L3Vzci9sb2NhbC92aXZpc2ltby1nb3VsZGluZzIvbGliL2phdmEvWG1sU2NoZW1hLVNOQVBTSE9ULmphcjovdXNyL2xvY2FsL3ZpdmlzaW1vLWdvdWxkaW5nMi9saWIvamF2YS9qYWthcnRhLWh0dHBjb3JlLTQuMC1hbHBoYTIuamFyOi91c3IvbG9jYWwvdml2aXNpbW8tZ291bGRpbmcyL2xpYi9qYXZhL2pjaWZzLmphcjovdXNyL2xvY2FsL3ZpdmlzaW1vLWdvdWxkaW5nMi9saWIvamF2YS9kYjJqY2NfbGljZW5zZV9jdS5qYXI6L3Vzci9sb2NhbC92aXZpc2ltby1nb3VsZGluZzIvbGliL2phdmEvYWN0aXZhdGlvbi5qYXI6L3Vzci9sb2NhbC92aXZpc2ltby1nb3VsZGluZzIvbGliL2phdmEvY29tbW9ucy1jb2RlYy0xLjMuamFyOi91c3IvbG9jYWwvdml2aXNpbW8tZ291bGRpbmcyL2xpYi9qYXZhL2Rzbi5qYXI6L3Vzci9sb2NhbC92aXZpc2ltby1nb3VsZGluZzIvbGliL2phdmEvcG9wMy5qYXI6L3Vzci9sb2NhbC92aXZpc2ltby1nb3VsZGluZzIvbGliL2phdmEvc3RheC1hcGktMS4wLjEuamFyOi91c3IvbG9jYWwvdml2aXNpbW8tZ291bGRpbmcyL2xpYi9qYXZhL2Fubm9nZW4tMC4xLjAuamFyOi91c3IvbG9jYWwvdml2aXNpbW8tZ291bGRpbmcyL2xpYi9qYXZhL3Bvc3RncmVzcWwtOC4wLTMxMi5qZGJjMy5qYXI6L3Vzci9sb2NhbC92aXZpc2ltby1nb3VsZGluZzIvbGliL2phdmEvY29tbW9ucy1maWxldXBsb2FkLTEuMS4xLmphcjovdXNyL2xvY2FsL3ZpdmlzaW1vLWdvdWxkaW5nMi9saWIvamF2YS9udGxtLXNlY3VyaXR5LmphcjovdXNyL2xvY2FsL3ZpdmlzaW1vLWdvdWxkaW5nMi9saWIvamF2YS9heGlzMi1rZXJuZWwtMS4xLVNOQVBTSE9ULmphcjovdXNyL2xvY2FsL3ZpdmlzaW1vLWdvdWxkaW5nMi9saWIvamF2YS9tYWlsYXBpLmphcjovdXNyL2xvY2FsL3ZpdmlzaW1vLWdvdWxkaW5nMi9saWIvamF2YS93c3R4LWFzbA==LTMuMC4xLmphcjovdXNyL2xvY2FsL3ZpdmlzaW1vLWdvdWxkaW5nMi9saWIvamF2YS9teXNxbC1jb25uZWN0b3ItamF2YS0zLjEuMTAtYmluLmphcjovdXNyL2xvY2FsL3ZpdmlzaW1vLWdvdWxkaW5nMi9saWIvamF2YS9tYWlsLmphcjovdXNyL2xvY2FsL3ZpdmlzaW1vLWdvdWxkaW5nMi9saWIvamF2YS9jb21tb25zLWh0dHBjbGllbnQtMy4wLjEuamFyOi91c3IvbG9jYWwvdml2aXNpbW8tZ291bGRpbmcyL2xpYi9qYXZhL2F4aW9tLWltcGwtU05BUFNIT1QuamFyOi91c3IvbG9jYWwvdml2aXNpbW8tZ291bGRpbmcyL2xpYi9qYXZhL25lZXRoaS1TTkFQU0hPVC5qYXI6L3Vzci9sb2NhbC92aXZpc2ltby1nb3VsZGluZzIvbGliL2phdmEvc2hhcmVwb2ludC5qYXI6L3Vzci9sb2NhbC92aXZpc2ltby1nb3VsZGluZzIvbGliL2phdmEvd29kZW4tMS4wLjBNNi5qYXI6L3Vzci9sb2NhbC92aXZpc2ltby1nb3VsZGluZzIvbGliL2phdmEvYmFja3BvcnQtdXRpbC1jb25jdXJyZW50LTIuMi5qYXI6L3Vzci9sb2NhbC92aXZpc2ltby1nb3VsZGluZzIvbGliL2phdmEvanRkcy0xLjEuamFyOi91c3IvbG9jYWwvdml2aXNpbW8tZ291bGRpbmcyL2xpYi9qYXZhL2phcmFwYWMuamFyJyAtWG14MTYwbSAtWFg6K0Rpc3BsYXlWTU91dHB1dFRvU3RkZXJyIC1YWDorSGVhcER1bXBPbk91dE9mTWVtb3J5RXJyb3IgLURqYXZhLmlvLnRtcGRpcj0vdXNyL2xvY2FsL3Zpdmlz' > is not a valid Base64 text sequence. Line 1, position 1775 > If I look at the SOAP envelope, it looks like chunks of 1024 source bytes are > encoded separately. This leads to extraneous '=' in the middle of my Base64 > data. If I split the data on these delimiters and decode each chunk and cat > them all together, it appears to have all the data. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
