Skip to content

List of XML API’S

August 5, 2009
XML API¬タルS For Database
Databases and XML offer complementary functionality for storing data. Databases store data for efficient retrieval, whereas XML offers an easy information exchange that enables interoperability between applications. To take advantage of XML’s features we can convert database tables into XML documents. We can then use XML tools with such documents for further processing. For example, XML documents can be presented as HTML pages with XSLT stylesheets, can be searched with XML-based query languages such as XQL, can be used as a data-exchange format, and so on. However, converting a database into an XML document is an expensive approach, one that requires not only the initial cost of conversion but also the subsequent costs of synchronizing both information sources.
DOM: Document Object Model
DTD: document type definition
SAX: Simple API for XML
XML: Extensible Markup Language
XQL: XML Query Language
XSL: Extensible Stylesheet Language
XSLT: XSL Transformations
XT: An XSLT processor
Overview of the SAX and DOM APIs
SAX is an event-based API for XML, the SAX parser reports events such as the start and end of elements to the application as it walks over the document. Because the parser reports events as it visits different parts of the document, it does not have to build any internal structure. That reduces the strain on system resources, which makes the parser attractive for large documents. For XML documents received as continuous streams, an event-based API is the only choice.
The DOM API, on the other hand, follows a treelike construct. Elements have parent-child relations with other elements. With this API, the parser builds an internal structure such that an application can navigate it in a treelike fashion. DOM allows an application to have random access to the tree-structured document at the cost of increased memory usage.
Java API¬タルS Related to XML
JAXM (Java API for XML Messaging)
The Java API for XML Messaging (JAXM) enables applications to send and receive document-oriented XML messages. JAXM implements Simple Object Access Protocol (SOAP) 1.1 with Attachments messaging so that developers can build, send, receive, and decompose messages for their applications.

A developer uses JAXM when there is a need to send and/or receive XML-based messages across a network. This is useful when you need to create, manipulate, or process the contents of the XML message or leverage the structure of a complex XML document.

If the sole intention of sending a message is to exchange a small amount of data that is more easily represented with Java technology’s standard types, JAX-RPC may be more appropriate than JAXM.
JAXP (Java API for XML Processing)
The Java API for XML Processing (JAXP) enables applications to parse, transform, validate and query XML documents using an API that is independent of a particular XML processor implementation. JAXP provides a pluggability layer to enable vendors to provide their own implementations without introducing dependencies in application code.  Using this software, application and tool developers can build fully-functional XML-enabled Java applications for e-commerce, application integration, and web publishing.
JAXR (Java API for XML Registries)
The Java API for XML Registries (JAXR) gives you a uniform way to use business registries that are based on open standards (such as ebXML) or industry consortium-led specifications
JAX-WS (Java API for XML Web Services)
JAX-WS is a fundamental technology for developing SOAP based and RESTful Java Web services. JAX-WS is designed to take the place of JAX-RPC in Web services and Web applications.
JAX-WSA (Java API for XML Web Services Addressing)
The Java API for XML Web Services Addressing 1.0 (JAX-WSA) specification [1] defines APIs and a framework to enable the transport neutral mechanisms to address Web services and messages. These mechanisms are defined by the W3C WS-Addressing Core 1.0 Candidate Recommendation, W3C WS-Addressing 1.0 – SOAP Binding Candidate Recommendation and W3C WS-Addressing 1.0 – WSDL Binding Working Draft specifications
One Comment leave one →
  1. jimmyzhang permalink
    December 2, 2009 2:09 am

    you may also want to check out vtd-xml, the latest and most advanced xml processing model


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: