[
https://issues.apache.org/jira/browse/WINK-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869511#action_12869511
]
Shay Tsadok commented on WINK-282:
----------------------------------
Hi Bryant,
Thanks for the fix! Since we are using Http 1.1 this solution fits.
BTW - I would like to take the latest Wink version including your fix, In order
to avoid custom "StringProvider" in my code.
I've noticed that the latest build is from 4-May-2010 (taken from:
http://apache.mivzakim.net/incubator/wink/1.1-incubating/apache-wink-1.1-incubating.zip),
Is there a chance to promote the build?
Thanks,
Shay
> StringProvider may not work properly when trying to write an "Xml string"
> --------------------------------------------------------------------------
>
> Key: WINK-282
> URL: https://issues.apache.org/jira/browse/WINK-282
> Project: Wink
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.0, 1.1
> Reporter: Shay Tsadok
> Assignee: Bryant Luk
> Priority: Critical
>
> Hi,
> StringProvider.getSize() returns t.length() even when the required charset is
> "UTF-8".
> That might be problematic for cases in which the string contains "2 bytes"
> letters - in that case the real stream length getting from the
> StringProvider.writeTo() will be greater compare to the
> StringProvider.getSize().
> The FlushResultHandler uses the provider to set the "Content-Length" to be
> the StringProvider.getSize() which is less that the real stream we write to
> the output!
> This is very problematic, in our case the client gets corrupted xml.
> Thanks in advance.
> Shay
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
