[ 
https://issues.apache.org/jira/browse/VELOCITY-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036258#comment-16036258
 ] 

Michael Osipov commented on VELOCITY-880:
-----------------------------------------

Right, that's correct. In my opinion using {{getAsciiStream()}} is wrong 
because you will lose the highest bit on a byte if the driver tries the 
conversion. I'd rather rely on {{getBinaryStream()}} for raw bytes and put a 
reader on top or rather completely rely on the driver and use 
{{getCharacterStream()}} which will return a reader for you. I can test that 
for Oracle, MySQL, SQL Server only at work which will take some time. As for 
PostgreSQL and other DBs someone else has to contribute. I think we need to 
test HSQLDB and H2 ourselves and database encoding with UTF-8 or UTF-16 only.

> DataSourceResourceLoader corrupts UTF-8 encoded characters in template
> ----------------------------------------------------------------------
>
>                 Key: VELOCITY-880
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-880
>             Project: Velocity
>          Issue Type: Bug
>    Affects Versions: 2.1.x
>         Environment: Oracle12c and HSQLDB 2.3.4, JDK 1.8
>            Reporter: James R Doyle
>         Attachments: project.tar.gz, velocity-880.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> A long-withstanding bug in the DataSourceResourceLoader corrupts UTF-8 
> templates retrieved from the database.  The Unit Test suite for this resource 
> loader has deficiencies that hide the bug. 
> The cause of the problem is this:
> {code}
>       InputStream rawStream = rs.getAsciiStream(templateColumn);
> The resolution of the problem is simply:
>       Reader r = rs.getCharacterStream(templateColumn);
>       InputStream rawStream = null;
>            try {
>                 rawStream = IOUtils.toInputStream(IOUtils.toString(r), 
> encoding);
>                 } catch (IOException ioe) {}
> {code}
> Once done, the test failure vanishes:
>         org.junit.ComparisonFailure: Unicode test failed.  
>         Expected :The Euro Currency Symbol € is a two-byte UTF-8 encoded 
> character.
>         Actual   :The Euro Currency Symbol ? is a two-byte UTF-8 encoded 
> character.
> The bug was verified and the fix was tested against Oracle12c and HSQLDB 
> 2.3.4 using a CLOB column to store the template data.
> The Unit Tests for this resource loader need attention.
> Please see VELOCITY-599 ; long standing problem, which has been erroneously 
> marked as resolved but has been in the codebase for a long time.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org

Reply via email to