> I think just the custom logging class that replaces the existing Log, Logger
> and
> JBossCategory and the use of TRACE. I'm in agreement with you on this
> items so unless there is other input to the contrary the details of the new
> Logger or
> whatever is all that remains.

What about the current Log.setLog() stuff?  Will that go away?  It was one
of the priary reasons that I did not convert some components to Log4j.

> Due to the proposed change to have a Logger class in
> log4j we probably don't want to use Logger as a classname to minmize name
> clash issues.

There is no reason why we can not use Logger, I would not suggest anything
else.  There will be almost no reasons to import org.jboss.log.Logger and
org.apache.log4j.Logger, we will simply use our version.  Applications can
choose which they prefer and use it.

Only our Logger impl will have to worry about the Log4j Logger, but simply
put:

public class Logger
    extends org.apache.log4j.Logger
{
   // ...
}

--jason


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to