[
https://issues.apache.org/jira/browse/VELOCITY-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-660.
-------------------------------------
Resolution: Fixed
Now that we moved to the slf4j logging facade, such a strategy can be achieved
using a specific slf4j binding.
> consider moving logging (and errors?) to an event/monitor approach
> ------------------------------------------------------------------
>
> Key: VELOCITY-660
> URL: https://issues.apache.org/jira/browse/VELOCITY-660
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 2.x
> Reporter: Nathan Bubna
> Fix For: 2.x
>
>
> As suggested in the comments for VELOCITY-168:
> "use so called Monitors.
> It means: use events to inform "subscribed" events listeners about something
> "interesting" which occurs inside velocity engine - e.g "template loaded",
> "parsing error" etc.
> Then if somebody is willing to log those events to log file - he can very
> easily create event listener(s) (probably just one class!!) which will log
> incoming events using what ever logging API he/she wishes."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
