Great, it works!!!
Following your suggestion I've configured the Log Detail with the string:
com.ibatis.sqlmap.engine.impl.SqlMapClientImpl=all=enabled:java.sql.Connection=all=enabled:java.sql.PreparedStatement=all=enabled:java.sql.ResultSet=all=enabled
And now I've got the logs on the "trace.lo
Thank you very much for the precious information ... I could have spent a
couple of months to spot it by myself ;-) .
Regards
Max
>-- Messaggio Originale --
>Reply-To: user-java@ibatis.apache.org
>Date: Thu, 11 Aug 2005 12:15:20 -0500
>From: Jeff Butler <[EMAIL PROTECTED]>
>To: user-java@ibatis.a
Hi Prashanth,
I've tried to remove all "unnecessary" lines from the log4j.properties file
but nothing changed.
At the moment this is my configuration:
*** LIBs in project classpath ***
- commons-logging-api.jar
- commons-logging.jar
- log4j.1.2.11.jar
*** log4j.properties file ***
# Global loggin
Sorry for my ignorance, what is the "log4j.PropertyConfigurator.configure",
I only have the log4j.properties file located in my "WEB-INF\classes" project
directory.
How\Where should I use "log4j.PropertyConfigurator.configure" ?
thanks in advance
Max
>-- Messaggio Originale --
>Reply-To: user-j
this is my "log4j.properties" file placed in the "WEB-INF\Classes" project
directory:
-
# Global logging configuration
log4j.rootLogger=DEBUG, stdout, DAILY_FILE
# for ibatis
# SqlMap logging configuration...
log4j.l
Hi,
I had "commons-logging.jar" and "log4j-1.2.8.jar" in my project classPath
and didn't see logs from iBatis.
I tried to add even "commons-logging-api.jar" to the classPath but nothing
changed...
I'm starting thinking it is Rational (WebSphere Studio) having some problems
in showing logs.
Just fo
Hi, I think a very simple question: how to log in Log4J with iBatis 2.1.5?
I'm using IBM Rational Software Development Platform Version: 6.0.0.1 and
iBatis 2.1.5 and I've configured log4j.properties file this way:
---
My situation is: iBatis framework using an existing WebSphere DataSource.
We were not succesful in defining the Datasource inside the iBatis
SqlMap-config.XML
file cause the datasource itself needs username and password being specified
at run-time by the application using it. Furthermore we do N
Brandon, you are right but the customer do not want to store username & password
inside the XML file where the JNDI datasource is defined... so they require
the application to pass these values run time...
Probably I've found a work-around:
I leave unchanged the xml file for Ibatis:
transaction
The JNDI Datasource is configured on the WebSphere AS without username and
password, so I need to pass them. I know that the right way to reference
an existing JNDI datasource is the following one:
transactionManager type="JDBC"
dataSource type="JNDI"
property name="DataSource" value="
10 matches
Mail list logo