[ http://issues.apache.org/jira/browse/XALANJ-2087?page=all ]
Brian Minchau resolved XALANJ-2087:
-----------------------------------
Resolution: Fixed
Patch was committed to CVS. The old code had a concept of a maximum unicode
value, and assumed
that all characters less than that were in the encoding (except in the 0 to 127
range which were handled
differently). This is not true for many encodings, which have multiple gaps in
their table.
New code uses the underlying supported Java library, and caches results for
performance.
Yash did some performance runs with this patch, most were unchanged, a few
tests ran faster, a few ran
slower, on average about the same as before. I'm satisfied with that.
> Get rid of the dependency on sun.io.CharToByteConverter
> -------------------------------------------------------
>
> Key: XALANJ-2087
> URL: http://issues.apache.org/jira/browse/XALANJ-2087
> Project: XalanJ2
> Type: Improvement
> Components: Xalan
> Versions: CurrentCVS
> Reporter: Jack
> Assignee: Brian Minchau
> Fix For: 2.7.0-future-release
> Attachments: Converter.java, Encodings&Converter.zip,
> serializer.jira.2087.patch1.txt
>
> The class org.apache.xml.serializer.Encodings references
> sun.io.CharToByteConverter directly, while the latter is not a public API. Is
> it possible to use java.nio.charset classes instead to remove this dependency?
--
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]
