-
1. Re: Logging.. log4j or commons.logging
marklittle Jul 29, 2006 2:22 PM (in response to kurtstam)We have a generic logging framework that ships as part of JBossTS, though it isn't tied to it. It interfaces with all of the logging implementations and provides support for I18N/L10N compatibility. There's actually a JIRA task for that already.
I don't have a strong preference. But I know this framework works and users have been able to plug in their own (proprietary) logging implementations without affecting the system (TS in this case). I'd suggest at least giving it a look. My intention was to use it for the first GA (or maybe the 2nd). In the meantime, log4j is probably good enough for us. -
2. Re: Logging.. log4j or commons.logging
starksm64 Jul 29, 2006 6:23 PM (in response to kurtstam)log4j is not without its own problems for servers. There are known deadlock problems and bottlenecks due to appender locking issues:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=71278
Merging the existing org.jboss.logging abstraction with the JBossTS version to create a common logging interface that does not conflict with existing logging abstraction is what I want to see. -
3. Re: Logging.. log4j or commons.logging
marklittle Jul 29, 2006 6:36 PM (in response to kurtstam)I agree. It's purely a matter of time and resources at the moment. Going the log4j route (or any specific implementation) for ESB would only be a stop-gap. Once we get the beta release of ESB out the door this is something we can definitely look at.
-
4. Re: Logging.. log4j or commons.logging
marklittle Jul 29, 2006 6:38 PM (in response to kurtstam)BTW, Kurt I updated the JBoss developer guide about 4 months ago with details on the logging infrastructure we have in TS and specifically on I18N/L10N capabilities. It would be worth checking that out post beta release.
-