springframework-developer

[Springframework-developer] Hibernate 3

[Colin S. <col...@ex...>]

Hibernate 3 is now out in Alpha. We should probably start thinking about 
how to add support for it, and a timeframe.

It's actually good that we didn't do anything before this, as there have 
been 4-5 bug fixes in Hibernate related session handling and transaction 
code the last few weeks. Since Hibernate 3 is in an entirely different 
package, what I think is probably the only viable option given that 
people are going to be using Hibernate2 for a long time yet, is to build 
up a parallel hierarchy of the support classes, probably with the same 
package names, but 'hibernate3' instead of just 'hibernate'. Arguably, 
the class names might make sense to have the version too, since it would 
reduce confusion a lot.

In terms of a timeframe, this could happen at any time in the sandbox, 
and probably in the main source tree after 1.1 final is out. The main 
issue is developer time, although I see the work as being pretty 
straightforward to do a direct translation. It's definitely worth it to 
then figure out what makes sense to add given the enhanced capabilities.

One interesting thing I read in the release notes; Hibernate now throws 
unchecked exceptions instead of checked exceptions...

Colin

[Springframework-developer] Re: Hibernate 3

[Artur K. <kar...@as...>]

Colin Sampaleanu wrote:

> Hibernate 3 is now out in Alpha. We should probably start thinking about
> how to add support for it, and a timeframe.

It would be great to have HB3 incorporated into spring, even in sandbox. Lot
of people could possibly help testing HB3 (well, at leas me:). Of course
HB3 has a lot of new, shiny, sexy features :).
 
> It's actually good that we didn't do anything before this, as there have
> been 4-5 bug fixes in Hibernate related session handling and transaction
> code the last few weeks. Since Hibernate 3 is in an entirely different
> package, what I think is probably the only viable option given that
> people are going to be using Hibernate2 for a long time yet, is to build
> up a parallel hierarchy of the support classes, probably with the same
> package names, but 'hibernate3' instead of just 'hibernate'. Arguably,
> the class names might make sense to have the version too, since it would
> reduce confusion a lot.

I'm not convinced. I thing most developers will switch from 2 to 3 within a
year. After that HB2 will be virtually outdated (like HB1 is now) and
spring will end up with "polluted" package names. I tend to wait few months
and switch completly to HB3, instead of HB2 and not "polluting" spring
packages. What about using "old" *.hibernate.* packages and adding classes
with version suffix? Just my $0.02. (and of course, with CVS there are,
unfortunatelly serious problems with directories - so refactoring (future
hibernate3->hibernate migration) is rather hard, in this case).

> In terms of a timeframe, this could happen at any time in the sandbox,
> and probably in the main source tree after 1.1 final is out. The main
> issue is developer time, although I see the work as being pretty
> straightforward to do a direct translation. It's definitely worth it to
> then figure out what makes sense to add given the enhanced capabilities.
> 
> One interesting thing I read in the release notes; Hibernate now throws
> unchecked exceptions instead of checked exceptions...

Other which could reflect spring API are "named-entities". All "old" session
- entity related - methods are now doubled with new, overloaded versions
with entity name.

Having support for new hibernate - spring managed - events would be cool
also.

Artur

RE: [Springframework-developer] Re: Hibernate 3

[Tom K <tk...@co...>]

I second this (anyone else?). Hibernate3 will be what I develop my new
projects with.

Tom K.

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Artur Karazniewicz
Sent: Tuesday, August 24, 2004 12:48 PM
To: spr...@li...
Subject: [Springframework-developer] Re: Hibernate 3

Colin Sampaleanu wrote:

> Hibernate 3 is now out in Alpha. We should probably start thinking
about
> how to add support for it, and a timeframe.

It would be great to have HB3 incorporated into spring, even in sandbox.
Lot
of people could possibly help testing HB3 (well, at leas me:). Of course
HB3 has a lot of new, shiny, sexy features :).
 
> It's actually good that we didn't do anything before this, as there
have
> been 4-5 bug fixes in Hibernate related session handling and
transaction
> code the last few weeks. Since Hibernate 3 is in an entirely different
> package, what I think is probably the only viable option given that
> people are going to be using Hibernate2 for a long time yet, is to
build
> up a parallel hierarchy of the support classes, probably with the same
> package names, but 'hibernate3' instead of just 'hibernate'. Arguably,
> the class names might make sense to have the version too, since it
would
> reduce confusion a lot.

I'm not convinced. I thing most developers will switch from 2 to 3
within a
year. After that HB2 will be virtually outdated (like HB1 is now) and
spring will end up with "polluted" package names. I tend to wait few
months
and switch completly to HB3, instead of HB2 and not "polluting" spring
packages. What about using "old" *.hibernate.* packages and adding
classes
with version suffix? Just my $0.02. (and of course, with CVS there are,
unfortunatelly serious problems with directories - so refactoring
(future
hibernate3->hibernate migration) is rather hard, in this case).

> In terms of a timeframe, this could happen at any time in the sandbox,
> and probably in the main source tree after 1.1 final is out. The main
> issue is developer time, although I see the work as being pretty
> straightforward to do a direct translation. It's definitely worth it
to
> then figure out what makes sense to add given the enhanced
capabilities.
> 
> One interesting thing I read in the release notes; Hibernate now
throws
> unchecked exceptions instead of checked exceptions...

Other which could reflect spring API are "named-entities". All "old"
session
- entity related - methods are now doubled with new, overloaded versions
with entity name.

Having support for new hibernate - spring managed - events would be cool
also.

Artur



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004
 

Re: [Springframework-developer] Re: Hibernate 3

[Seth L. <set...@gm...>]

I think Spring 1.XX should always work with Hibernate 2.  A Spring
2.XX release could drop Hibernate 2, IMHO.  But that is a far bit
away.

Minor release numbers should always be backwards compatible.

My two cents,
Seth

On Tue, 24 Aug 2004 12:55:36 -0500, Tom K <tk...@co...> wrote:
> I second this (anyone else?). Hibernate3 will be what I develop my new
> projects with.
> 
> Tom K.
> 
> 
> 
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On Behalf
> Of Artur Karazniewicz
> Sent: Tuesday, August 24, 2004 12:48 PM
> To: spr...@li...
> Subject: [Springframework-developer] Re: Hibernate 3
> 
> Colin Sampaleanu wrote:
> 
> > Hibernate 3 is now out in Alpha. We should probably start thinking
> about
> > how to add support for it, and a timeframe.
> 
> It would be great to have HB3 incorporated into spring, even in sandbox.
> Lot
> of people could possibly help testing HB3 (well, at leas me:). Of course
> HB3 has a lot of new, shiny, sexy features :).
> 
> > It's actually good that we didn't do anything before this, as there
> have
> > been 4-5 bug fixes in Hibernate related session handling and
> transaction
> > code the last few weeks. Since Hibernate 3 is in an entirely different
> > package, what I think is probably the only viable option given that
> > people are going to be using Hibernate2 for a long time yet, is to
> build
> > up a parallel hierarchy of the support classes, probably with the same
> > package names, but 'hibernate3' instead of just 'hibernate'. Arguably,
> > the class names might make sense to have the version too, since it
> would
> > reduce confusion a lot.
> 
> I'm not convinced. I thing most developers will switch from 2 to 3
> within a
> year. After that HB2 will be virtually outdated (like HB1 is now) and
> spring will end up with "polluted" package names. I tend to wait few
> months
> and switch completly to HB3, instead of HB2 and not "polluting" spring
> packages. What about using "old" *.hibernate.* packages and adding
> classes
> with version suffix? Just my $0.02. (and of course, with CVS there are,
> unfortunatelly serious problems with directories - so refactoring
> (future
> hibernate3->hibernate migration) is rather hard, in this case).
> 
> > In terms of a timeframe, this could happen at any time in the sandbox,
> > and probably in the main source tree after 1.1 final is out. The main
> > issue is developer time, although I see the work as being pretty
> > straightforward to do a direct translation. It's definitely worth it
> to
> > then figure out what makes sense to add given the enhanced
> capabilities.
> >
> > One interesting thing I read in the release notes; Hibernate now
> throws
> > unchecked exceptions instead of checked exceptions...
> 
> Other which could reflect spring API are "named-entities". All "old"
> session
> - entity related - methods are now doubled with new, overloaded versions
> with entity name.
> 
> Having support for new hibernate - spring managed - events would be cool
> also.
> 
> Artur
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

Re: [Springframework-developer] Re: Hibernate 3

[Martin K. <Mar...@St...>]

> I think Spring 1.XX should always work with Hibernate 2.  A Spring
> 2.XX release could drop Hibernate 2, IMHO.  But that is a far bit
> away.

I don't like droping Hibernate 2. You know it will cost some afford
(aka money) to convert a project utilizing Hibernate2 to a project
utilizing Hibernate3. So it is very likely to have projects, which
work fine and using Hibernate 2 to stay in that condition for a
really long time. And so I think the support should not be dropped
anytime. At least a compatible solution should be offered.

I favour the package naming solution, mentioned earlier. Call
the package hibernate3 and rename the old one to hibernate2.

So I guess things would become very clear and beside some
renaming nothing much has to be changed to convert an existing
project to use the newest Spring release.


Cheers,

Martin (Kersten)

>
> Minor release numbers should always be backwards compatible.
>
> My two cents,
> Seth
>
> On Tue, 24 Aug 2004 12:55:36 -0500, Tom K <tk...@co...> wrote:
> > I second this (anyone else?). Hibernate3 will be what I develop my new
> > projects with.
> >
> > Tom K.
> >
> >
> >
> > -----Original Message-----
> > From: spr...@li...
> > [mailto:spr...@li...] On Behalf
> > Of Artur Karazniewicz
> > Sent: Tuesday, August 24, 2004 12:48 PM
> > To: spr...@li...
> > Subject: [Springframework-developer] Re: Hibernate 3
> >
> > Colin Sampaleanu wrote:
> >
> > > Hibernate 3 is now out in Alpha. We should probably start thinking
> > about
> > > how to add support for it, and a timeframe.
> >
> > It would be great to have HB3 incorporated into spring, even in sandbox.
> > Lot
> > of people could possibly help testing HB3 (well, at leas me:). Of course
> > HB3 has a lot of new, shiny, sexy features :).
> >
> > > It's actually good that we didn't do anything before this, as there
> > have
> > > been 4-5 bug fixes in Hibernate related session handling and
> > transaction
> > > code the last few weeks. Since Hibernate 3 is in an entirely different
> > > package, what I think is probably the only viable option given that
> > > people are going to be using Hibernate2 for a long time yet, is to
> > build
> > > up a parallel hierarchy of the support classes, probably with the same
> > > package names, but 'hibernate3' instead of just 'hibernate'. Arguably,
> > > the class names might make sense to have the version too, since it
> > would
> > > reduce confusion a lot.
> >
> > I'm not convinced. I thing most developers will switch from 2 to 3
> > within a
> > year. After that HB2 will be virtually outdated (like HB1 is now) and
> > spring will end up with "polluted" package names. I tend to wait few
> > months
> > and switch completly to HB3, instead of HB2 and not "polluting" spring
> > packages. What about using "old" *.hibernate.* packages and adding
> > classes
> > with version suffix? Just my $0.02. (and of course, with CVS there are,
> > unfortunatelly serious problems with directories - so refactoring
> > (future
> > hibernate3->hibernate migration) is rather hard, in this case).
> >
> > > In terms of a timeframe, this could happen at any time in the sandbox,
> > > and probably in the main source tree after 1.1 final is out. The main
> > > issue is developer time, although I see the work as being pretty
> > > straightforward to do a direct translation. It's definitely worth it
> > to
> > > then figure out what makes sense to add given the enhanced
> > capabilities.
> > >
> > > One interesting thing I read in the release notes; Hibernate now
> > throws
> > > unchecked exceptions instead of checked exceptions...
> >
> > Other which could reflect spring API are "named-entities". All "old"
> > session
> > - entity related - methods are now doubled with new, overloaded versions
> > with entity name.
> >
> > Having support for new hibernate - spring managed - events would be cool
> > also.
> >
> > Artur
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> > _______________________________________________
> > Springframework-developer mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springframework-developer
> >
> > ---
> > Incoming mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004
> >
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> > _______________________________________________
> > Springframework-developer mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springframework-developer
> >
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer