[
https://issues.apache.org/jira/browse/VELOCITY-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henning Schmiedehausen closed VELOCITY-310.
-------------------------------------------
> Exceptions thrown during Servlet template merging
> -------------------------------------------------
>
> Key: VELOCITY-310
> URL: https://issues.apache.org/jira/browse/VELOCITY-310
> Project: Velocity
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.4
> Environment: Operating System: All
> Platform: All
> Reporter: Clive Haworth
> Assigned To: Velocity-Dev List
>
> My servlet extends VelocityServlet and returns a valid template reference in
> the handler. The template references a method which does some DB access. If I
> turn off the DB and run the app, I have two issues:
> 1/ I don't get the exception. I can work around this by providing my own error
> () handler to deal with it, work out whether the exception has been logged
> etc
> and return some error HTML. Messy but hey, Velocity is free.
> 2/ Oh dear. It seems the template merging flushes out what it has processed
> so
> far before re-throwing the exception. I dont want this. If an error occurs
> during parsing, I want the user to see an error message, not half a template
> !!
> Hope I haven't missed anything obvious, but how do I do this ?
> NOTE
> I quite like Velocity and managed to integrate my own Logger (although it
> would
> have been easier if the authors had used the Apache commons Logging stuff).
> This is better than FreeMarker.
--
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]
