Hey Clinton,
You've got volunteers coming out of the woodwork ;-)
-Original Message-
From: Martin Ellis [mailto:ellis@gmail.com]
Sent: Wednesday, April 07, 2010 11:43 AM
To: user-java@ibatis.apache.org
Subject: Re: SqlSession.close() without committing
One thing I'd have liked to see
I am not even sure this is worth two-cents but:
What (for lack of a better word) confuses me is the phrase "generate a
jar file that will pull out some of the data..."
>From what I can decipher, I would handle it like this. As you say, your
data model itself is identical but the second applicatio
iBatis relies on logging of the underlying JDBC statements which is documented
(somewhere).
We use the following settings in our log4j.xml file, adjust to your liking:
-Original Message-
From: Trenton D. Adams [mailto:tre...@athabascau.ca]
Sent:
Agreed on both points below... but am curious to the community at
large... has anyone come up with something useful to do on a database
exception other than apologize to the user? This might be a good forum
to share.
From: Clinton Begin [mailto:clinton.be...@gmail.com]
Sent: Thursday, Decembe
I would guess this is more applet related than iBatis. i.e. Do any of
the applet JARs contain your SQLMapConfig file? Or are you assuming that
it has access to the filesystem (because an applet does not have access
to the filesystem unless you explicitly configure it so).
This is just my first gu
Even if it is not an "issue", I think it is usually good form to include
your solution to a problem when you post. Not just "hey, *I* solved
*my* problem, so good luck with yours".
From: Poitras Christian [mailto:christian.poit...@ircm.qc.ca]
Sent: Thursday, November 19, 2009 7:38 AM
To: 'use
Welcome to my world. I recently trudged down this road myself and found
the help/warnings in this area lacking (readers: PLEASE feel free to
point out web documentation to refute me on that statement!).
As there are six items in your "stack" (ibatis + BasicDataSource +
Spring DAO + DataSourceTran
Unfortunately I cannot dive into the many details of iBatis and
transactions but here is how I would answer your question:
1) You almost assuredly want to create a single static SqlMapClient to
service many threads.
2) I am pretty sure that iBatis uses ThreadLocal to isolate transactions
from dif
Since I have some time over lunch:
1) I agree with Larry's reply below
2) At the risk of embarrassing myself on this forum, see below for my
reply to your comments and questions:
[your-code-sample-was-here]
[your-comments-were-here]
I've been wrestling with this problem for a long time and right n
Are they simply the other connections in the connection pool?
-Original Message-
From: Jim Borland [mailto:jborl...@calpoly.edu]
Sent: Saturday, October 17, 2009 10:04 PM
To: user-java@ibatis.apache.org
Subject: iBatis - Connections to PostgreSQL Not Closing
I have a Java application in
I needed to use the following technique to solve a similar challenge
recently and, though seemingly obvious, I found no references on the
web. I cannot give it a full stamp of approval but it is working for us
so far:
1) Extend the iBatis class SimpleDataSourceFactory:
public class YourClass
Depending on the DataSource you are using, you might be able extend that
class to override a particular property/method call. Can you describe
your iBatis configuration? (i.e. sqlMap.xml, are you using Spring, what
datasource are you using)
From: Ejaz X Mohammed [mailto:ejaz.moham...@jpmorgan.
I may be overstepping my overall iBatis knowledge but here is my
understanding:
1) The workhorse of iBatis is the SqlMapClient object which is
configured through an iBatis XML file (and you may be using Spring
configuration as well, sounds like it).
2) The XML file defines one, and only one, dataso
(from the way you wrote your question)
Assumption #1: You have N web-applications that each have their own
Spring 'applicationContext.xml' file.
Assumption #2: Until now, each configLocation property of the
sqlMapClient bean has been identical.
If Assumptions #1 and #2 are correct, then you have a
I have not looked at the source you're referring to but did you
"deprecate" the behavior or "remove" the behavior. I am not sure if you
have a standing policy on things like this but here is my opinion:
I understand the need to "clean things up" in a major release but I tend
to favor "formal depr
15 matches
Mail list logo
