RE: [Springframework-developer] Spring Framework 1.0 M3 released

[Alef A. \(JTeam\) <al...@jt...>]

> or if we want to stick with=20
> Hibernate 2.0=20
> for a bit longer.
I don't know. Personally I don't think we will have much problem with
the transition to 2.1, but I don't know about other people. Are there
any significant differences between Hibernate 2.1 and 2.0 that would
convince us to switch, besides the CGLIB stuff? If there aren't any
major compatibility-issues I would prefer checking both CGLIB1 and 2
(thus supporting both Hib 2.0 and 2.1), but that might generatea lot of
work... It would however allow people having Spring mX in production
already to change to Spring 1.0 without changing Hibernate version...

Just some thougts...


> Regards,
> Colin
>=20
> Colin Sampaleanu wrote:
>=20
> > The issue is that Hibernate 2.1 is still in beta. So while it's
> > hopefully ok for them to go to cglib 2 in their beta, the=20
> same thing=20
> > does not necessarilly apply to us in our 1.0 RC and final releases.=20
> > That is, I don't personally know what state cglib 2 is=20
> right now. We=20
> > have to look at it ourselves. Even if we do go to cglib2, I=20
> think that=20
> > may kill our ability to work with Hibernate 2.0, if cglib2 is not=20
> > totally upwards compatible with cglib1. This is important to figure=20
> > out...
> >
> > I'm actually unclear on why cglib embeds ASM themselves.=20
> It's a little
> > bit annoying, as I use AMS outside of cglib, and that fact=20
> that it's=20
> > in the cglib jar means I am tied to that version unless I=20
> want to do=20
> > some surgery.
> >
> >
> > j=FCrgen h=F6ller [werk3AT] wrote:
> >
> >> Looking forward, I'm keen on getting out RC1 in December, right
> >> before Christmas if necessary - the goal as I see it is=20
> "this year".=20
> >> Our main concern will be documentation, I guess, as=20
> everything else=20
> >> should just be about bug-fixing and refining. If anyone=20
> wants to add=20
> >> a major new feature, feel free to go ahead but please tell=20
> the group=20
> >> and hurry up ;-)
> >>
> >> One point to get right for RC1 is correct packaging of third-party
> >> libraries. Like Hibernate, we should include the licenses of all=20
> >> packages that we ship. And we should update to the current=20
> versions=20
> >> of all libs. In particular, we need to pay attention to Hibernate=20
> >> 2.1: IIRC, they switched to CGLIB2 in the 2.1 tree, so we should=20
> >> check if our AOP framework can work with that too. After=20
> all, we have=20
> >> numerous users combining Hibernate and Spring's declarative=20
> >> transaction management.
> >>
> >> Agreement? Wishes? Complaints?
> >>
> >> Juergen
> >>
> >>
> >> ________________________________
> >>
> >> Von: spr...@li...=20
> im Auftrag
> >> von j=FCrgen h=F6ller [werk3AT]
> >> Gesendet: Di 25.11.2003 12:47
> >> An: spr...@li...;=20
> >> spr...@li...
> >> Betreff: [Springframework-developer] Spring Framework 1.0=20
> M3 released
> >>
> >>
> >>
> >> Hello everybody,
> >>
> >> I'm pleased to announce the release of Spring Framework=20
> 1.0 M3. This
> >> is the fifth public release towards 1.0 final.  As you can=20
> see in the=20
> >> changelog, there have been lots of changes in this iteration. The=20
> >> next release will be 1.0 RC1; we do not plan any further milestone=20
> >> releases.
> >>
> >> M3 introduces significant new features and enhancements,=20
> among them:
> >> - Type 3 IoC support in the bean factory (constructor resolution)
> >> - bean factory SPI interfaces (package bean.factory.config)
> >> - redesigned AOP API (more flexible pointcut handling etc)
> >> - reworked and optimized transaction manager implementations
> >> - fine-grained JDBC exception handling in the Hibernate support
> >> - reworked JDO support with a new JdoDialect strategy
> >> - reworked exception handling in the web framework
> >> - working Tiles example application included
> >>
> >> Some of the changes will need migration of existing code, most=20
> >> notably:
> >> - Controllers are now allowed to throw Exception (affecting=20
> >> BaseCommandController and AbstractFormController)
> >> - some of BeanCommandController's methods have been renamed
> >> - ServletRequestDataBinder contains a BindException now instead of=20
> >> deriving from it
> >>
> >> Typical application code should not be affected as we have kept
> >> deprecated methods. We recommend to migrate promptly though, as we=20
> >> intend to drop the deprecated methods before 1.0 final. See=20
> >> changes-M2-M3.txt for details.
> >>
> >> Regards,
> >> Juergen
> >>  =20
> >
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.=20
> Does SourceForge.net help you be more productive?  Does it=20
> help you create better code?  SHARE THE LOVE, and help us=20
> help YOU!  Click Here: http://sourceforge.net/donate/=20
> _______________________________________________
> Springframework-developer mailing list=20
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20