[ http://issues.apache.org/jira/browse/AXISCPP-779?page=all ]
Adrian Dick resolved AXISCPP-779:
---------------------------------
Fix Version: current (nightly)
Resolution: Fixed
Assign To: Adrian Dick
I think there has been a mis-understanding of the specifications and how
base64Binary works.
When the specification refers to collapsing whitespace it means for the encoded
string -- which according to the encoding rules of base64binary should not
produce any whitespace anyway.
The actual original data contained within the base64Binary object should be
unchanged, as this is just binary -- albeit in this example it happens to be
text.
I have updated the internal class for Base64Binary to intiailize a
WhiteSpaceObject as "collapse", though it shouldn't really make a difference as
whitespace shouldn't be produced.
I have also updated the expected response for XSD_base64Binary2 to reflect this
fuller understanding of what should be happening.
> Whitespaces are not stripped off in XSD_base64Binary type inputs.
> ------------------------------------------------------------------
>
> Key: AXISCPP-779
> URL: http://issues.apache.org/jira/browse/AXISCPP-779
> Project: Axis-C++
> Type: Bug
> Reporter: Manohar
> Assignee: Adrian Dick
> Fix For: current (nightly)
>
> The leading or trailing whitespaces in XSD-base64Binary type input are not
> stripped off.
> As per the specification, all leading and trailing whitespace will be
> stripped off. The following piece of code shows the problem.
> sprintf(endpoint, "%s", url);
> XSD_base64Binary* ws = new XSD_base64Binary(endpoint);
> xsd__base64Binary input;
> xsd__unsignedByte* testUB = (xsd__unsignedByte*)" <test><xml>
> some dod&y string </xml></test> ";
> input.__ptr=testUB;
> input.__size=100;
> // Test non-nillable element
> xsd__base64Binary result = ws->asNonNillableElement(input);
> cout << "non-nillable element" << endl;
> cout << " size=" << result.__size << endl;
> cout << " data=" << result.__ptr << endl;
> XSD_base64Binary2 testcase shows this problem.
> Regards
> Manohar
--
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
