jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • PicoContainer
  • PICO-253

Per-Instance ComponentMonitor implementation

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.2-RC1, 2.2
  • Fix Version/s: None
  • Component/s: PicoContainer (Java)
  • Labels:
    None

Description

Gems should contain a ComponentMonitor implementation that does instance-level logging (rather than class-level).

This will allow users increased granularity when using a CM.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Paul Hammant added a comment - 23/Oct/05 6:31 AM

Assuming Log4J/Clogging..

And is the instance the monitor instance or the component instance ?

Could it be that, some how, the CM should inticate which instance of the component via the JVM reference ID for the object, ot via a new log category?

Show
Paul Hammant added a comment - 23/Oct/05 6:31 AM Assuming Log4J/Clogging.. And is the instance the monitor instance or the component instance ? Could it be that, some how, the CM should inticate which instance of the component via the JVM reference ID for the object, ot via a new log category?
Hide
Permalink
Michael Rimov added a comment - 10/May/08 3:20 PM

Isn't this fixed for 2.2?

Show
Michael Rimov added a comment - 10/May/08 3:20 PM Isn't this fixed for 2.2?
Hide
Permalink
Paul Hammant added a comment - 10/May/08 4:28 PM

I'm not sure what Peter is after. Pete ?

CM has better methods in Pico 2.x than 1.x that's for sure.

In 2.2, aside from CM, there is a way to inject custom things like you'd see for Log4J and CommonsLogging. Refer usages of SwedeFactoryInjector in http://svn.codehaus.org/picocontainer/java/2.x/trunk/pico/container/src/test/org/picocontainer/DefaultPicoContainerTestCase.java

or did you mean something like:

pico.as(withCustomMonitor(myMonitor1)).addComponent(Foo.class,FooImpl.class);
pico.as(withCustomMonitor(myMonitor2)).addComponent(Bar.class,BarImpl.class);
Show
Paul Hammant added a comment - 10/May/08 4:28 PM I'm not sure what Peter is after. Pete ? CM has better methods in Pico 2.x than 1.x that's for sure. In 2.2, aside from CM, there is a way to inject custom things like you'd see for Log4J and CommonsLogging. Refer usages of SwedeFactoryInjector in http://svn.codehaus.org/picocontainer/java/2.x/trunk/pico/container/src/test/org/picocontainer/DefaultPicoContainerTestCase.java or did you mean something like:
pico.as(withCustomMonitor(myMonitor1)).addComponent(Foo.class,FooImpl.class);
pico.as(withCustomMonitor(myMonitor2)).addComponent(Bar.class,BarImpl.class);

People

  • Assignee:
    Unassigned
    Reporter:
    peter royal
Vote (0)
Watch (0)

Dates

  • Created:
    28/Aug/05 4:55 PM
    Updated:
    10/May/08 4:28 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.