Joakim Olsson napisał(a):
I have had this problem since switching to Geronimo from a clean
Tomcat-environment too.
The problem is that Geronimo uses a newer version of CGLIB than iBatis is
supporting.
I solved the problem by putting the correct version of cglib.jar in my
webapps lib-dir but I
Joakim Olsson napisaÅ(a):
I have had this problem since switching to Geronimo from a clean
Tomcat-environment too.
The problem is that Geronimo uses a newer version of CGLIB than iBatis
is
supporting.
I solved the problem by putting the correct version of cglib.jar in my
webapps lib-dir
Joakim Olsson napisał(a):
Joakim Olsson napisał(a):
I have had this problem since switching to Geronimo from a clean
Tomcat-environment too.
The problem is that Geronimo uses a newer version of CGLIB than iBatis
is
supporting.
I solved the problem by putting the correct version of cglib.jar
I agree that the SQL returns multiple rows for each instance of a
contact, but isn't that what the groupby property is supposed to handle?
From the iBatis SQLMaps documentation:
The resultMap element also supports the attribute groupBy. The groupBy
attribute is used to specify a list
of
Yes, that could be clearer - the difference here is that the examples
are all 1 - M - N, but what you are trying to do is 1 - M*N.
It's not going to work, you'll need to write a rowhandler, or find
some other solution.
Larry
On 1/15/07, Ben Schmidt [EMAIL PROTECTED] wrote:
I agree that the
OK, Thanks for the help.
Ben.
Larry Meadors wrote:
Yes, that could be clearer - the difference here is that the examples
are all 1 - M - N, but what you are trying to do is 1 - M*N.
It's not going to work, you'll need to write a rowhandler, or find
some other solution.
Larry
On 1/15/07,
No problem, it just seems non-intuitive.
While driver has to throw batch update exception as it cannot know if that
should be a bailout error or not (and there are different versions of
drivers), iBatis could decide differently, i.e. if there are some failed
statements in a batch to just return
But if that is so, why do we have:
int[] rowCounts = be.getBatchUpdateException().getUpdateCounts();
where be is BatchException
My understanding is this will give all the wrong and good statements in
a batch, will it not? (which means all the remaining statements in the batch
will be attempted
