Java EE 7 Tutorial Part I Introduction to Chapter 1th Overview of section 1.8 Java Platform Java EE 7 API, Standard Edition 7

Original: http://docs.oracle.com/javaee/7/tutorial/doc/overview008.htm

Translation: Shi Zholin [email protected]

1.8 Java EE 7 APIs in the Java Platform, standard Edition 7

Several APIs that is required by the Java EE 7 platform is included in the Java platform, Standard Edition 7 (Java SE 7) and is thus available to Java EE applications.

1.8 Java EE 7 API in the Java Platform, Standard Edition 7

The several API required by the Java EE 7 platform is included in the Java Platform Standard Edition 7 (Java SE 7) for use in Java EE applications.

1.8.1 Java Database Connectivity API

The Java Database Connectivity (JDBC) API lets your invoke SQL commands from Java programming language methods. Your use of the JDBC API in an enterprise bean is when you have a session bean access the database. You can also with the JDBC API from a servlet or a JSP page to access the database directly without going through an enterp Rise Bean.

The JDBC API has both parts:

• An Application-level interface used by the application components to access a database
• A service provider interface to attach a JDBC driver to the Java EE platform

The Java SE 7 platform requires JDBC 4.1.

1.8.1 Java database Connection API

The Java Database Connectivity (JDBC) API allows you to invoke SQL commands in a Java program language method. When you have a session bean accessing the database, you can use the JDBC API in the Enterprise bean. Of course you can also use the JDBC API to connect directly to a database in a servlet or JSP page without having to go through the enterprise bean.

The JDBC API consists of two parts:

• An application-level interface for application component access to the database
• A service provider interface for attaching a JDBC driver to the Java EE Platform

The Java SE 7 platform requires JDBC 4.1.

1.8.2 Java naming and Directory Interface API

The Java Naming and directory Interface (JNDI) API provides naming and directory functionality, enabling applications to a ccess multiple naming and directory services, such as LDAP, DNS, and NIS. The JNDI API provides applications with methods for performing standard directory operations, such as associating attribut Es with objects and searching for objects using their attributes. Using JNDI, a Java EE application can store and retrieve any type of the named Java object, allowing Java EE applications to C Oexist with many legacy applications and systems.

Java EE Naming services provide application clients, enterprise beans, and Web Components with access to a JNDI naming Environment. A naming environment allows a component to being customized without the need to access or change the Componen T ' s source code. A container implements the component ' s environment and provides it to the component as a JNDI naming Context.

The naming environment provides four logical Namespaces:java:comp, Java:module, Java:app, and Java:global for objects Available to components, modules, or applications or shared by all deployed applications. A Java EE component can access named system-provided and User-defined objects. The names of some system-provided objects, such as a default JDBC DataSource object, a default JMS connection factory, and A JTA usertransaction object, is stored in the Java:comp namespace. The Java EE platform allows a component to name user-defined objects, such as enterprise beans, environment entries, JDBC DataSource objects, and messaging destinations.

A Java EE Component can also locate its environment naming the context by using JNDI interfaces. A component can create a Javax.naming.InitialContext object and look up the environment naming context in InitialContext u NDEr the name java:comp/env. A component ' s naming environment is stored directly in the environment naming context or in any of its direct or indirect Subcontexts.

1.8.2 Java naming and directory interface API

The Java Naming and directory interface (JNDI) API provides naming and directory service capabilities that enable applications to access multiple naming and directory services, such as LDAP, DNS, and NIS. This Jndi API provides applications and methods to handle standard directory operations, such as object property access and using property search objects. Using Jndi,java EE applications, you can store and restore any Java named object type, allowing Java EE applications to coexist with many traditional applications and systems.

The Java EE Naming Service provides an environment for application clients, enterprise beans, and Web Component access Jndi naming. A naming environment allows custom component access without the need to change component source code. The container implements the environment for the component and provides it to the component as a Jndi naming context .

This naming environment provides four logical namespaces for active components, modules, apps, or shares in all deployed apps: Java:comp, Java:module, Java:app, and Java:global. A Java EE component can access system-named provided or user-defined objects. The names of some system-supplied objects, such as a default JDBC data source object, a default JMS connection factory, and the default JTA user transaction object, including objects that are stored in the Java:comp namespace. The Java EE platform allows user-defined components to be named objects, such as enterprise beans, environment items, JDBC data source objects, and message destinations.

In a Java EE component, you can also find its environment naming context by using the Jndi interface. A component can create a Javax.naming.InitialContext object and java:comp/in InitialContext The env name queries the environment naming context. The naming environment for a component is stored directly in the environment naming context or in any direct or indirect child context.

1.8.3 JavaBeans Activation Framework

The JavaBeans Activation Framework (JAF) is used by the JavaMail API. JAF provides standard services to determine the type of a arbitrary piece of data, encapsulate access to it, discover the Operations available on it, and create the appropriate JavaBeans component to perform those operations.

1.8.3 JavaBeans Activation Framework

The JavaBeans Activation Framework (JAF) is used for JavaMail APIs. JAF provides standard services to determine any data type, encapsulate its access, discover its available operations, and create the appropriate JavaBean components to perform these operations.

1.8.4 Java API for XML processing

The Java API for XML processing (JAXP), part of the Java SE platform, supports the processing of the XML documents using Docum ENT Object Model (DOM), Simple API for XML (SAX), and extensible Stylesheet Language Transformations (XSLT). JAXP enables applications to parse and transform XML documents independently of a particular xml-processing implementation .

JAXP also provides namespace support, which lets your work with schemas that might otherwise has naming conflicts. Designed to is flexible, JAXP lets you use any xml-compliant parser or XSL processor from within your application and supp Orts the Worldwide Web Consortium (website) schema. You can find information on the Http://www.w3.org/XML/Schema.

1.8.4 java API FOR XML processing

The Java API for XML processing (JAXP) is part of the Java SE platform, which supports the use of the Document Object Model (DOM) to process XML documents, XML simple APIs (SAX), and Extended Style language Transformations (XSLT). JAXP enables applications to parse and transform XML documents independently using specific XML processing implementations.

JAXP also provides namespace support that allows you to work with schemas when you have possible naming conflicts. With flexible design, JAXP allows you to use any of the appropriate XML parsers and XSL processors in your application, and supports the World Wide Web Consortium architecture. You can plan HTTP : Find information in//www.w3.org/xml/schema.

1.8.5 Java Architecture for XML Binding

The Java Architecture for XML Binding (JAXB) provides a convenient-to-bind-a XML schema to a representation in Java L Anguage programs. JAXB can is used independently or in combination with Jax-WS, in which case it provides a standard data binding for Web SE Rvice messages. All Java EE Application client containers, Web containers, and EJB containers support the JAXB API.

The Java EE 7 platform requires JAXB 2.2.

1.8.5 Java Architecture FOR XML binding

The architecture for XML binding (JAXB) provides a convenient way to bind XML schemas to the presentation layer in a Java language program. JAXB can be used alone or in combination with Jax-WS, which in some cases provides standard data binding for Web service messages. All Java EE application client containers, Web containers, and EJB containers support the JAXB API.

The Java EE 7 platform requires JAXB 2.2.

1.8.6 Java API for XML Web Services

The Java API for XML Web services (JAX-WS) specification provides support for Web services, the use of the JAXB API for Bindi ng XML data to Java objects. The JAX-WS specification defines client APIs for accessing Web services as well as techniques for implementing Web Service Endpoints. The implementing Enterprise WEB Services Specification describes the deployment of jax-ws-based Services and clients. The EJB and Java Servlet specifications also describe aspects of such deployment. Jax-ws-based applications can is deployed using any of these deployment models.

The JAX-WS specification describes the support for message handlers that can process message requests and responses. In general, these message handlers execute on the same container and with the same privileges and execution context as the JAX-WS client or endpoint component with which they is associated. These message handlers has access to the same JNDI namespace as their associated component. Custom serializers and Deserializers, if supported, is treated in the same as message handlers.

The Java EE 7 platform requires JAX-WS 2.2.

1.8.6 Java API for XML Web Services

The Java API (JAX-WS) Specification for XML Web Services provides support for using JAXB-bound XML data and Java objects in a Web service. The JAX-WS specification defines the client API for the technical implementation of Web service client Access Web services. The JAX-WS-Based service service and client deployment descriptions for enterprise Web services normalization are implemented. The EJB and Java servlet specifications also provide a partial description of the deployment. JAX-WS-Based applications can be deployed using any deployment model.

The JAX-WS specification Description provides support for message handlers that handle message requests and responses. In the usual case, these message handlers are executed in the same container with the JAX-WS client with the same permissions and execution context, or with the terminal components associated with it. These message handlers can access the same Jndi namespace and its associated components. If custom serialization and deserialization are supported, the message handlers are treated in the same way.

The Java EE 7 platform requires JAX-WS 2.2.

1.8.7 SOAP with Attachments APIs for Java

The SOAP with Attachments APIs for Java (SAAJ) are a low-level API on which JAX-ws depends. SAAJ enables the production and consumption of messages that conform to the SOAP 1.1 and 1.2 specifications and the SOAP W ITH Attachments Note. Most developers don't use the SAAJ API, instead using the higher-level JAX-WS API.

1.8.7 SOAP APIs included with Java

The SOAP API (SAAJ) that comes with Java is a low-level API that relies on JAX-ws. Saaj makes the production and consumption of messages from the SOAP 1.1/1.2 specification and the accompanying soap annotations. Most developers do not use the Saaj API, instead use the Advanced JAX-WS API.

1.8.8 Java authentication and Authorization Service

The Java Authentication and Authorization Service (JAAS) provides a-a-to-a Java EE application to authenticate and auth Orize a specific user or group of users to run it.

JAAS is a Java programming language version of the standard pluggable authentication Module (PAM) framework, which extends The Java platform security architecture to support user-based authorization.

1.8.8 Java certification and certification services

Java and authentication Services (JAAS) provide methods for Java EE applications to authorize and validate specific users or groups that run it.

Jaas is a Java programming language version of the standard Pluggable Authentication module framework that supports user-based authentication for the extended Java Platform Security architecture.

1.8.9 Common Annotations for the Java Platform

Annotations enable a declarative style of programming in the Java platform.

The Java EE 7 platform requires Common Annotations for the Java platform 1.2.

1.8.9 Java Platform General annotations

Annotations make it possible to declare styles programmatically in the Java platform.

The Java EE 7 platform requires common annotation 1.2 for the Java platform.

Java EE 7 Tutorial Part I Introduction to Chapter 1th Overview of section 1.8 Java Platform Java EE 7 API, Standard Edition 7