Velocity
  1. Velocity
  2. VELOCITY-660

consider moving logging (and errors?) to an event/monitor approach

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.x
    • Fix Version/s: 2.x
    • Component/s: Engine
    • Labels:
      None

      Description

      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."

        Activity

        Nathan Bubna created issue -
        Hide
        Adrian Tarau added a comment -

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

        Show
        Adrian Tarau added a comment - I like this one...one thing is the logging and another thing is sending important events to the application
        Mark Thomas made changes -
        Field Original Value New Value
        Workflow jira [ 12449190 ] Default workflow, editable Closed status [ 12551703 ]
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12551703 ] jira [ 12552233 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Nathan Bubna
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development