[
https://issues.apache.org/jira/browse/VELOCITY-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614778#action_12614778
]
Christopher Schultz commented on VELOCITY-599:
----------------------------------------------
Er... that should have been getCharacterStream. In my zeal to comment, I didn't
double-check that ;)
I read the documentation for ResultSet.getAsciiStream, which claims to to
whatever conversion is necessary to convert from the native database format to
ASCII. For those characters that don't fit into the ASCII character set, do you
end up with multiple ASCII characters? I'm not sure if there's a good way to
get around this other than Mark's hack, except that you'll have to pre-define
the encoding you expect the database to use.
Perhaps the API could change for Velocity 1.6 to use Readers instead, or maybe
something like an InputSource a la the JAXP API... ?
> 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
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
