[
https://issues.apache.org/jira/browse/VELOCITY-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614452#action_12614452
]
Christopher Schultz commented on VELOCITY-599:
----------------------------------------------
<quote>
} catch (Exception ex) {
throw new
ResourceNotFoundException("DataSourceResourceLoader:UnsupportedEncodingException");
}
</quote>
I object to over-catching exceptions. If you only expect
UnsupportedEncodingException, then only catch that. If an NPE is thrown and you
report it as an UEE, you'll confuse the heck out of whoever it looking at the
stack trace. Also, if possible, use chained exceptions (like throw new
ResourceNotFoundException("message", originalException) so you can get a /full/
stack trace.
> 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]
