• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
Sheriffs:
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
Bartenders:
  • Mike London

Migration from Spring 2.5

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Craig,
I developed a project based on Spring2.5 and IBatis2.3 , do you advice the migration to the new major release of Spring? Do you think it's worth it ? Is spring2.5 compatible with Ibatis 2.3 ?

Regards
Sandro .
 
author
Posts: 422
13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I absolutely recommend moving to Spring 3 from any older version of Spring. My reasons are explained in several other posts on this forum, so I won't repeat them here. In short, Spring 3 affords several key benefits in terms of bean wiring and REST support to make it worth the move.

As for iBatis support...I don't use iBatis that much any more, but I do know that Spring's ORM module is compiled against iBatis 2.3.4. So, yes, I believe it will work with iBatis 2.3.
 
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Craig:

In Spring 2.5, several classes and methods — for example, paged list holders in Spring MVC — have been deprecated and scheduled for removal in Spring 3.0. Are there any guidelines not only to merely migrate existing applications to Spring 3.0, but also to migrate them in an optimal way, through usage of non-deprecated API components?

Thanks,

Jeff
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic