• 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

Spring In Action: but I'm stuck in Struts

 
blacksmith
Posts: 979
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

I'm dealing with a Struts application...version 1.2.9

...there are pressing reasons to migrate to Spring e.g.
security...does your book give some indications on
how to go about migrating frameworks...

Cheers,

Gian
 
author
Posts: 422
13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Tips on migrating from Struts to Spring MVC would be a wonderful topic for an article or blog entry, but it's not included in the book.

Why? Well, where would I draw the line? Migration from Struts to Spring...migration from WebWork to Spring...migration from Tapestry to Spring...migration from Wicket to Spring...migration from [pick a web framework] to Spring. You could probably write a book's worth of material just on migrating from Framework X to Spring, where each chapter would cover a different value for X.

It's worth pointing out here that there's no reason that you *must* abandon Struts, WebWork, Wicket, or whatever in order to use Spring. You can use Struts (or whatever you like) in the web layer of your application and use Spring for other parts. In fact, that might be the first step in such a migration: leave the web layer alone and start using Spring for things like declarative transactions or security...then if you decide to move to Spring MVC at the web layer you can do so...or not. Your choice.
 
reply
    Bookmark Topic Watch Topic
  • New Topic