Violation of MVC
Could you give an example of a real-world scenario where the MVC is violated and could you explain how the violation takes place? Can you suggest what quality(ies) of a system are sacrificed in this case?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

MVC is violated anytime the application control-flow and/or the model or view/presentation is coupled into the same components/objects. This is most often seen in J2EE Web applications when servlets are used to handle control flow (client requests), but they also are used to access databases and create the markup (HTML) for the responses.

When MVC is violated, tight-couplings within the source code prevent the system from being distributed or scaled easily. It also makes upgrades to the system much more difficult, because the system is not divided into easily replaceable modules.

This was first published in December 2003

Back to top