[Bug 150] New: LogManager is needed but not implemented yet

http://bugzilla.slf4j.org/show_bug.cgi?id=150

           Summary: LogManager is needed but not implemented yet
           Product: SLF4J
           Version: 1.5.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: log4j-over-slf4j
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]


org.apache.log4j.LogManager is used by some legacy applications I've worked
with. There is no equivalent in log4j-over-slf4j. Therefore these applications
cannot use log4f-over-slf4j and have to remain using Log4j.

There are several other unimplemented public classes in org.apache.log4j but I
have not seen any others in use.


--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dev mailing list
[hidden email]
http://www.slf4j.org/mailman/listinfo/dev

http://bugzilla.slf4j.org/show_bug.cgi?id=150


Thorbjørn Ravn Andersen <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #1 from Thorbjørn Ravn Andersen <[hidden email]>  2009-09-15 17:32:32 ---
Could you list the specific functionality you need.

It may be possible to create enough code to make your program run, but do the
equivalent functionality in the chosen backend.


--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dev mailing list
[hidden email]
http://www.slf4j.org/mailman/listinfo/dev

http://bugzilla.slf4j.org/show_bug.cgi?id=150





--- Comment #2 from Ceki Gulcu <[hidden email]>  2009-09-15 17:36:04 ---
As Thorbjørn points out, it would be helpful if you could list the missing
methods in LogManager.


--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dev mailing list
[hidden email]
http://www.slf4j.org/mailman/listinfo/dev

http://bugzilla.slf4j.org/show_bug.cgi?id=150


Ceki Gulcu <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #3 from Ceki Gulcu <[hidden email]>  2009-09-23 12:39:02 ---
In log4j-over-slf4j, added missing LogManager. This class is a minimal
implementation of the original org.apache.log4j.LogManager (as found
in log4j 1.2) delegating all calls to SLF4J.

The fix will be ship with SLF4J 1.5.10.

It implementation does NOT implement the setRepositorySelector(),
getLoggerRepository(), exists(), getCurrentLoggers(), shutdown() and
resetConfiguration() methods which do not have SLF4J equivalents. If the fix is
insufficient to cover your needs, please re-open this report.


--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dev mailing list
[hidden email]
http://www.slf4j.org/mailman/listinfo/dev

http://bugzilla.slf4j.org/show_bug.cgi?id=150


Rick Beton <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




--- Comment #4 from Rick Beton <[hidden email]>  2009-10-09 15:08:49 ---
Sorry for the late reply.

I have legacy code using only LogManager's

void resetConfiguration()
Logger getRootLogger()

In my case, it would be sufficent to implement an empty method for
resetConfiguration(), although I don't know whether this would be good general
solution. getRootLogger() must return a non-null logger.

A synopsis of the legacy code is:

LogManager.resetConfiguration();
Logger rootLogger = LogManager.getRootLogger();
rootLogger.setLevel(Level.WARN);

(Unfortunately, this code cannot be modified because it is expected to continue
to work with Log4J also.)

Thanks.


--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dev mailing list
[hidden email]
http://www.slf4j.org/mailman/listinfo/dev