The Model-View-Controller Paradigm
Enterprise applications are typically split into three different tiers, or layers. They are more commonly referred to as the presentation layer (the application’s “view”), the business object layer (the application’s “controller”), and the data access layer (the application’s “model”). Does any of this seem vaguely familiar to you? In a roundabout way, we have described the Model-View-Controller (MVC) paradigm that you have no doubt seen in Java Swing or JavaServer Pages.
In this chapter, we will present some of the more common issues you are likely to run into, with respect to internationalization and localization, for the various tiers in the MVC paradigm when developing an enterprise application, along with best practices to handle these issues. Our discussion will move from the presentation layer to the business object layer and finally to the data access layer.