Can't we just create a special org.apache.log4j.Category (and later
org.apache.log4j.Logger) and make it so none of the methods do anything.
We could make it so the factory methods simply return our degenerate
Category. This would make the smallest possible log4j distribution for
embedded use.
-Phil
"marc fleury"
<[EMAIL PROTECTED]> To:
Sent by:
<[EMAIL PROTECTED]>
[EMAIL PROTECTED] cc:
eforge.net Subject: RE:
[JBoss-dev] Dropping the
System.out calls in the
jmx code
05/02/2002 09:00 AM
The idea of a "logger" in an embedded system is kind of strange, what are
you going to log to ??? I mean most of the time is your embedded chip going
to lug around a 50Gig barracuda IDE??? no... are you going to open an
socket
just for "logging"... no... are you going to fill your memory (tight if we
believe specs) with "log" message... no.
Logging in J2ME (JBoss4.0) strikes me as a DEBUGGING feature. Useful while
in development. Then YES you want to know what is going on, that much is
trivial to see.
This is where log4j becomes interesting, we would essentially DISABLE it
for
use in production J2ME while keeping it on for development but the code
remains the same. So the port to log4j is interesting in that respect.
So the question for you JBoss4.0 fans out there is how small can we get
log4j to be to do NOTHING, i.e. redirect all messages to /dev/null but
still
keep the code the same in our JBossMX/JBoss layers.
marcf
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Adrian Brock
|Sent: Thursday, May 02, 2002 7:05 AM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] Dropping the System.out calls in the jmx code
|
|
|Making the JBossMX logger use log4j is easy enough.
|The only problem is log4j isn't configured until
|after the MBeanServer is created in ServerImpl.
|This isn't a big problem since the loggers are designed
|to boot with System.err and swap over to the required
|logging implementation when it becomes available.
|
|There are also some places in the code that do
|System.out directly that need fixing.
|
|I'll do this at the weekend.
|
|I'm was also looking at reducing the footprint for
|embedded, while allowing functionality to be added later.
|My early attempt isn't very good. The footprint is
|9k compared with 2k for common's Logger.
|
|Regards,
|Adrian
|* * *
|
|View thread online:
http://jboss.org/forums/thread.jsp?forum=66&thread=14612
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
