[jira] Commented: (VELOCITY-660) consider moving logging (and errors?) to an event/monitor approach

["Adrian Tarau (JIRA)" <de...@velocity.apache.org>]

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

Adrian Tarau commented on VELOCITY-660:
---------------------------------------

I like this one...one thing is the logging and another thing is sending  important events to the application

> 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.0
>            Reporter: Nathan Bubna
>             Fix For: 2.0
>
>
> 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 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