Is there a way to allow connection retries (via a user configured
parameter) while using the SimpleDataSource tx manager?
proxis.be/com I think, maybe the're ordering directly from Manning. I
don't think they order from Amazon :-)
Niels
From: Clinton Begin [mailto:[EMAIL PROTECTED]
Sent: zaterdag 17 februari 2007 20:46
To: user-java@ibatis.apache.org
Subject: Re: iBATIS in Ac
There are instructions for building a new version of the plugin in the
eclipse help for Abator.
Jeff Butler
On 2/17/07, Brad Balmer <[EMAIL PROTECTED]> wrote:
I've checked out and compiled the latest svn version. Is there a way to
get this into the eclipse plugin?
--
Brad Balmer
[EMAIL PROT
I am responding on the dev list too :-) There's two things going on:
1) An automated build numbering -- and any build numbering for that
matter -- isn't needed for official distributions. All you need is the
X.Y.Z scheme where X=major,Y=minor,Z=revision versions.
2) You are actually using the
The build number is very important...it's the only automated serial number
we have.
It doesn't matter to me where that number comes from. SVN rev number is an
excellent suggestion. But I don't want to downplay the importance of an
automated serial number.
I agree with Jeff's point, that there
Did you order it from Manning directly or Amazon? Let me know and I'll
give them a boot. ;-)
Hopefully it means they're sold out!
clinton
On 2/17/07, Niels Beekman <[EMAIL PROTECTED]> wrote:
All,
Ordered the book about a month ago, but got nothing :(
I received an email last Friday from
I've checked out and compiled the latest svn version. Is there a way to get
this into the eclipse plugin?
--
Brad Balmer
[EMAIL PROTECTED]
All,
Ordered the book about a month ago, but got nothing :(
I received an email last Friday from the shop which (translated) states the
following:
"Ibatis in Action (Begin, Clinton), code 1932394826
Despite our continuous efforts we did not receive a shipment from our supplier,
nor did we rece
I agree that the build number is useless. Apache policy says that there are
not different versions of a release. So we really shouldn't have 2.3.0-638and
2.3.0-677, we only have one 2.3.0 release (we've only broken that rule one
time that I remember).
I kind of like the way Derby does it. The
OK, as I am digging through this, I see that we have this "build
number" thing on the download.
I am wondering if we should change it to make that number have some more value.
What I mean is: "What does 'ibatis-2.3.0.677.zip' really tell me about
the build?"
677 is just an arbitrary magic numbe
Thanks Brandon (and Jeff),
I'm definitely going to try that. I thought I was confined to the types
declared in the JdbcTypeRegistry class. In that class there is a
"ORACLECURSOR" declared - which I can pass onto a stored
function/procedure as JDBCType when I want to do something with REF
Cursors.
11 matches
Mail list logo