[ http://jira.codehaus.org/browse/XFIRE-378?page=comments#action_64722 ]
Matthijs Wensveen commented on XFIRE-378: ----------------------------------------- Thanks for fixing this. Wierd that the example from http://java.sun.com/webservices/docs/1.5/api/javax/xml/stream/XMLStreamReader.html#getTextCharacters(int,%20char[],%20int,%20int) that was literally in the source does not work.... I'm not sure why it wouldn't work, but I haven't really looked into it. Anyway, thanks again for fixing this. > xsd:base64Binary .NET interop problem > -------------------------------------- > > Key: XFIRE-378 > URL: http://jira.codehaus.org/browse/XFIRE-378 > Project: XFire > Type: Bug > Versions: 1.1-RC1 > Reporter: Wouter > Assignee: Dan Diephouse > Fix For: 1.1 > Attachments: envelope.dat, envelope.dat, testcase.zip > > > .NET encodes base64 according to specs: line feed after 76 bytes. > When we upload the contents of a file as a base64Binary byte[] with a .NET > client to our XFire web service, the size and contents of the byte array that > the method on the service receives do not match. It seems XFire has problems > decoding base64Binary data that has a fixed line length of 76 characters. > Testing with other clients that sent the data as one line (chunked or not > chunked) did work. > According to the XML Schema Datatypes spec (chapter 3.2.16) the line-length > of 76 is not mandatory and must not be enforced. This suggests that a > line-length of 76 characters is allowed, however. > Attached is the request done by the .Net client (including HTTP headers and > SOAP Envelope). Using a base64 decoding tool you can convert the data to a > .gif file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
