• 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
  • Ron McLeod
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Rob Spoor
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Carey Brown
Bartenders:

Can implement Spring in part of existing old Servlet/jsp Application

 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We are planning to add an enhancement to a existing old Servlet/Jsp application which was developed more than 10yrs back. Is it possible to implement Spring in part of that application with new enhancement? how feasible it would be ? please correct me or guide me if i have wrong idea on this. Thanks in advance
 
Saloon Keeper
Posts: 26536
187
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It is quite possible. Heck, you can even add JSF to an old web application. The functionality you are gaining comes as additional services not as something that will conflict with older stuff.

I have a project, in fact, that was done with a proprietary MVC and ORM service and I've been slowly migrating stuff as enhancement requests came it. The only real issue I have with this legacy code co-existing with my newer Spring/JSF code is that the old ORM's entity classes couldn't simply be annotated into JPA entity classes because the old ORL did some questionable things with its objects (they're not POJOs, for one thing). So I occasionally have to transfer stuff between new and old ORM models. Which isn't a Spring issue. Even if I was using JPA without Spring, the modelling confllcts would still exist.
 
Ranch Hand
Posts: 46
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, I think you should just configure Spring and your web.xml in order to avoid any conflicts with your current Servlet mappings. Basically don't use any "magic" stuff like Spring Boot.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic