Well, we happen to be one of the companies who would like JBoss to have support for the logging system of what you call the "JDK 1.4 crap API".
If what you are saying is that JBoss is already decoupled from its logging system I am quite happy - from the docs it just seemed to me it was not. But why is there no support for using the standard java.util.logging mechanism with JBoss? Does anyone know where / how JBoss is configured for using a certain logging system? Randahl -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jason Dillon Sent: 4. oktober 2002 11:48 To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Design: Plans to decouple JBoss from log4j I just looked over the commons logging api and it closly resembles org.jboss.logging.Logger. The only major differences are that Logger is a class and is serializable (the log4j commons log impl does not) not a big deal, as we can write a subclass of the log4j log factory to produce serializable objects. So... they are so similar why switch? One reason might be that there are already plugins to JDK 1.4 crap API. ANother reason might be because Log is an interface, allowing proxies to be used (why I don't know... but I am sure I can think of a reason). Do you know how you switch the LogFactory impl? I am guessing there is a system property, but I did not see anything obvious by looking at the javadocs. It might warrent a little investigation to see how useful this might be, and what issues would have to be resolved (like the lack of a direct log(level, msg) method) --jason On Fri, 4 Oct 2002, Randahl Fink Isaksen wrote: > Are there any plans to decouple JBoss from the logging system used? > > > > According to the docs it seems JBoss is currently tightly coupled to > log4j. I have absolutely nothing against log4j, for all I know it is > (one of) the best logging systems available to the Java platform. > However, I do think JBoss ought to be independent of the logging system. > When you set up JBoss in your server environment you have the freedom to > choose whichever database you want, if you do not want to use the > prepackaged HyperSonic database, but, surprisingly, there is no way > around the prepackaged logging system. > > > > If you are in an environment with several different running applications > there is a big chance you have already chosen a preferred logging system > when you start using JBoss, and there is no guarantee that your > preferred logging system happens to be log4j. One obvious choice of > course being Java's built in java.util.logging system - but there are > many other options... your logging system written by your own company, > for instance. > > > > I noticed on jakarta.apache.org that they have written a logging > decoupling mechanism as part of their Jakarta Commons package. Without > knowing the details of JBoss development at all, I would like to raise > the question of whether JBoss could use that package. > > > > Since logging is a central part of JBoss I would imagine that decoupling > JBoss from its logging system had better happen sooner than later - the > code base is growing rapidly and so is the coupling to log4j. > > > > > > Randahl > > > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
