Ticket #295 (closed enhancement: fixed)

Opened 9 months ago

Last modified 6 months ago

Logging package needs LoggerManager

Reported by: peterfarrell Owned by: peterfarrell
Priority: major Milestone: Mach-II 1.8.0 alpha
Component: framework - logging Version: 1.8.0 - Framework
Keywords: log logging logger LoggerManager caching CacheStrategyManager Cc:
Blocking: Blocked By:

Description

Working on my presentation on using Mach-II's caching / logging packages at cf.Objective() I realized we have a nice CacheStrategyManager CFC for the caching package, but no simile in the logging package. So I think we should add LoggerManager that is hierarchical aware just like its kin in the caching package and upgrade the LoggingProperty to use the new manager instead of storing the strong references to the loggers in the property itself.

Attachments

Change History

Changed 9 months ago by peterfarrell

  • status changed from new to closed
  • resolution set to fixed

(In [1563]) - Changes how we store loggers which is easier in the long run and better for people that are using the logging without the MVC framework closes #295

Changed 9 months ago by doug.arogos@…

It looks like this breaks the Debugging tab in the Dashboard, with the following error:

The method getLoggerByName was not found in component /MachII/1.8.0.alpha/logging/LoggingProperty.cfc.

The error is thrown at line 97 in <dashboard>/listeners/DebuggingListener.cfc.

Changed 9 months ago by peterfarrell

  • status changed from closed to reopened
  • resolution fixed deleted

@Doug, thanks for finding this defect. Looks like I forgot to add in the helper methods to the logger manager in the logging property so the API does not change between 1.6 and 1.8. I'll fix this up soon. You'll have to reload your entire application in order to pick up the changes.

Changed 9 months ago by peterfarrell

  • status changed from reopened to closed
  • resolution set to fixed

(In [1577]) closes #295

Changed 9 months ago by anonymous

Awesome, thank you for the fast response! I applied the patch and it worked great!

Changed 9 months ago by peterfarrell

Glad to have been of help and thanks for the word of appreciation -- not something we hear too often around here so it's music to my ears. After looking at the exception, it looked like an easy fix (it also reminded me that I changed the API which is a bad thing to do anyways) and therefore I hate low hanging fruit tickets. So I bashed it out of the way by adding in the helper methods so the API remains the same between 1.6 and 1.8.

Add/Change #295 (Logging package needs LoggerManager)

Author


E-mail address and user name can be saved in the Preferences.


Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.