Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.2-RC1, 2.2
-
Fix Version/s: 3.0
-
Component/s: PicoContainer (Java)
-
Labels:None
-
Number of attachments :
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
Jörg Schaible
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Affects Version/s | 1.2-RC1 [ 11979 ] | |
| 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. |
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. |
Isn't this fixed for 2.2?
Show
Michael Rimov
added a comment - Isn't this fixed for 2.2?
Michael Rimov
added a comment - Isn't this fixed for 2.2? Michael Rimov
made changes -
| Affects Version/s | 2.2 [ 14251 ] |
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 - 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);
Paul Hammant
added a comment - 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);
Since we haven't heard anything to clarify on this bug, I'm going to close this issue. Please feel free to reopen if needed.
Show
Michael Rimov
added a comment - Since we haven't heard anything to clarify on this bug, I'm going to close this issue. Please feel free to reopen if needed.
Michael Rimov
added a comment - Since we haven't heard anything to clarify on this bug, I'm going to close this issue. Please feel free to reopen if needed. Michael Rimov
made changes -
| Status | Open [ 1 ] | Closed [ 6 ] |
| Fix Version/s | 3.0 [ 14410 ] | |
| Resolution | Won't Fix [ 2 ] |
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?