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

[<jue...@we...>]

Looking forward, I'm keen on getting out RC1 in December, right before =
Christmas if necessary - the goal as I see it is "this year". Our main =
concern will be documentation, I guess, as everything else should just =
be about bug-fixing and refining. If anyone wants to add a major new =
feature, feel free to go ahead but please tell the group and hurry up =
;-)
=20
One point to get right for RC1 is correct packaging of third-party =
libraries. Like Hibernate, we should include the licenses of all =
packages that we ship. And we should update to the current versions of =
all libs. In particular, we need to pay attention to Hibernate 2.1: =
IIRC, they switched to CGLIB2 in the 2.1 tree, so we should check if our =
AOP framework can work with that too. After all, we have numerous users =
combining Hibernate and Spring's declarative transaction management.
=20
Agreement? Wishes? Complaints?
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von j=FCrgen h=F6ller [werk3AT]
Gesendet: Di 25.11.2003 12:47
An: spr...@li...; =
spr...@li...
Betreff: [Springframework-developer] Spring Framework 1.0 M3 released



Hello everybody,

I'm pleased to announce the release of Spring Framework 1.0 M3. This is =
the fifth public release towards 1.0 final.  As you can see in the =
changelog, there have been lots of changes in this iteration. The next =
release will be 1.0 RC1; we do not plan any further milestone releases.

M3 introduces significant new features and enhancements, 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 notably:
- Controllers are now allowed to throw Exception (affecting =
BaseCommandController and AbstractFormController)
- some of BeanCommandController's methods have been renamed
- ServletRequestDataBinder contains a BindException now instead of =
deriving from it

Typical application code should not be affected as we have kept =
deprecated methods. We recommend to migrate promptly though, as we =
intend to drop the deprecated methods before 1.0 final. See =
changes-M2-M3.txt for details.

Regards,
Juergen



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer