Quick Table of Contents
  1. Table of Contents
  2. Preface
  3. Section 1: Application Design Concepts and Principles
  4. Section 2: Common Architectures
  5. Section 3: Integration and Messaging
  6. Section 4: Business Tiers Technologies
  7. Section 5: Web Tier Technologies
  8. Section 6: Applicability of Java EE Technology
  9. Section 7: Patterns
  10. Section 8: Security

Section 5: Web Tier Technologies

State the benefits and drawbacks of adopting a web framework in designing a Java EE application.

Software framework for the development of dynamic web applications. Avoids overhead in development for the web. Puts an abstract layer on top of the Servlet API.

Benefits

Drawbacks

Explain standard uses for JSP pages and servlets in a typical Java EE application.

JSP

JSPs are text files that contain static formatting code (like HTML or XML) and JSP-elements (scriptlets and custom tags) that generate dynamic content.

Servlets

Servlets objects work with a request-response paradigm. It is possible to output HTML code directly (not recommended).

Servlet lifecycle:

  1. Servlet is created then initialized
  2. Zero or more service calls from clients are handle
  3. Servlet is destroyed then garbage collected and finalized

Model 1 Architecture

Model 2 Architecture

Explain standard uses for JavaServer Faces components in a typical Java EE application.

JavaServer Faces

JavaServer Faces Main Components

  1. Java APIs to represent UI components, manage state, handle events, supports internationalization and accessibility, and validate input.
  2. Two JSP custom tag libraries for expressing user interface (UI) components within a JSP page (core and HTML), and for wiring components to server-side objects.

JavaServer Faces Application Components

  1. JavaBeans components (or model objects)
  2. Event listeners
  3. JSP pages
  4. Property files
  5. Server-side helper classes
  6. A custom tag library for UI components
  7. A custom tag library for event handlers and validators
  8. UI components for stateful objects on the server
  9. Validators, event handlers, and navigation handlers
  10. Configuration file (faces-config.xml)

JavaServer Faces Request Lifecycle

  1. Restore state of objects
  2. Request processed by FacesServlet
  3. Loads appropriate view template
  4. Builds component tree
  5. Processes events
  6. Renders response
  7. Save state of objects

Given a system requirements definition, explain and justify your rationale for choosing a web-centric or EJB-centric implementation to solve the requirements. Web-centric means that you are providing a solution that does not use EJB components. EJB-centric solution will require an application server that supports EJB components.

Web-Centric

Web tier communicates directly with Enterprise Information Resource (EIS).

EJB-Centric

Enterprise beans encapsulate the EIS tier and core application logic. Web tier communicates with the beans and serves only as a front end.

Comments
hactolmna - 14 April 2012hWCXkz <a href="http://tdigofakzbjl.com/">tdigofakzbjl</a>
Jegan - 13 April 2012When I'm doing JSP, I can never remember the atetibutrs for the various tags, nor exactly what class the implicit objects are. This book allows me to look them up quickly without having to have a big manual on my desk. It's cheap and small, and you can find stuff quickly. I give it a 4 instead of a 5 because like many pocket references from O'Reilly, it doesn't have a sufficient cross-referenced index.
Leave a comment


Name:*
Email:
Message:*
Security code:*
(type the code in the text field)