PicoContainer
  1. PicoContainer
  2. PICO-400

Need more logging/monitoring on parameter resolution/injectee selection

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.0
    • Fix Version/s: None
    • Component/s: PicoContainer (Java)
    • Labels:
      None
    • Number of attachments :
      0

      Description

      Pico REALLY needs more information tracing as it goes through its finding matches for component resolution when injecting different types. I'm finding I'm having to resort to debugging because something isn't getting injected when its just a wrong type being registered.

      Since ComponentMonitor does its job on handling component modification, I'd like to propose:

      interface InjectionTracingMonitor

      To save on the already cluttered picocontainer constructors, I say we just default to NullInjectionTracingLogicMonitor and then create a "swapInjectionTracingMonitor()" method for those that need to turn on that level of debugging.

      Duties will involve:

      • Notification if an injectee is matched with its component
      • Notification if a component is rejected as a match due to incompatible types
      • Notification if a component parameter is using default component resolution or a specific constant or specific component parameter.

      That kind of thing.

        People

        • Assignee:
          Paul Hammant
          Reporter:
          Michael Rimov
        • Votes:
          0 Vote for this issue
          Watchers:
          1 Start watching this issue

          Dates

          • Created:
            Updated: