overview7.html

j2eePDF格式的电子书

The JavaBeans Activation Framework (JAF) is included because JavaMail uses it. It 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.
</p>
<a name="wp82767"> </a><h3 class="pHeading2">
Java API for XML Processing
</h3>
<a name="wp82770"> </a><p class="pBody">
The Java API for XML Processing (JAXP) supports the processing of XML documents using Document Object Model (DOM), Simple API for XML Parsing (SAX), and XML Stylesheet Language Transformation (XSLT). JAXP enables applications to parse and transform XML documents independent of a particular XML processing implementation.
</p>
<a name="wp82771"> </a><p class="pBody">
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 of XSL processor from within your application and supports the W3C schema. You can find information on the W3C schema at this URL: <code class="cCode">http://www.w3.org/XML/Schema</code>.
</p>
<a name="wp82772"> </a><h3 class="pHeading2">
Java API for XML Registries
</h3>
<a name="wp82773"> </a><p class="pBody">
The Java API for XML Registries (JAXR) lets you access business and general-purpose registries over the Web. JAXR supports the ebXML Registry/Repository standards and the emerging UDDI specifications. By using JAXR, developers can learn a single API and get access to both of these important registry technologies. 
</p>
<a name="wp82774"> </a><p class="pBody">
Additionally, businesses submit material to be shared and search for material that others have submitted. Standards groups have developed schemas for particular kinds of XML documents, and two businesses might, for example, agree to use the schema for their industry's standard purchase order form. Because the schema is stored in a standard business registry, both parties can use JAXR to access it.
</p>
<a name="wp82775"> </a><h3 class="pHeading2">
Java API for XML-Based RPC
</h3>
<a name="wp82776"> </a><p class="pBody">
The Java API for XML-based RPC (JAX-RPC) uses the SOAP standard and HTTP so client programs can make XML-based remote procedure calls (RPCs) over the Internet. JAX-RPC also supports WSDL so you can import and export WSDL documents. With JAX-RPC and a WSDL, you can easily interoperate with clients and services running on Java-based or non-Java-based platforms such as .NET. For example, based on the WSDL document, a Visual Basic .NET client can be configured to use a Web service implemented in Java technology or a Web service can be configured to recognize a Visual Basic .NET client. 
</p>
<a name="wp82777"> </a><p class="pBody">
JAX-RPC relies on the HTTP transport protocol. Taking that a step further, JAX-RPC lets you create service applications that combine HTTP with a Java technology version of the Secure Socket Layer (SSL) and Transport Layer Security (TLS) protocols to establish basic or mutual authentication. SSL and TLS ensure message integrity by providing data encryption with client and server authentication capabilities. 
</p>
<a name="wp83134"> </a><p class="pBody">
Authentication is a measured way to verify whether a party is eligible and able to access certain information as a way to protect against the fraudulent use of a system and/or the fraudulent transmission of information. Information transported across the Internet is especially vulnerable to being intercepted and misused, so configuring a JAX-RPC Web service to protect data in transit is very important. 
</p>
<a name="wp82779"> </a><h3 class="pHeading2">
SOAP with Attachments API for Java
</h3>
<a name="wp82780"> </a><p class="pBody">
The SOAP with Attachments API for Java (SAAJ) is a low-level API upon which JAX-RPC depends. It enables the production and consumption of messages that conform to the SOAP 1.1 specification and SOAP with Attachments note. Most developers will not use the SAAJ API, but will use the higher-level JAX-RPC API instead. 
</p>
<a name="wp80338"> </a><h3 class="pHeading2">
J2EE Connector Architecture
</h3>
<a name="wp80341"> </a><p class="pBody">
The J2EE Connector architecture is used by J2EE tools vendors and system integrators to create resource adapters that support access to enterprise information systems that can be plugged into any J2EE product. A <em class="cEmphasis">resource adapter</em> is a software component that allows J2EE application components to access and interact with the underlying resource manager. Because a resource adapter is specific to its resource manager, there is typically a different resource adapter for each type of database or enterprise information system.
</p>
<a name="wp83123"> </a><p class="pBody">
JAX-RPC and the J2EE Connector Architecture are complementary technologies for enterprise application integration (EAI) and end-to-end business integration. 
</p>
<a name="wp83124"> </a><p class="pBody">
The J2EE Connector Architecture also provides a performance-oriented, secure, scalable, and message-based transactional integration of J2EE-based Web services with existing EISs that can be either synchronous or asynchronous. Existing applications and EISs integrated through the J2EE Connector Architecture into the J2EE platform can be exposed as XML-based Web services using JAX-RPC and J2EE component models. 
</p>
<a name="wp79994"> </a><h3 class="pHeading2">
Java Authentication and Authorization Service
</h3>
<a name="wp79996"> </a><p class="pBody">
The Java Authentication and Authorization Service (JAAS) provides a way for a J2EE application to authenticate and authorize a specific user or group of users to run it.
</p>
<a name="wp79997"> </a><p class="pBody">
JAAS is a Java programing language version of the standard Pluggable Authentication Module (PAM) framework that extends the Java 2 Platform security architecture to support user-based authorization. 
</p>
<a name="wp79998"> </a><h3 class="pHeading2">
Simplified Systems Integration
</h3>
<a name="wp79999"> </a><p class="pBody">
The J2EE platform is a platform-independent, full systems integration solution that creates an open marketplace in which every vendor can sell to every customer. Such a marketplace encourages vendors to compete, not by trying to lock customers into their technologies but by trying to outdo each other by providing products and services that benefit customers, such as better performance, better tools, or better customer support. 
</p>
<a name="wp80000"> </a><p class="pBody">
The J2EE APIs enable systems and applications integration through the following:
</p>
<div class="pSmartList1"><ul class="pSmartList1">
<a name="wp80001"> </a><div class="pSmartList1"><li>Unified application model across tiers with enterprise beans</li></div>
<a name="wp80002"> </a><div class="pSmartList1"><li>Simplified response and request mechanism with JSP pages and servlets</li></div>
<a name="wp80003"> </a><div class="pSmartList1"><li>Reliable security model with JAAS</li></div>
<a name="wp80004"> </a><div class="pSmartList1"><li>XML-based data interchange integration with JAXP</li></div>
<a name="wp80005"> </a><div class="pSmartList1"><li>Simplified interoperability with the J2EE Connector Architecture</li></div>
<a name="wp80006"> </a><div class="pSmartList1"><li>Easy database connectivity with the JDBC API</li></div>
<a name="wp80007"> </a><div class="pSmartList1"><li>Enterprise application integration with message-driven beans and JMS, JTA, and JNDI</li></div>
</ul></div>
<a name="wp80008"> </a><p class="pBody">
You can learn more about using the J2EE platform to build integrated business systems by reading <em class="cEmphasis">J2EE Technology in Practice</em>:
</p>
<div class="pPreformattedRelative"><pre class="pPreformattedRelative">
<a  href="http://java.sun.com/j2ee/inpractice/aboutthebook.html" target="_blank">http://java.sun.com/j2ee/inpractice/aboutthebook.html</a><a name="wp80011"> </a>
</pre></div>
    </blockquote>

   <img src="images/blueline.gif" width="550" height="8" ALIGN="BOTTOM" NATURALSIZEFLAG="3" ALT="Divider">


    <table width="550" summary="layout" id="SummaryNotReq1">
      <tr>
	<td align="left" valign="center">
	<font size="-1">
	<a href="http://java.sun.com/j2ee/1.4/download.html#tutorial" target="_blank">Download</a>
	<br>
	<a href="http://java.sun.com/j2ee/1.4/docs/tutorial/information/faq.html" target="_blank">FAQ</a>
	<br>
	<a href="http://java.sun.com/j2ee/1.4/docs/tutorial/information/history.html" target="_blank">History</a>
	</td>
        <td align="center" valign="center">
<a accesskey="p" href="Overview6.html"><img id="LongDescNotReq1" src="images/PrevArrow.gif" width="26" height="26" border="0" alt="Prev" /></a><a accesskey="c" href="J2EETutorialFront.html"><img id="LongDescNotReq1" src="images/UpArrow.gif" width="26" height="26" border="0" alt="Home" /></a><a accesskey="n" href="IntroXML.html"><img id="LongDescNotReq3" src="images/NextArrow.gif" width="26" height="26" border="0" alt="Next" /></a><a accesskey="i" href="J2EETutorialIX.html"></a>
        </td>
	<td align="right" valign="center">
	<font size="-1">
	<a href="http://java.sun.com/j2ee/1.4/docs/api/index.html" target="_blank">API</a>
	<br>
	<a href="http://java.sun.com/j2ee/1.4/docs/tutorial/information/search.html" target="_blank">Search</a>
	<br>
	<a href="http://java.sun.com/j2ee/1.4/docs/tutorial/information/sendusmail.html" target="_blank">Feedback</a></font>
	</font>
	</td>
      </tr>
    </table>

    <img src="images/blueline.gif" width="550" height="8" ALIGN="BOTTOM" NATURALSIZEFLAG="3" ALT="Divider">

<p><font size="-1">All of the material in <em>The J2EE(TM) 1.4 Tutorial</em> is 
<a href="J2EETutorialFront2.html">copyright</a>-protected and may not be published in other works
without express written permission from Sun Microsystems.</font>

  </body>
</html>