Mantis - Resin
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
1124 | feature | always | 05-18-06 13:11 | 05-30-06 10:34 | |
|
|||||
Reporter: | eahollin | Platform: | |||
Assigned To: | ferg | OS: | |||
Priority: | normal | OS Version: | |||
Status: | closed | Product Version: | 3.0.19 | ||
Product Build: | Resolution: | fixed | |||
Projection: | none | ||||
ETA: | none | Fixed in Version: | 3.0.20 | ||
|
|||||
Summary: | 0001124: Incomplete java.util.logging implementation? | ||||
Description: |
In Resin 2.1.x, we used the java.util.logging API to dynamically display and change the configured Loggers and corresponding Levels. Now in Resin 3.0.x, it appears Resin is extending/overriding the functions of the java.util.logging package. However, Resin's custom LogManager extension class does not appear to provide an overridden version of the getLoggerNames() method. As a result, we cannot pull an Enumeration of Loggers so that we can dynamically manipulate their levels. Is an overridden version of getLoggerNames() expected in a future release? Thanks! |
||||
Steps To Reproduce: | |||||
Additional Information: | |||||
Relationships | |||||
Attached Files: |
Notes | |||||
|
|||||
|
|