原文：http://docs.oracle.com/javaee/7/tutorial/doc/overview008.htm
翻译：石卓林 shizhuolin@hotmail.com
Several APIs that are required by the Java EE 7 platform are included in the Java Platform, Standard Edition 7 (Java SE 7) and are thus available to Java EE applications.
Java EE 7平台所必须的Several API包括在Java平台标准版7(Java SE 7)中,从而可用于Java EE利用.
The Java Database Connectivity (JDBC) API lets you invoke SQL commands from Java programming language methods. You use the JDBC API in an enterprise bean when you have a session bean access the database. You can also use the JDBC API from a servlet or a JSP page to access the database directly without going through an enterprise bean.
The JDBC API has two parts:
The Java SE 7 platform requires JDBC 4.1.
Java数据库连接(JDBC) API让你可以在Java程序语言方法中调用SQL命令. 当你有1个会话bean访问数据库时你可以在企业bean中使用JDBC API. 固然你也能够在servlet或jsp页面中使用JDBC API直接连接数据库而不需要通过企业bean.
JDBC API包括两部份:
Java SE 7平台要求JDBC 4.1.
The Java Naming and Directory Interface (JNDI) API provides naming and directory functionality, enabling applications to access 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 attributes with objects and searching for objects using their attributes. Using JNDI, a Java EE application can store and retrieve any type of named Java object, allowing Java EE applications to coexist 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 be customized without the need to access or change the component'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, are 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 context by using JNDI interfaces. A component can create a javax.naming.InitialContext object and look up the environment naming context in InitialContext under 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.
Java命名和目录接口(JNDI) API提供命名和目录服务功能, 使利用可以访问多个命名和目录服务,例如LDAP, DNS和NIS. 此JNDI API提供了利用和方法以处理标准目录操作, 例如对象属性访问和使用属性搜索对象. 使用JNDI,Java EE利用可以存储和恢复任意Java命名对象类型, 允许Java EE利用与很多传统利用和系统共存.
Java EE命名服务为利用客户端,企业bean和web组件访问JNDI命名提供环境. 1个命名环境允许自定义组件访问而不需要更改组件源码. 容器实现组件的环境,并将其提供给该组件作为JNDI命名上下文.
此命名环境为所有部署利用中的有效组件，模块，利用或同享等对象提供4种逻辑命名空间: java:comp, java:module, java:app和java:global. 1个Java EE组件可以访问系统命名提供的或用户定义的对象. 1些系统提供的对象的名称, 例如1个默许的JDBC数据源对象,1个默许的JMS连接工厂和默许的JTA用户事务对象, 包括被存储在java：comp命名空间中的对象. Java EE 平台允许用户定义组件为命名对象,例如企业bean,环境项, JDBC数据源对象和消息目的地.
在Java EE组件中还可以通过使用JNDI接口找到它的环境命名上下文. 1个组件可以创建1个javax.naming.InitialContext对象并且在InitialContext中的java:comp/env名称中查询环境命名上下文.组件的命名环境是直接存储在环境命名上下文或任何直接或间接的子上下文中.
The JavaBeans Activation Framework (JAF) is used by the JavaMail API. JAF provides standard services to determine the type of an arbitrary piece of data, encapsulate access to it, discover the operations available on it, and create the appropriate JavaBeans component to perform those operations.
JavaBeans活化框架(JAF)用于JavaMail API. JAF提供标准服务以肯定任意数据类型,封装其访问,发现其可用操作并且创建相应的JavaBean组件来履行这些操作.
The Java API for XML Processing (JAXP), part of the Java SE platform, supports the processing of XML documents using Document 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 you work with schemas that might otherwise have naming conflicts. Designed to be flexible, JAXP lets you use any XML-compliant parser or XSL processor from within your application and supports the Worldwide Web Consortium (W3C) schema. You can find information on the W3C schema at http://www.w3.org/XML/Schema.
用于XML处理的Java API(JAXP)是Java SE平台的1部份,其支持使用文档对象模型(DOM)处理XML文档, XML简单API(SAX)和扩大样式语言转换(XSLT). JAXP使利用程序可使用特定XML处理实现做到独立解析和转换XML文档.
JAXP也提供命名空间支持, 可以在你有可能的命名冲突时使用架构工作.通过灵活设计, JAXP让你可以在你的利用中使用任意的合适的XML解析器和XSL处理器,并且支持万维网WEB同盟(W3C)架构.你可以在W3C计划http://www.w3.org/XML/Schema中找到相干信息.
The Java Architecture for XML Binding (JAXB) provides a convenient way to bind an XML schema to a representation in Java language programs. JAXB can be used independently or in combination with JAX-WS, in which case it provides a 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.
用于XML绑定的体系结构(JAXB)为在Java语言程序中绑定XML架构到表现层提供便捷方法. JAXB可以单独使用或与JAX-WS组合使用, 它在1些案例中为web服务消息提供标准的数据绑定. 所有Java EE利用客户端容器,web容器和EJB容器支持JAXB API.
Java EE 7平台要求JAXB 2.2.
The Java API for XML Web Services (JAX-WS) specification provides support for web services that use the JAXB API for binding 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 be 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 in the same container and with the same privileges and execution context as the JAX-WS client or endpoint component with which they are associated. These message handlers have access to the same JNDI namespace as their associated component. Custom serializers and deserializers, if supported, are treated in the same way as message handlers.
The Java EE 7 platform requires JAX-WS 2.2.
用于XML Web服务的Java API(JAX-WS)规范为在WEB服务中使用JAXB绑定XML数据和Java对象提供支持. JAX-WS规范为web服务客户端访问web服务的技术实现定义客户端API.实现了企业web服务规范化的基于JAX-WS的服务服务和客户端部署描写 . EJB和Java Servlet规范也为部署提供部份描写.基于JAX-WS的利用可使用任意部署模型部署.
JAX-WS规范描写为处理消息要求和响应的消息处理程序提供支持. 在通常情况中, 这些消息处理程序在同1个容器中用相同的权限和履行上下文的JAX-WS客户端或与其关联的终端组件1起履行. 这些消息处理程序可以访问相同的JNDI命名空间及其相干组件. 如果支持自定义序列化和反序列化的话, 则以一样的方式对待消息处理程序.
Java EE 7平台要求JAX-WS 2.2.
The SOAP with Attachments API for Java (SAAJ) is 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 with Attachments note. Most developers do not use the SAAJ API, instead using the higher-level JAX-WS API.
Java中附带的SOAP API(SAAJ)是1种依赖JAX-WS的低级API. SAAJ使消息的生产和消费尊从SOAP 1.1/1.2规范和附带的SOAP注释. 多数开发人员不使用SAAJ API,反而使用高级JAX-WS API.
The Java Authentication and Authorization Service (JAAS) provides a way for a Java EE application to authenticate and authorize 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.
Java和认证服务(JAAS)为Java EE利用授权和验证运行它的特定用户或组提供方法.
JAAS是标准可插入认证模块框架的Java程序语言版本, 那些扩大的Java平台安全部系支持基于用户的认证.
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.
注解使得在Java平台中可使用编程的方式声明样式.
Java EE 7平台要求Java平台通用注解 1.2.