|
||||||||||
PREV NEXT | FRAMES NO FRAMES |
See:
Description
Parsing | |
javax.xml.parsers | Provides classes allowing the processing of XML documents. |
org.xml.sax | SAX (Simple API to XML) is an event-driven parser API, which supports most of the widely available XML parsers. |
org.xml.sax.helpers | This package contains simple "helper" classes which can help programmers get started using the SAX APIs. |
Object Model | |
org.w3c.dom | The Document Object Model (DOM) is a Recommendation of the World Wide Web Consortium, defining programming interfaces for XML (and, optionally, HTML) documents. |
This library provides core functionality necessary in most Java based applications of the Extensible Markup Language (XML) 1.0.
Both the parsing and object model APIs have an API structure consisting of an interface (currently SAX 1.0 and the DOM Level 1 core, respectively) and the JAXP APIs have an API structure consisting of abstract classes providing a thin layer for pluggability of parsers.The reference implementation of the above packages is currently in the com.sun.xml.* portion of the Java package namespace.
For example, Extensible Stylesheet Language (XSL) provides a way to translate XML into other XML structures, including ones which are legal HTML or which use "flow objects" to support publication quality rendering. (HTML can not support that quality of document rendering.) A package supporting the transformation parts of XSL could be useful in many environments, including XML document servers. A package supporting "flow/formmating" objects from the XSL specification would be useful where high quality rendering was needed, including publishing applications with "what you see is what you get" (WYSIWYG) editing. Some services such as WebDAV might use XML internally, and not expose it.
Other examples of XML-based services include support for XML based linking (XPointer/XLink), a variety of services supporting integration with relational or object databases, specialized vertical market toolsets, and messaging frameworks. Messaging frameworks could include support for XML-based data marshaling, asynchronous messaging systems such as the Java Messaging Service (JMS), and synchronous messaging systems (categorized as "Remote Procedure Calls", RPCs) including those constructed directly on top of HTTP/HTTPS messaging.
Applications may have server side components, client side ones, or both. Web based server side components will often be built using Java Servlets or JavaServer Pages.
Another category of applications is developer tools, perhaps supporting database integration or providing a better coupling between object level modeling (e.g., with UML) and XML DTDs/Schemas.
|
||||||||||
PREV NEXT | FRAMES NO FRAMES |