Drop Portlet MVC support [SPR-14129]

[spring-projects-issues]

Juergen Hoeller opened SPR-14129 and commented

Spring's Portlet MVC support turned into a second-class feature in recent years, never having been updated to the modern-day HandlerMethod infrastructure that Servlet MVC is based on these days (since 3.1 already, with the old Servlet MVC variant deprecated since 3.2). Furthermore, the Portlet 3.0 specification intends to introduce annotation-driven dispatching itself, so there is no strategic place for Spring Portlet MVC either, even within its present niche. And last but not least, common Portlet environments seem to be stuck on Spring 3.x, not even upgrading to Spring 4.x yet.

We will therefore drop Portlet MVC support completely as of Spring 5, while at the same time introducing our Reactive MVC variant. We intend to keep supporting (but not recommending) the use of Spring with JSF in a Portlet environment, in particular through Spring Web Flow. For all other purposes, Spring Framework 4.3.x will remain supported until 2020, including its Portlet MVC support (and underlying Servlet 2.5 support).

---

Issue Links:

• Deprecate MultiActionController and Controller*NameHandlerMapping [SPR-14128] #18700 Deprecate MultiActionController and Controller*NameHandlerMapping
• Drop JDO support [SPR-14130] #18702 Drop JDO support

Referenced from: commits 2b3445d

[ngriffin7a]

To all fans of Spring Portlet MVC: please see my blog post titled What does the future hold for Spring Portlet MVC? Long live PortletMVC4Spring! and the GitHub project page.