You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Christopher Schultz (JIRA)" <de...@velocity.apache.org> on 2011/01/06 23:30:45 UTC

[jira] Commented: (VELOCITY-599) DataSourceResourceLoader doesn't support UTF8

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

Christopher Schultz commented on VELOCITY-599:
----------------------------------------------

Mark's hack could waste huge amounts of memory due to the complete fetching of the clob, then converting it to a byte array, then reading from that.

I'm not sure why using getBinaryStream doesn't work. Can someone explain? Using getClob sounds like it's just going to make us convert from char to binary and then back again at a higher level.

I'll make another push to change template fetching to use Readers. Maybe in 2.0?

> DataSourceResourceLoader doesn't support UTF8
> ---------------------------------------------
>
>                 Key: VELOCITY-599
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-599
>             Project: Velocity
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: 1.5
>         Environment: WindowsServer2003 R2, Oracle10g(10.2.0,UTF8characterSet),  jdk1.5.0_12
>            Reporter: markchen
>             Fix For: 2.x
>
>
> If templates are stored in the database instead of files,the characters retrived becomes garbled.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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