You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-java@ibatis.apache.org by Clinton Begin <cl...@gmail.com> on 2006/08/13 11:27:59 UTC
Multiple Result Set Support complete, 2.2.0 will fly within a week
Hi all,
The good news is that I'm on vacation. The bad news is that I spent the
last 6 hours watching the first two extended edition Lord of the Rings
movies while implementing the Multiple ResultSet support.
That was the last "required" feature for 2.2.0 to go out, so I'm thinking it
should be no more than a week before we see it deployed. There may be a few
more things to go, but certainly not of that size.
Speaking of major features, I think that must be darn near the entire JDBC
API we've wrapped with iBATIS, and iBATIS 2.0 is showing its age. It's been
in production for almost 2.5 years, which is great life to get out of any
software.
That said, with 2.2.0 out, I fully expect the next major version to be 3.0.
I recommend 2.0 enter an extended maintenance mode, whereby we only fix bugs
and make minor improvements to existing features.
I don't suggest we attempt to leverage Java 5/6 or JDBC 3/4 features in
iBATIS 2.x.
Instead, I'm thinking iBATIS 3.0 should cover all of those, with 2.x still
supported until JDK 1.4 drops to well below 15% usage (it's currently at
around 80%).
Thoughts welcome.
Cheers,
Clinton
Re: Re: Multiple Result Set Support complete, 2.2.0 will fly within a week
Posted by Clinton Begin <cl...@gmail.com>.
Not really.
But here's a quick personal take:
* Turn invalid the JDBC 4.0 "Ease of Development API" by kicking the
living snot out of it.
* Make laughable the Microsoft DLINQ API.
* Bring to the enterprise the ways of Ruby without ActiveRecord.
* Remain a good neighbour to Spring, Hibernate and our other friends in
the open source community.
Cheers, ;-)
Clinton
PS: Note the smiley.
On 8/14/06, Jerome Gagner <ph...@gmail.com> wrote:
>
> Is there a road map for 3.0 yet? It'd be cool to see :)
> On 8/14/06, Gwyn Evans <gw...@gmail.com> wrote:
> > On 13/08/06, Clinton Begin <cl...@gmail.com> wrote:
> > >
> > > The good news is that I'm on vacation. The bad news is that I spent
> the
> > > last 6 hours watching the first two extended edition Lord of the Rings
> > > movies while implementing the Multiple ResultSet support.
> >
> > As a result, to enable it, just set the attribute "RingBearer" to true
> > in your sqlmap...
> >
> > > That said, with 2.2.0 out, I fully expect the next major version to be
> 3.0.
> >
> > but, taking a lead from Peter Jackson, versions 3.1 & 3.2 will be
> > developed in parallel with it...
> >
> > :-)
> >
> > /Gwyn
> > --
> > Download Wicket 1.2.1 now! - http://wicketframework.org
> >
>
Re: Re: Multiple Result Set Support complete, 2.2.0 will fly within a week
Posted by Clinton Begin <cl...@gmail.com>.
Not really.
But here's a quick personal take:
* Turn invalid the JDBC 4.0 "Ease of Development API" by kicking the
living snot out of it.
* Make laughable the Microsoft DLINQ API.
* Bring to the enterprise the ways of Ruby without ActiveRecord.
* Remain a good neighbour to Spring, Hibernate and our other friends in
the open source community.
Cheers, ;-)
Clinton
PS: Note the smiley.
On 8/14/06, Jerome Gagner <ph...@gmail.com> wrote:
>
> Is there a road map for 3.0 yet? It'd be cool to see :)
> On 8/14/06, Gwyn Evans <gw...@gmail.com> wrote:
> > On 13/08/06, Clinton Begin <cl...@gmail.com> wrote:
> > >
> > > The good news is that I'm on vacation. The bad news is that I spent
> the
> > > last 6 hours watching the first two extended edition Lord of the Rings
> > > movies while implementing the Multiple ResultSet support.
> >
> > As a result, to enable it, just set the attribute "RingBearer" to true
> > in your sqlmap...
> >
> > > That said, with 2.2.0 out, I fully expect the next major version to be
> 3.0.
> >
> > but, taking a lead from Peter Jackson, versions 3.1 & 3.2 will be
> > developed in parallel with it...
> >
> > :-)
> >
> > /Gwyn
> > --
> > Download Wicket 1.2.1 now! - http://wicketframework.org
> >
>
Re: Re: Multiple Result Set Support complete, 2.2.0 will fly within a week
Posted by Jerome Gagner <ph...@gmail.com>.
Is there a road map for 3.0 yet? It'd be cool to see :)
On 8/14/06, Gwyn Evans <gw...@gmail.com> wrote:
> On 13/08/06, Clinton Begin <cl...@gmail.com> wrote:
> >
> > The good news is that I'm on vacation. The bad news is that I spent the
> > last 6 hours watching the first two extended edition Lord of the Rings
> > movies while implementing the Multiple ResultSet support.
>
> As a result, to enable it, just set the attribute "RingBearer" to true
> in your sqlmap...
>
> > That said, with 2.2.0 out, I fully expect the next major version to be 3.0.
>
> but, taking a lead from Peter Jackson, versions 3.1 & 3.2 will be
> developed in parallel with it...
>
> :-)
>
> /Gwyn
> --
> Download Wicket 1.2.1 now! - http://wicketframework.org
>
Re: Multiple Result Set Support complete, 2.2.0 will fly within a week
Posted by Gwyn Evans <gw...@gmail.com>.
On 13/08/06, Clinton Begin <cl...@gmail.com> wrote:
>
> The good news is that I'm on vacation. The bad news is that I spent the
> last 6 hours watching the first two extended edition Lord of the Rings
> movies while implementing the Multiple ResultSet support.
As a result, to enable it, just set the attribute "RingBearer" to true
in your sqlmap...
> That said, with 2.2.0 out, I fully expect the next major version to be 3.0.
but, taking a lead from Peter Jackson, versions 3.1 & 3.2 will be
developed in parallel with it...
:-)
/Gwyn
--
Download Wicket 1.2.1 now! - http://wicketframework.org
Re: Multiple Result Set Support complete, 2.2.0 will fly within a week
Posted by Clinton Begin <cl...@gmail.com>.
That's a great idea. Let's do an infomercial with Chuck Norris too.
Cheers, :-)
Clinton
On 8/14/06, Larry Meadors <lm...@apache.org> wrote:
>
> ..or take a cue from commercial software vendors, and release them all
> today (available for pre-order, that is).
>
> Larry
>
>
>
> On 8/14/06, Jeff Butler <je...@gmail.com> wrote:
> >
> > LOL - we should do MDD - then we could just draw a pretty picture and
> > there would be NO development time. :)
> >
> > Jeff
> >
> >
> > On 8/14/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> > >
> > > >> don't make any grand pronouncements about 2.2.0
> > >
> > > Good call Jeff. Sorry for sounding extreme. We'll definitely be
> > > supporting 2.2.0 for a long time, including new features that make too
> > > much sense to ignore.
> > >
> > > At the end of the day, we'll always do what makes sense. Our
> > > investors don't mind. ;-)
> > >
> > > >> we don't have any idea how long it will take to develop [iBATIS 3.0
> > > ]
> > >
> > > I do! According to the latest hype:
> > >
> > > * iBATIS 3.0 will take 4 weeks to write.
> > > * iBATIS.NET <http://ibatis.net/> 3.0 will take 2 weeks to write.
> > > * RBatis 3.0 will take 3.5 hours.
> > >
> > > Cheers, ;-)
> > >
> > > Clinton
> > >
> > >
> > > On 8/14/06, Jeff Butler <jeffgbutler@gmail.com > wrote:
> > > >
> > > > I agree that no new JDK/JDBC features should be put into iBATIS 2.x.
> > > > But I'd suggest that we don't make any grand pronouncements about
> > > > 2.2.0 being the last release except for maintenance. It's hard to
> > > > predict what the future holds and we have no idea when iBATIS 3.0might be released. There have been no substantive discussions about iBATIS
> > > > 3.0 anywhere and we don't have any idea how long it will take to
> > > > develop such a thing.
> > > >
> > > > So I'd just say that we plan to keep iBATIS 2.x using JDK 1.4. I
> > > > can't see any value to declaring some kind of extended maintenance mode for
> > > > iBATIS 2.x - let's wait to do that until iBATIS 3.0 is somewhat
> > > > close to a real product.
> > > >
> > > > Jeff Butler
> > > >
> > > >
> > > > On 8/13/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > The good news is that I'm on vacation. The bad news is that I
> > > > > spent the last 6 hours watching the first two extended edition Lord of the
> > > > > Rings movies while implementing the Multiple ResultSet support.
> > > > >
> > > > > That was the last "required" feature for 2.2.0 to go out, so I'm
> > > > > thinking it should be no more than a week before we see it deployed. There
> > > > > may be a few more things to go, but certainly not of that size.
> > > > >
> > > > > Speaking of major features, I think that must be darn near the
> > > > > entire JDBC API we've wrapped with iBATIS, and iBATIS 2.0 is
> > > > > showing its age. It's been in production for almost 2.5 years,
> > > > > which is great life to get out of any software.
> > > > >
> > > > > That said, with 2.2.0 out, I fully expect the next major version
> > > > > to be 3.0. I recommend 2.0 enter an extended maintenance mode,
> > > > > whereby we only fix bugs and make minor improvements to existing features.
> > > > >
> > > > > I don't suggest we attempt to leverage Java 5/6 or JDBC 3/4
> > > > > features in iBATIS 2.x.
> > > > >
> > > > > Instead, I'm thinking iBATIS 3.0 should cover all of those, with
> > > > > 2.x still supported until JDK 1.4 drops to well below 15% usage
> > > > > (it's currently at around 80%).
> > > > >
> > > > > Thoughts welcome.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Clinton
> > > > >
> > > >
> > > >
> > >
> >
>
Re: Multiple Result Set Support complete, 2.2.0 will fly within a week
Posted by Larry Meadors <lm...@apache.org>.
..or take a cue from commercial software vendors, and release them all today
(available for pre-order, that is).
Larry
On 8/14/06, Jeff Butler <je...@gmail.com> wrote:
>
> LOL - we should do MDD - then we could just draw a pretty picture and
> there would be NO development time. :)
>
> Jeff
>
>
> On 8/14/06, Clinton Begin <cl...@gmail.com> wrote:
> >
> > >> don't make any grand pronouncements about 2.2.0
> >
> > Good call Jeff. Sorry for sounding extreme. We'll definitely be
> > supporting 2.2.0 for a long time, including new features that make too
> > much sense to ignore.
> >
> > At the end of the day, we'll always do what makes sense. Our investors
> > don't mind. ;-)
> >
> > >> we don't have any idea how long it will take to develop [iBATIS 3.0]
> >
> > I do! According to the latest hype:
> >
> > * iBATIS 3.0 will take 4 weeks to write.
> > * iBATIS.NET <http://ibatis.net/> 3.0 will take 2 weeks to write.
> > * RBatis 3.0 will take 3.5 hours.
> >
> > Cheers, ;-)
> >
> > Clinton
> >
> >
> > On 8/14/06, Jeff Butler <jeffgbutler@gmail.com > wrote:
> > >
> > > I agree that no new JDK/JDBC features should be put into iBATIS 2.x.
> > > But I'd suggest that we don't make any grand pronouncements about
> > > 2.2.0 being the last release except for maintenance. It's hard to
> > > predict what the future holds and we have no idea when iBATIS 3.0might be released. There have been no substantive discussions about iBATIS
> > > 3.0 anywhere and we don't have any idea how long it will take to
> > > develop such a thing.
> > >
> > > So I'd just say that we plan to keep iBATIS 2.x using JDK 1.4. I
> > > can't see any value to declaring some kind of extended maintenance mode for
> > > iBATIS 2.x - let's wait to do that until iBATIS 3.0 is somewhat close
> > > to a real product.
> > >
> > > Jeff Butler
> > >
> > >
> > > On 8/13/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > The good news is that I'm on vacation. The bad news is that I spent
> > > > the last 6 hours watching the first two extended edition Lord of the Rings
> > > > movies while implementing the Multiple ResultSet support.
> > > >
> > > > That was the last "required" feature for 2.2.0 to go out, so I'm
> > > > thinking it should be no more than a week before we see it deployed. There
> > > > may be a few more things to go, but certainly not of that size.
> > > >
> > > > Speaking of major features, I think that must be darn near the
> > > > entire JDBC API we've wrapped with iBATIS, and iBATIS 2.0 is showing
> > > > its age. It's been in production for almost 2.5 years, which is
> > > > great life to get out of any software.
> > > >
> > > > That said, with 2.2.0 out, I fully expect the next major version to
> > > > be 3.0. I recommend 2.0 enter an extended maintenance mode, whereby
> > > > we only fix bugs and make minor improvements to existing features.
> > > >
> > > > I don't suggest we attempt to leverage Java 5/6 or JDBC 3/4 features
> > > > in iBATIS 2.x.
> > > >
> > > > Instead, I'm thinking iBATIS 3.0 should cover all of those, with 2.xstill supported until JDK
> > > > 1.4 drops to well below 15% usage (it's currently at around 80%).
> > > >
> > > > Thoughts welcome.
> > > >
> > > > Cheers,
> > > >
> > > > Clinton
> > > >
> > >
> > >
> >
>
Re: Multiple Result Set Support complete, 2.2.0 will fly within a week
Posted by Jeff Butler <je...@gmail.com>.
LOL - we should do MDD - then we could just draw a pretty picture and there
would be NO development time. :)
Jeff
On 8/14/06, Clinton Begin <cl...@gmail.com> wrote:
>
> >> don't make any grand pronouncements about 2.2.0
>
> Good call Jeff. Sorry for sounding extreme. We'll definitely be
> supporting 2.2.0 for a long time, including new features that make too
> much sense to ignore.
>
> At the end of the day, we'll always do what makes sense. Our investors
> don't mind. ;-)
>
> >> we don't have any idea how long it will take to develop [iBATIS 3.0]
>
> I do! According to the latest hype:
>
> * iBATIS 3.0 will take 4 weeks to write.
> * iBATIS.NET <http://ibatis.net/> 3.0 will take 2 weeks to write.
> * RBatis 3.0 will take 3.5 hours.
>
> Cheers, ;-)
>
> Clinton
>
>
> On 8/14/06, Jeff Butler <je...@gmail.com> wrote:
> >
> > I agree that no new JDK/JDBC features should be put into iBATIS 2.x.
> > But I'd suggest that we don't make any grand pronouncements about 2.2.0being the last release except for maintenance. It's hard to predict what
> > the future holds and we have no idea when iBATIS 3.0 might be released.
> > There have been no substantive discussions about iBATIS 3.0 anywhere and
> > we don't have any idea how long it will take to develop such a thing.
> >
> > So I'd just say that we plan to keep iBATIS 2.x using JDK 1.4. I can't
> > see any value to declaring some kind of extended maintenance mode for iBATIS
> > 2.x - let's wait to do that until iBATIS 3.0 is somewhat close to a real
> > product.
> >
> > Jeff Butler
> >
> >
> > On 8/13/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> > >
> > > Hi all,
> > >
> > > The good news is that I'm on vacation. The bad news is that I spent
> > > the last 6 hours watching the first two extended edition Lord of the Rings
> > > movies while implementing the Multiple ResultSet support.
> > >
> > > That was the last "required" feature for 2.2.0 to go out, so I'm
> > > thinking it should be no more than a week before we see it deployed. There
> > > may be a few more things to go, but certainly not of that size.
> > >
> > > Speaking of major features, I think that must be darn near the entire
> > > JDBC API we've wrapped with iBATIS, and iBATIS 2.0 is showing its
> > > age. It's been in production for almost 2.5 years, which is great
> > > life to get out of any software.
> > >
> > > That said, with 2.2.0 out, I fully expect the next major version to be
> > > 3.0. I recommend 2.0 enter an extended maintenance mode, whereby we
> > > only fix bugs and make minor improvements to existing features.
> > >
> > > I don't suggest we attempt to leverage Java 5/6 or JDBC 3/4 features
> > > in iBATIS 2.x.
> > >
> > > Instead, I'm thinking iBATIS 3.0 should cover all of those, with 2.xstill supported until JDK
> > > 1.4 drops to well below 15% usage (it's currently at around 80%).
> > >
> > > Thoughts welcome.
> > >
> > > Cheers,
> > >
> > > Clinton
> > >
> >
> >
>
Re: Multiple Result Set Support complete, 2.2.0 will fly within a week
Posted by Clinton Begin <cl...@gmail.com>.
>> don't make any grand pronouncements about 2.2.0
Good call Jeff. Sorry for sounding extreme. We'll definitely be supporting
2.2.0 for a long time, including new features that make too much sense to
ignore.
At the end of the day, we'll always do what makes sense. Our investors
don't mind. ;-)
>> we don't have any idea how long it will take to develop [iBATIS 3.0]
I do! According to the latest hype:
* iBATIS 3.0 will take 4 weeks to write.
* iBATIS.NET 3.0 will take 2 weeks to write.
* RBatis 3.0 will take 3.5 hours.
Cheers, ;-)
Clinton
On 8/14/06, Jeff Butler <je...@gmail.com> wrote:
>
> I agree that no new JDK/JDBC features should be put into iBATIS 2.x. But
> I'd suggest that we don't make any grand pronouncements about 2.2.0 being
> the last release except for maintenance. It's hard to predict what the
> future holds and we have no idea when iBATIS 3.0 might be released. There
> have been no substantive discussions about iBATIS 3.0 anywhere and we
> don't have any idea how long it will take to develop such a thing.
>
> So I'd just say that we plan to keep iBATIS 2.x using JDK 1.4. I can't
> see any value to declaring some kind of extended maintenance mode for iBATIS
> 2.x - let's wait to do that until iBATIS 3.0 is somewhat close to a real
> product.
>
> Jeff Butler
>
>
> On 8/13/06, Clinton Begin <cl...@gmail.com> wrote:
> >
> > Hi all,
> >
> > The good news is that I'm on vacation. The bad news is that I spent the
> > last 6 hours watching the first two extended edition Lord of the Rings
> > movies while implementing the Multiple ResultSet support.
> >
> > That was the last "required" feature for 2.2.0 to go out, so I'm
> > thinking it should be no more than a week before we see it deployed. There
> > may be a few more things to go, but certainly not of that size.
> >
> > Speaking of major features, I think that must be darn near the entire
> > JDBC API we've wrapped with iBATIS, and iBATIS 2.0 is showing its age.
> > It's been in production for almost 2.5 years, which is great life to get
> > out of any software.
> >
> > That said, with 2.2.0 out, I fully expect the next major version to be
> > 3.0. I recommend 2.0 enter an extended maintenance mode, whereby we
> > only fix bugs and make minor improvements to existing features.
> >
> > I don't suggest we attempt to leverage Java 5/6 or JDBC 3/4 features in
> > iBATIS 2.x.
> >
> > Instead, I'm thinking iBATIS 3.0 should cover all of those, with 2.xstill supported until JDK
> > 1.4 drops to well below 15% usage (it's currently at around 80%).
> >
> > Thoughts welcome.
> >
> > Cheers,
> >
> > Clinton
> >
>
>
Re: Multiple Result Set Support complete, 2.2.0 will fly within a week
Posted by Jeff Butler <je...@gmail.com>.
I agree that no new JDK/JDBC features should be put into iBATIS 2.x. But
I'd suggest that we don't make any grand pronouncements about 2.2.0 being
the last release except for maintenance. It's hard to predict what the
future holds and we have no idea when iBATIS 3.0 might be released. There
have been no substantive discussions about iBATIS 3.0 anywhere and we don't
have any idea how long it will take to develop such a thing.
So I'd just say that we plan to keep iBATIS 2.x using JDK 1.4. I can't see
any value to declaring some kind of extended maintenance mode for
iBATIS 2.x- let's wait to do that until iBATIS
3.0 is somewhat close to a real product.
Jeff Butler
On 8/13/06, Clinton Begin <cl...@gmail.com> wrote:
>
> Hi all,
>
> The good news is that I'm on vacation. The bad news is that I spent the
> last 6 hours watching the first two extended edition Lord of the Rings
> movies while implementing the Multiple ResultSet support.
>
> That was the last "required" feature for 2.2.0 to go out, so I'm thinking
> it should be no more than a week before we see it deployed. There may be a
> few more things to go, but certainly not of that size.
>
> Speaking of major features, I think that must be darn near the entire JDBC
> API we've wrapped with iBATIS, and iBATIS 2.0 is showing its age. It's
> been in production for almost 2.5 years, which is great life to get out of
> any software.
>
> That said, with 2.2.0 out, I fully expect the next major version to be 3.0.
> I recommend 2.0 enter an extended maintenance mode, whereby we only fix
> bugs and make minor improvements to existing features.
>
> I don't suggest we attempt to leverage Java 5/6 or JDBC 3/4 features in
> iBATIS 2.x.
>
> Instead, I'm thinking iBATIS 3.0 should cover all of those, with 2.x still
> supported until JDK 1.4 drops to well below 15% usage (it's currently at
> around 80%).
>
> Thoughts welcome.
>
> Cheers,
>
> Clinton
>
Re: Multiple Result Set Support complete, 2.2.0 will fly within a week
Posted by Larry Meadors <lm...@apache.org>.
I totally agree that 2.x should not try and assimilate the new JDKs and the
new JDBC stuff - that should be tackled in 3.x instead.
On a related note, what JDBC drivers are at jdbc4 now?
Oracle, MySQL, and Sybase are on the expert group, but I poked around the
Oracle and MySQL sites looking for drivers, and came up empty. I don't
really care about Sybase, sorry. ;-)
Derby looks like they might have it in the nightly builds, but "There is no
guarantee that they will actually work nor that they will include optional
build components that are present in official releases, such as JSR169
support, OSGi support, and JDBC 4.0 support."
PostgreSQL look like they might have drivers, but I didn't find them
available for download either..or even mentioned on their site.
So, what that tells me is that if we are going to make iBATIS3 work with
JDBC4, we may need to help implement or at the very least test JDBC4, too. I
am OK with that, it might be fun to get into the guts of the JDBC spec and a
few driver implementations. ;-)
Thinking out loud...I wonder if it would be possible for iBATIS3 to sit
between the driver and the application in a way that it adds functionality
to the driver in a standard way? What I mean by that is could iBATIS
implement the JDBC4 specification, but really just be a wrapper for a JDBC4
driver that adds our funtionality to any existing driver? That would be
slick.
Larry
On 8/13/06, Clinton Begin <cl...@gmail.com> wrote:
>
> Hi all,
>
> The good news is that I'm on vacation. The bad news is that I spent the
> last 6 hours watching the first two extended edition Lord of the Rings
> movies while implementing the Multiple ResultSet support.
>
> That was the last "required" feature for 2.2.0 to go out, so I'm thinking
> it should be no more than a week before we see it deployed. There may be a
> few more things to go, but certainly not of that size.
>
> Speaking of major features, I think that must be darn near the entire JDBC
> API we've wrapped with iBATIS, and iBATIS 2.0 is showing its age. It's
> been in production for almost 2.5 years, which is great life to get out of
> any software.
>
> That said, with 2.2.0 out, I fully expect the next major version to be 3.0.
> I recommend 2.0 enter an extended maintenance mode, whereby we only fix
> bugs and make minor improvements to existing features.
>
> I don't suggest we attempt to leverage Java 5/6 or JDBC 3/4 features in
> iBATIS 2.x.
>
> Instead, I'm thinking iBATIS 3.0 should cover all of those, with 2.x still
> supported until JDK 1.4 drops to well below 15% usage (it's currently at
> around 80%).
>
> Thoughts welcome.
>
> Cheers,
> Clinton
>