Java Reference
In-Depth Information
(SAX), and Extensible Stylesheet Language Transformations (XSLT). JAXP enables ap-
plications 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 World-
wide Web Consortium (W3C) schema. You can find information on the W3C schema at
Java Architecture for XML Binding
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 independ-
ently or in combination with JAX-WS, where it provides a standard data binding for web
service messages. All Java EE application client containers, web containers, and EJB con-
tainers support the JAXB API.
The Java EE 6 platform requires JAXB 2.2.
SOAP with Attachments API for Java
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 SOAP with Attachments note. Most developers do
not use the SAAJ API, instead using the higher-level JAX-WS API.
Java API for XML Web Services
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 spe-
cification defines client APIs for accessing web services as well as techniques for imple-
menting web service endpoints. The Implementing Enterprise Web Services specification
describes the deployment of JAX-WS-based services and clients. The EJB and Java Ser-
vlet 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 en-
dpoint component with which they are associated. These message handlers have access
to the same JNDI
java:comp/env
namespace as their associated component. Custom
