move up to springframework 2.5.6?

[Eamonn Dwyer-2]

Hi
is there a reason we are using version 2.5.5 of spring framework? I think servicemix and camel have already moved on up to 2.5.6, so would it be a good idea to upgrade to both stay in synch with them and also to avail of any bug fixes.

Regards
Eamonn
     
_________________________________________________________________
New Windows 7: Find the right PC for you. Learn more.
http://windows.microsoft.com/shop

[Paweł Lipka]

Just for you to know - we're happily using CXF 2.2.3 with Spring 2.5.6
without any issues whatsoever. We only had to bump up xbean version to 3.6.

thanks,
Eamonn Dwyer wrote:
> Hi
> is there a reason we are using version 2.5.5 of spring framework? I think servicemix and camel have already moved on up to 2.5.6, so would it be a good idea to upgrade to both stay in synch with them and also to avail of any bug fixes.
>
> Regards
> Eamonn
>      
> _________________________________________________________________
> New Windows 7: Find the right PC for you. Learn more.
> http://windows.microsoft.com/shop


--
Paweł Lipka
Senior IT Architect
AMG.net, A Bull Group Company
ul. Łąkowa 29
90-554 Łódź
tel.: [phone]
www.amg.net.pl

Treść niniejszej wiadomości może być poufna.
Jeżeli nie jesteście Państwo jej adresatem, to rozprowadzanie
lub wykorzystywanie zawartych tu informacji jest zabronione.

This e-mail contains material that is confidential for the sole
use of the intended recipient. Any review, reliance or distribution
by others or forwarding without express permission is strictly
prohibited. If you are not the intended recipient, please contact
the sender and delete all copies.

[dkulp]

On Wed November 4 2009 10:43:38 am Eamonn Dwyer wrote:
> Hi
> is there a reason we are using version 2.5.5 of spring framework? I think
>  servicemix and camel have already moved on up to 2.5.6, so would it be a
>  good idea to upgrade to both stay in synch with them and also to avail of
>  any bug fixes.

Spring 2.5.6 has a "bug" in the JMS stuff that is resulting in stack traces
being printed out in several places when running out test suite.  We've more
or less stayed on 2.5.5 so that those stack traces aren't confused with real
errors.

--
Daniel Kulp
dkulp@...
http://www.dankulp.com/blog

[Eamonn Dwyer-2]

Ok so, thanks for explaining it.
The other reason I suggested it was because my project is using artifacts from cxf, servicemix and camel. I ended up with a mix of 2.5.5 and 2.5.6, and I end up with method signature clashes :(. I can live with more stringent depenedencies in my poms until everyone harmonises on 2.5.7.

Regards
Eamonn

> From: dkulp@...
> To: dev@...
> Subject: Re: move up to springframework 2.5.6?
> Date: Wed, 4 Nov 2009 11:04:57 -0500
> CC: eamdwyercxf@...
>
> On Wed November 4 2009 10:43:38 am Eamonn Dwyer wrote:
> > Hi
> > is there a reason we are using version 2.5.5 of spring framework? I think
> >  servicemix and camel have already moved on up to 2.5.6, so would it be a
> >  good idea to upgrade to both stay in synch with them and also to avail of
> >  any bug fixes.
>
> Spring 2.5.6 has a "bug" in the JMS stuff that is resulting in stack traces
> being printed out in several places when running out test suite.  We've more
> or less stayed on 2.5.5 so that those stack traces aren't confused with real
> errors.
>
> --
> Daniel Kulp
> dkulp@...
> http://www.dankulp.com/blog

     
_________________________________________________________________
New Windows 7: Find the right PC for you. Learn more.
http://windows.microsoft.com/shop