Java EE6 - Architecture and Services

Resources

• JSR-316 Java Platform, Enterprise Edition 6 (Final Release)
  Splitted in 2x3 parts (either for an evaluation or building an implementation):
  - Java EE 6 Specification (evaluation, implementation)
  - Java EE 6 Web Profile Specification (evaluation, implementation)
  - Java EE 6 Managed Beans Specification (evaluation, implementation)
• JSR-220 Enterprise JavaBeans 3.0 Final Release (simplified)
  The simplified version is highly recommended as an introduction to EJB 3.0.

Java EE Architecture Diagram

Click to enlarge

 

JAX-RPC (JSR-101): Java API for XML-Based RPC

The RPC (Remote Procedure Call) mechanism enables a remote procedure call from a client to be communicated to a remote server.

JAX-WS (JSR-224): Java API for XML-Based Web Services

JAX-WS is a follow-on to JAX-RPC extending it, with new specifications and new versions of the standards it depends on.

SAAJ (JSR-67): SOAP with Attachments API for Java

SAAJ is used mainly for the SOAP messaging that goes on behind the scenes in JAX-WS handlers and JAXR implementations.

JAX-RS (JSR-311): Java API for RESTful Web Services

Set of Java APIs for the development of Web services built according to the Representational State Transfer (REST) architectural style.

A JAX-RS application is a web application that consists of classes that are packaged as a servlet in a WAR file along with required libraries.

The JAX-RS API is new to the Java EE 6 platform.

JAXR (JSR-93): Java API for XML Registries

JAXR API aims to be the confluence of the various registry specifications (OASIS, eCo Framework, ebXML and UDDI).

JASPIC (JSR-196): Java Authentication Service Provider Interface for Containers

The  JASPIC specification defines a service provider interface (SPI) by which authentication providers that implement message authentication mechanisms may be integrated in client or server message processing containers or runtimes. 

Authentication providers integrated through this interface operate on network messages provided to them by their calling container. They transform outgoing messages so that the source of the message may be authenticated by the receiving container, and the recipient of the message may be authenticated by the message sender. They authenticate incoming messages and return to their calling container the identity established as a result of the message authentication.

The JASPIC API is new to the Java EE 6 platform.

JACC (JSR-115): Java Authorization Service Provider Contract for Containers

The Java ACC API defines a contract between a Java EE application server and an authorization policy provider. All Java EE containers support this contract.

The Java ACC API defines java.security.Permission classes that satisfy the Java EE authorization model. The specification defines the binding of container access decisions to operations on instances of these permission classes. It defines the semantics of policy providers that employ the new permission classes to address the authorization requirements of the Java EE platform, including the definition and use of roles.

CDI & DI (JSR-299): Contexts and Dependency Injection

Contexts and Dependency Injection (CDI) provides Dependency Injection (DI) power and flexibility. Both are part of the Java Platform, Enterprise Edition (Java EE) 6 specification and ready to use.

The CDI API is new to the Java EE 6 platform.

Web Services (JSR-109): Java Web Services

Web services is a service oriented architecture which allows for creating an abstract definition of a service, providing a concrete implementation of a service, publishing and finding a service, service instance selection, and interoperable service use. In general a Web service implementation and client use may be decoupled in a variety of ways. Client and server implementations can be decoupled in programming model. Concrete implementations may be decoupled in logic and transport

WS Metadata (JSR-181): Web Services Metadata

This API allows to reduces the amount of information required to implement Web Services on J2EE by using metadata to specify declaratively the Web Services that each application provides. The metadata annotates the Java source file that implements the Web Service.

Management (JSR-77): Java Management API

The J2EE Management Model is a specification of the attributes, operations and architecture of the managed objects required by compliant J2EE platform implementations. The model is designed to be interoperable with a variety of industry standard management systems and protocols.

JMS (JSR-914): Java Message Service (JMS) API

JMS provides a common way for Java programs to create, send, receive and read an enterprise messaging system’s messages.

Connectors (JSR-322): Java EE Connector Architecture (JCA)

The Java EE Connector architecture defines a standard architecture for connecting the Java EE platform to heterogeneous EISs. Examples of EISs include Enterprise Resource Planning (ERP), mainframe transaction processing (TP), and database systems. By using the J2EE Connector architecture, EIS vendors no longer need to customize their product for each application server. Application server vendors who conform to the J2EE Connector architecture do not need to add custom code whenever they want to add connectivity to a new EIS.

See also:  JSR-112

JTA (JSR-907): Java Transaction API

Java Transaction API (JTA) specifies standard Java interfaces between a transaction manager and the parties involved in a distributed transaction system: the resource manager, the application server, and the transactional applications. 

Persistence (JSR-317): Java Persistence

The Java Persistence 2.0 API addresses improvements in the areas of domain modeling, object/relational mapping, EntityManager and Query interfaces, and the Java Persistence query language. It adds an API for criteria queries, a metamodel API, and support for validation.

JSF (JSR-314): Java Server Faces

JavaServer Faces (JSF) is a user interface (UI) framework for Java web applications. It is designed to significantly ease the burden of writing and maintaining applications that run on a Java application server and render their UIs back to a target client.

Note: See also JSR-127

JSTL (JSR-52): Java Server Pages Standard Tag Library

The ultimate goal of JSTL is to help simplify Java Server Pages (JSP) page authors’ lives. A page author is someone who is responsible for the design of a web application’s presentation layer using JSP pages. Many page authors are not fluent in any programming language.

A key aspect of JSTL is an expression language (EL) designed specifically for the page author.

JavaMail (JSR-919): JavaMail

The JavaMail API provides a set of abstract classes defining objects that comprise a mail system. The API defines classes like Message, Store and Transport. The API can be extended and can be subclassed to provide new protocols and to add functionality when necessary.

Others

Management (JSR-160): Java Management EXtension  (JMX) Remote API

Although JSR-3 defines terminology for remote access to instrumentation, it does not standardize any particular remote access API or protocol. Many solutions exist for exporting JMX API instrumentation
either through existing management protocols such as the simple network management protocol (SNMP) or through proprietary protocols. This JSR (JSR 160) standardizes one such solution.
The principal goals of this standard are interoperability, transparency, security, and flexibility.

Note: JMX 1.x were defined by JSR-3 of the Java Community Process. The changes proposed in the JSR-160 are intended as interim steps towards JSR-255 ("JMX Specification, version 2.0"), which will contains larger set of updates to the JMX Remote specification.

An extension of the JMX Remote API for Web Services is being developed under JSR-262.

Application Deployement (JSR-88): Java Application Deployment

Defines standard APIs to enable deployment of components and applications based on the J2EE platform, as well as the development of platform-independent deployment tools.

Java Network Launch Protocol (JSR-56): JNLP

The Java Network Launching Protocol and API (JNLP) is a Web-centric provisioning protocol and application environment for Web-deployed Java applications. An application implementing this specification is called a JNLP Client.

JSP (JSR-245): Java Server Pages

A JSP page is a textual document that describes how to create a response object from a request object for a given protocol. The processing of the JSP page may involve creating and/or using other objects.

Servlets (JSR-154): Java Servlets

A servlet is a Java technology-based Web component, managed by a container, that generates dynamic content. Like other Java technology-based components, servlets are platform-independent Java classes that are compiled to platform-neutral byte code that can be loaded dynamically into and run by a Java technology-enabled Web server. Containers, sometimes called servlet engines, are Web server extensions that provide servlet functionality. Servlets interact with Web clients via a request/response paradigm implemented by the servlet container.

JavaBeans Activation Framework (JSR-925):  JAF

The Java platform (including JavaBeans) already provides some support for a modest activation framework. The JAF leverages as much of that existing technology as possible. The JAF integrates these mechanisms.

Java Authentication and Authorization Service : JAAS

The Java Authentication and Authorization Service (JAAS) was introduced as an optional package (extension) to the Java 2 SDK, Standard Edition (J2SDK), v 1.3. 

Since J2SDK 1.4, JAAS has been integrated into the JDK (including JSE 7).

Java Naming and Directory Interface: JNDI

The JNDI is included in the Java 2 SDK, v1.3 and later releases (including JSE 7). It is also available as a Java Standard Extension for use with the JDK 1.1 and the Java 2 SDK, v1.2.

JNDI is an API specified in Java technology that provides naming and directory functionality to applications written in the Java programming language.