Re: Outgoing SwA binary attachments: All 0xFF bytes are missing
Hi, We have not come across such an issue before..Can you describe youtr service implementation more.. Are you using a byte[] data source?.. What Axis2 does is just write the entire byte stream we get from data handler (==data source) to the output stream in the correct location(inside MIME boudaries). It would be really great if you can provide a test case for this so that we can see whether it's bug in Axis2. thanks, Thilina On Mon, Jul 28, 2008 at 7:41 AM, Nicolas Verbeke [EMAIL PROTECTED] wrote: Hello I have a web service that sends binary data as MIME attachments (SwA). I realized that the data received by the client was not exactly the same as the data given to the web service. More precisely, a dozen bytes are missing (out of 12,004). All the missing bytes should have had the value 0xFF (255) -- and all the 0xFF bytes from the original data are missing. The original data represents an array of 3001 float values. I'm suspecting a charset-related problem... Does anyone have any clue about what happens? Thanks a lot in advance. Hereafter: What was received by the client HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835; type=text/xml; start=0.urn:uuid:[EMAIL PROTECTED][EMAIL PROTECTED] Transfer-Encoding: chunked Date: Mon, 28 Jul 2008 13:48:15 GMT 243 --MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835 Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: 0.urn:uuid:[EMAIL PROTECTED][EMAIL PROTECTED] ?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ soapenv:Bodytns:getLcValuesResponse xmlns:tns=http://www.myplace.com/MyWebService/xsd tns:columntns:values tns:href=urn:uuid:DF83F3FB6FDDA694771217252894381 tns:count=3001 //tns:column/tns:getLcValuesResponse/soapenv:Body/soapenv:Envelope 38 --MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835 2000 Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-ID: urn:uuid:DF83F3FB6FDDA694771217252894381 (... Binary data with missing bytes ...) 38 --MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835 2 -- 0 Connection #0 to host localhost left intact -- View this message in context: http://www.nabble.com/Outgoing-SwA-binary-attachments%3A-All-0xFF-bytes-are-missing-tp18689243p18689243.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thilina Gunarathne - http://thilinag.blogspot.com
Outgoing SwA binary attachments: All 0xFF bytes are missing
Hello I have a web service that sends binary data as MIME attachments (SwA). I realized that the data received by the client was not exactly the same as the data given to the web service. More precisely, a dozen bytes are missing (out of 12,004). All the missing bytes should have had the value 0xFF (255) -- and all the 0xFF bytes from the original data are missing. The original data represents an array of 3001 float values. I'm suspecting a charset-related problem... Does anyone have any clue about what happens? Thanks a lot in advance. Hereafter: What was received by the client HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835; type=text/xml; start=0.urn:uuid:[EMAIL PROTECTED] Transfer-Encoding: chunked Date: Mon, 28 Jul 2008 13:48:15 GMT 243 --MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835 Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: 0.urn:uuid:[EMAIL PROTECTED] ?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodytns:getLcValuesResponse xmlns:tns=http://www.myplace.com/MyWebService/xsd;tns:columntns:values tns:href=urn:uuid:DF83F3FB6FDDA694771217252894381 tns:count=3001 //tns:column/tns:getLcValuesResponse/soapenv:Body/soapenv:Envelope 38 --MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835 2000 Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-ID: urn:uuid:DF83F3FB6FDDA694771217252894381 (... Binary data with missing bytes ...) 38 --MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835 2 -- 0 Connection #0 to host localhost left intact -- View this message in context: http://www.nabble.com/Outgoing-SwA-binary-attachments%3A-All-0xFF-bytes-are-missing-tp18689209p18689209.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Outgoing SwA binary attachments: All 0xFF bytes are missing
Hello I have a web service that sends binary data as MIME attachments (SwA). I realized that the data received by the client was not exactly the same as the data given to the web service. More precisely, a dozen bytes are missing (out of 12,004). All the missing bytes should have had the value 0xFF (255) -- and all the 0xFF bytes from the original data are missing. The original data represents an array of 3001 float values. I'm suspecting a charset-related problem... Does anyone have any clue about what happens? Thanks a lot in advance. Hereafter: What was received by the client HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835; type=text/xml; start=0.urn:uuid:[EMAIL PROTECTED] Transfer-Encoding: chunked Date: Mon, 28 Jul 2008 13:48:15 GMT 243 --MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835 Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: 0.urn:uuid:[EMAIL PROTECTED] ?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodytns:getLcValuesResponse xmlns:tns=http://www.myplace.com/MyWebService/xsd;tns:columntns:values tns:href=urn:uuid:DF83F3FB6FDDA694771217252894381 tns:count=3001 //tns:column/tns:getLcValuesResponse/soapenv:Body/soapenv:Envelope 38 --MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835 2000 Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-ID: urn:uuid:DF83F3FB6FDDA694771217252894381 (... Binary data with missing bytes ...) 38 --MIMEBoundaryurn_uuid_DF83F3FB6FDDA694771217252895835 2 -- 0 Connection #0 to host localhost left intact -- View this message in context: http://www.nabble.com/Outgoing-SwA-binary-attachments%3A-All-0xFF-bytes-are-missing-tp18689243p18689243.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
