Not working with derby 10.3.1.4

Hi, I tried to upgrade to derby 10.3.1.4 but I get strange error messages that I didn't get with derby 10.2.2.0. I use ibatis-2.3.0.677. Any ideas? Zsolt com.intland.codebeamer.persistence.util.PersistenceException: com.ibatis.common.jdbc.exception.NestedSQLException: --- The error

Log4j again... sorry

Hi everyone, Sorry to bother you with that subject again, but I can not get any log, wether from ibatis or from the java.sql BUT I do have spring logs and logs from my webapp code... My code uses commons-logging AND log4j (I use a log4j.properties file) I have read the documentation and I

Re: Log4j again... sorry

Try this: log4j.logger.java.sql=DEBUG Larry On 8/31/07, Gilles Schlienger [EMAIL PROTECTED] wrote: Hi everyone, Sorry to bother you with that subject again, but I can not get any log, wether from ibatis or from the java.sql BUT I do have spring logs and logs from my webapp code... My

Re : Log4j again... sorry

Thanks for your email, Still no luck though... No log happens. But I can see the SQL request in my MYSQL database logs... Regards Gilles - Message d'origine De : Larry Meadors [EMAIL PROTECTED] À : user-java@ibatis.apache.org Envoyé le : Vendredi, 31 Août 2007, 15h09mn 37s Objet : Re:

Re: Re : Re : Log4j again... sorry

Make sure you have log4j in your webapp classpath and then add the following to your log4j.properties file in the root of your WEB-INF/classes directory. # Rules reminder: # DEBUG INFO WARN ERROR FATAL # Global logging configuration log4j.rootLogger=WARN, stdout # SqlMap logging

Re: Re : Re : Log4j again... sorry

Additionally you could try adding commons-logging to your webapp classpath and then place the following contents into a WEB-INF/commons- logging.properties file: org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger Brandon On 8/31/07, Brandon Goodin [EMAIL PROTECTED]

Re : Re : Log4j again... sorry

Something weird: I created a servlet listener, and added it in my web.xml file. In this listener I call: com.ibatis.common.logging.LogFactory.selectLog4JLogging(); Still I get no log in the console or anywhere else... I use Ibatis with Spring using Spring's Template. Regards Gilles -

Re: Not working with derby 10.3.1.4

What is your column type in derby? Apparently the JDBC driver is reporting it as a type of UNKNOWN. Brandon On 8/31/07, Zsolt Koppany [EMAIL PROTECTED] wrote: Hi, I tried to upgrade to derby 10.3.1.4 but I get strange error messages that I didn't get with derby 10.2.2.0. I use

Re: PaginatedList

There is no replacement needed. The SqlMap contains a method called queryForList(String id, Object parameter, int skip, int max). See the javadoc below. This will accomplish what you want. We've decided that the PaginatedList is outside the scope of iBATIS and oft abused. That is why we deprecated

Re: Re : Re : Re : Log4j again... sorry

iBATIS logs almost everything to java.sql logs. The only thing you'll see in com.ibatis is caching information. Sounds like you've got it working. Jeff Butler On 8/31/07, Gilles Schlienger [EMAIL PROTECTED] wrote: Tried that but still no luck. java.sql logs work fine though But still

Re : Re : Re : Re : Log4j again... sorry

Thanks Jeff Gilles - Message d'origine De : Jeff Butler [EMAIL PROTECTED] À : user-java@ibatis.apache.org Envoyé le : Vendredi, 31 Août 2007, 17h41mn 19s Objet : Re: Re : Re : Re : Log4j again... sorry iBATIS logs almost everything to java.sql logs. The only thing you'll see in

JavaBean and Map parameters

Hello all, what should I prefer, this: return getSqlMapClientTemplate().queryForList(listEvaluationPlans, new Object() { long getPersonId() { return personId; } String getLang() { return lang; } }); or this: final MapString, Object params = new HashMapString, Object(2);