Most of my projects are WebSphere projects.  I can see iBATIS logging statements in the WebSphere logs - but WebSphere uses it's own internal logging implementation to hook into commons logging.  So I wrote this FAQ about how to see logging statements in WebSphere because it's not as simple as you might hope for:
 
http://opensource.atlassian.com/confluence/oss/display/IBATIS/How+do+I+Configure+Logging+in+WebSphere
 
It would help us diagnose the problem if we knew more about the runtime environment.
 
Jeff Butler

 
On 6/11/06, Ben Munat <[EMAIL PROTECTED]> wrote:
Well, I don't know about Tarek, but I've always used commons-logging with log4j
underneath... so both are on my classpath.

I've used ibatis on several projects now, and thinking back, I don't recall ever seeing
ibatis log statements, though I always put com.ibatis and java.sql in my log properties.

Jeff, Brandon, do you see ibatis log statements in you logs? Are you using commons logging
or something else?

b

Jeff Butler wrote:
> It's also good to remember that iBATIS will use commons logging if it
> finds it in the classpath (for example, WebSphere has commons logging on
> the application server classpath QED iBATIS allways uses commons logging
> on WebSphere).
>
> The search order for log implementations is:
>
> 1. commons logging
> 2. log4j
> 3. JDK 1.4 logging
>
> iBATIS will use the first one it finds.
>
> Whenever there's a problem with iBATIS seeming to ignore the
> log4j.properties file I always think that iBATIS is trying to use
> commons logging instead.
>
> So look to see if commons logging is in the classpath somewhere - that's
> probably the problem.
>
> Jeff Butler
>
>
>
> On 6/11/06, *Brandon Goodin* <[EMAIL PROTECTED]
> <mailto: [EMAIL PROTECTED]>> wrote:
>
>     We pulled out commons logging because we wanted zero dependencies and
>     it was such an insignificant amount of code. It seemed silly to create
>     dependencies for such a small amount of code. We are not going to add
>     commons logging. But, we will fix our logging if it is not functioning
>     :) If this is a common issue that folks are having then please submit
>     a JIRA issue.
>
>     Brandon
>
>     On 6/11/06, Ben Munat <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
>      > Yeah it's a strange name/location but it should work... and Tarek
>     claims to be getting
>      > other log output to that file... and Tarek's question made me
>     realize that I've never
>      > actually been getting com.ibatis logging in my log files.
>      >
>      > So, I think there's a legitimate question here. Is there some
>     trick to getting ibatis to
>      > log? And, why does ibatis have it's own Log and LogFactory
>     classes? Should these, if they
>      > do cause problems, be switched to commons, juli, or sl4j?
>      >
>      > Clinton? Larry? Nathan? Anyone?
>      >
>      > b
>      >
>      > Graeme J Sweeney wrote:
>      > > On Sun, 11 Jun 2006, Tarek Nabil wrote:
>      > >
>      > >> log4j.appender.RollingFile.File=c:/customs.log
>      > >
>      > >
>      > > c:\customs.log ?
>      > >
>      >
>
>

Reply via email to