Link Details

Link 952051 thumbnail
User 899255 avatar

By marcfasel
Published: Apr 09 2013 / 14:39

OpenCms websites tend to place a lot of responsibility for the controller and view functionality of a page on the JSP, a JEE anti-pattern known as a Monolithic/Compound JSP. We recently integrated SpringMVC into an OpenCMS website at one of our clients to gain the advantages of a Model-View-Controller framework without an extensive rewrite of the codebase.
  • 6
  • 1
  • 1479
  • 838
User 226303 avatar

devdanke replied ago:

0 votes Vote down Vote up Reply

The tight linkage between OpenCMS and Spring seems like a poor choice. First, according to the architectural diagram, OpenCMS is hit before Spring. This makes OpenCMS a potential attack vector for security threats. That's a big increase in the surface area your company most protect, day after day, version after version of OpenCMS. Second, following the author's suggestion, your company is now tightly tied to OpenCMS. But what if OpenCMS doesn't meet your company's needs in the future? Switching to another CMS would be difficult. The new CMS would have to be written in Java and offer similar extension points, which is not likely. I think a better approach is to avoid tight integration between Spring and your CMS. Instead, deal with it via an abstract REST API. This would also make testing simpler, because Spring and your CMS could be tested completely separately.

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Upvoters (6)

Downvoters (1)

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java