Note that there are some explanatory texts on larger screens.

plurals
  1. POIs it possible\advisable to refactor a Spring MVC application to use another MVC framework?
    text
    copied!<p>I am just getting started using Spring and am currently reading <a href="http://rads.stackoverflow.com/amzn/click/1933988134" rel="nofollow">Spring in Action</a> to ramp up. In citing the benefits of Spring vs. EJBs, the book makes the statement: </p> <blockquote> <p>"With Spring, components are typically not required to implement, extend, or use any Spring-specific classes or interfaces, making it possible to reuse the components anywhere, even in the absence of Spring."</p> </blockquote> <p>My application is currently using Spring MVC. I can see how the above statement holds true for my application's business logic, as the use of dependency injection has completely decoupled our beans from the Spring framework. But what about the MVC stuff, which in this case is a web application? I am curious as to whether it would be possible to swap out Spring MVC in my application with another MVC framework in the future. </p> <p>My question is twofold:<br> 1) Should I view the web tier as tightly coupled to the Spring framework and assume that a change in my MVC would necessitate the creation of a new web application to support it? </p> <p>2) If not, what would be involved in decoupling the web application from Spring? I can already guess that in the absence of the Spring framework, all of the annotations would need to be removed from the controllers and the associated code would need to be refactored to support the new MVC framework. </p> <p>I am particularly interested in the insights of anyone who has been through this process.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload