Interesting Logger Bug

Hi, I happened to notice this pattern of logging that Ibatis was defecting on.I am surprised it hasnt been mentioned earlier. Anyways, this is the situation, Say you are calling a procedure that returns a ref-cursor. Your resultMap for the refcursor is something like this

Dynamic result map

Hi, I have a refcursor returned out of my procedure. The data that comes out of it is like this col1 has either value 1 or value 2 and there are other column data I wanna put data mapped to col1=value1 in a object and col1=value2 in a object. Is there a way to do this with Ibatis. Regards Su

Re: iBatis Tomcat log4j IntelliJ IDEA

Hi, in the log4j config file you have to configure the java.sql logger to debug Giovanni On Thu, Jul 17, 2008 at 8:34 PM, Tokajac <[EMAIL PROTECTED]> wrote: > > I'm working with Tomcat and Struts framework. > > I want to log SQL queries (SELECT, INSERT, UPDATE...) with log4j. > I configured log4j

iBatis Tomcat log4j IntelliJ IDEA

I'm working with Tomcat and Struts framework. I want to log SQL queries (SELECT, INSERT, UPDATE...) with log4j. I configured log4j, it works fine for other logs. I don't know how can I get the queries that are executed? Regards -- View this message in context: http://www.nabble.com/iBatis-T

Re: iBATIS lock timeouts

I've removed all thread throttling from iBATIS. It was causing a great deal of confusing and people complained about performance. The thread throttling was quite advanced and had a lot of scalability testing behind it, it was able to hide a lot of problems like this. The downside is that you no

iBATIS lock timeouts

Production Environment: We are using a JNDI datasource in WS 6.1 (fixpack 15) to connect to a DB2 9.1 (fixpack 2) database on a separate cluster. We recently upgraded our Java version of iBATIS after falling way behind from 2.0.9 to the latest release 2.3.1. The dev and test environment showed no

Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production

Absolutely. The only reason that version 2.x has been so quiet lately is that I've been focused on version 3.0. Initially I didn't think a compatibility kit would be possible, but it's looking more and more like it will be. I'm nearly finished it to a point where I can make a release of an iBATI

[ARTICLE] iBATIS, Hibernate, and JPA: Which is right for you? -- JavaWorld

http://www.javaworld.com/javaworld/jw-07-2008/jw-07-orm-comparison.html

Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production

As a new user to iBatis (we just began using it two weeks ago at my company!), I just want to give you guys a big thanks for your work on the framework. It's made it a lot more comfortable to know that iBatis is under active development, and has a lively community around it. Keep up the good work!

Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production

No. The Spring integration is using internals of iBATIS which are not meant to be publicly consumed. We're not going to stop evolving our code just to keep compatible with 3rd party frameworks that reach into the guts of iBATIS. Waiting for 2.4 would just delay the inevitable. The solutions is:

RE: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production

Upgrading to newer version of iBatis is becoming more and more complicated. So now we will have to wait for new version of spring in order to get new version of iBatis? Isn't it better just to revert all those changes back on branch 2.3.x and start new branch with those changes (2.4 or long waiti

Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production

Wow... K, it's looking more and more like we just need to update the Spring integration. I'm not willing to roll back all of the simplifications we made to the software. We got rid of a lot of internal cruft that just made the code harder to read and didn't serve a purpose. I'll see what I

Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production

That's a fair point -- for maven users. :-) I'll see if Brandon is willing to commit to that. Clinton On Thu, Jul 17, 2008 at 4:16 AM, Iwao AVE! <[EMAIL PROTECTED]> wrote: > Hi Clinton, > > I understand you need more testers, but then, why don't you publish these > betas in the maven repositor

Bug with complex property in result map?

Hi there, I noticed that after upgrading to newer version of iBatis, some of the functionality that used to work with iBatis 2.0.9 stopped working. Namely, the problem occurred in case when there is complex property in result map. Here is the simple test case: - Sql map:

Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production

Hi Clinton, I understand you need more testers, but then, why don't you publish these betas in the maven repository? It would increase the number of testers (1 at least = me). Sorry if this topic has been discussed already. Regards, Iwao

Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production

Hi, there. I'm developing a spring 2.5 web based application. I tried upgrading from iBatis 2.3.0 to iBatis 2.3.3, but I get the following exception: nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'whatever' defined in class path resour