Friday, October 26, 2012

Java EE 6

Web Tie

JSF: JavaServer Faces technology is a server-side component framework for building Java technology-based web applications.

  • JavaServer Faces technology provides a well-defined programming model and various tag libraries. These features significantly ease the burden of building and maintaining web applications with server-side user interfaces (UIs). With minimal effort, you can complete the following tasks.
  • Create a web page.
  • Drop components onto a web page by adding component tags.
  • Bind components on a page to server-side data.
  • Wire component-generated events to server-side application code.
  • Save and restore application state beyond the life of server requests.
  • Reuse and extend components through customization.

Diagram of web application technologies. JavaServer Pages, the JSP Standard Tag Library, and JavaServer Faces rest on Java Servlet technology. .

  • One of the greatest advantages of JavaServer Faces technology is that it offers a clean separation between behavior and presentation for web applications. A JavaServer Faces application can map HTTP requests to component-specific event handling and manage components as stateful objects on the server.
  • Facelets technology, available as part of JavaServer Faces 2.0, is now the preferred presentation technology for building JavaServer Faces technology-based web applications
  • Createing a simple JSF app
  • In the Java EE 6 platform, JavaServer Faces provides built-in support for Ajax. 
    • By using the f:ajax tag along with another standard component in a Facelets application. This method adds Ajax functionality to any UI component without additional coding and configuration.
    • By using the JavaScript API method jsf.ajax.request(), directly within the Facelets application. This method provides direct access to Ajax methods, and allows customized control of component behavior.

EL :  Expression Language. Used by both JSP and JSF.

Web Services

Enteprise Beans

Persistence(JPA)

Security

Contexts and Dependency Injection

The most fundamental services provided by CDI are as follows:
  • Contexts: The ability to bind the lifecycle and interactions of stateful components to well-defined but extensible lifecycle contexts
  • Dependency injection: The ability to inject components into an application in a typesafe way, including the ability to choose at deployment time which implementation of a particular interface to inject

No comments:

Post a Comment