RE: [JBoss-dev] Design: Plans to decouple JBoss from log4j

[Randahl Fink Isaksen]

Title: Message

marc f     There is no reason telling me the basics of the business, Morpheus - I might very well swallow that famous addictive red pill you keep on pushing. It would suit my company quite well if I got deeper into what is becoming a more and more central technology to us, and since you guys all seem like a friendly bunch …   However, while getting more and more insight into the inner workings of JBoss, I will keep on posting messages like the one starting this thread. This will give me a chance to find out more about the issues I currently have while at the same time giving me a better idea of the current state of things and thus finding out where I can contribute.   Now regarding this thread, I am glad to get the clarification that it is simply because the feature has not been implemented yet. With extensive technologies like JBoss it is often  hard to tell if the technology cannot do what you want it to, or if it is just because you have not yet found that very important 4 line forum post which tells you what the magic trick is. I find the subscription documentation to be really great but even with those in your hands, few would survive without the forums.   Bottom line: You will see me writing similar posts in the future, it is not asking you do something I did not pay you to do, it is simply trying to get clarification, and trying to find out what can be done to make JBoss an even better technology.     Have a nice weekend marc f   Randahl   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of marc fleury Sent: 4. oktober 2002 15:43 To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Design: Plans to decouple JBoss from log4j   randahl,   I am swimming back up this thread as it seems it has kicked up a fuss.   dude, the bottom line is very simple.  If you really care, you put your time on the line, or you pay us to do it (we do a lot of work under contract for customers on this list).  I do believe that the separation is already there, or almost there, so it wouldn't be too much hassle to really decouple ( i do believe it is already there again).  At most it would be a simpler configuration file with possibly a SAR, although there is some logging going on at boot time.   The separation between "nice to have and must have" is determined by your eagerness to give us your time or your money, if you are ready to pay in one form then the feature is real, you really need it.   As you know Einstein already proved time=money and it helps us keep the codebase real, with real features, but we let you say how real you want it.   marc f -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Randahl Fink Isaksen Sent: Friday, October 04, 2002 5:10 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Design: Plans to decouple JBoss from log4j 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