| Usuario |
por favor ayudenme comprender el s... |
Desconocido
|
| Enviado - 1/10/2004 |
| |
User gets access to the application using HTML browser. Presentation tier
handles request via Servlet controller, validate data, resolve and process
target action. Action performs calls to Business logic level using Business
delegate and Service locator patterns (see chapter 3.5 Patterns overview
for details).
Generadora application presentation layer should be able to have access to
the Business Layer. Business Layer entry point is Session Facade which
implicitly can be remote. It is desirable to minimize coupling between
presentation-tier and business service, thus hiding the underlying
implementation details of the service, such as lookup and access. So
Business delegate pattern is used.
The problem is a combination of the problems solved by the Front Controller
and View Helper patterns in the presentation tier. There is no centralized
component for managing access control, content retrieval, or view
management, and there is duplicate control code scattered throughout
various views. Additionally, business logic and presentation formatting
logic are intermingled within these views, making the system less flexible,
less reusable, and generally less resilient to change.
Pattern used to combine a controller and dispatcher with views and helpers
to handle client requests and prepare a dynamic presentation as the
response. Controllers delegate content retrieval to helpers, which manage
the population of the intermediate model for the view. A dispatcher is
responsible for view management and navigation and can be encapsulated
either within a controller or a separate component.
urgente
mi e-mail: [email protected] |
| |
|
|
|
