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

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

According to this email:
  
http://sourceforge.net/mailarchive/forum.php?thread_id=3471802&forum_id=7517
the Hibernate team is aiming for a Hibernate 2.1 release before Dec. 14th.

Assuming that does go through, that makes the decision process a bit 
simpler for us; we just have to decide if we are targetting the released 
Hibernate 2.1 and its cglib, or if we want to stick with Hibernate 2.0 
for a bit longer. Personally I favour the former, in that I'm already 
using Hibernate 2.1beta6 with Spring right now, but other people may 
have other opinions...

Regards,
Colin

Colin Sampaleanu wrote:

> 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 same thing 
> does not necessarilly apply to us in our 1.0 RC and final releases. 
> That is, I don't personally know what state cglib 2 is right now. We 
> have to look at it ourselves. Even if we do go to cglib2, I think that 
> may kill our ability to work with Hibernate 2.0, if cglib2 is not 
> totally upwards compatible with cglib1. This is important to figure 
> out...
>
> I'm actually unclear on why cglib embeds ASM themselves. It's a little 
> bit annoying, as I use AMS outside of cglib, and that fact that it's 
> in the cglib jar means I am tied to that version unless I want to do 
> some surgery.
>
>
> jürgen höller [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 "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 ;-)
>>
>> 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.
>>
>> Agreement? Wishes? Complaints?
>>
>> Juergen
>>
>>
>> ________________________________
>>
>> Von: spr...@li... im Auftrag 
>> von jürgen höller [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
>>   
>