This subproject contains the source code for the implementation classes
of the Java Servlet and JSP APIs (packages javax.servlet).

Swing Layout Extensions goal is to make it easy to create
professional cross platform layouts with Swing. This project has
an eye towards the needs of GUI builders, such as NetBeans. This
project consists of the following pieces: * Ability to get the
baseline for components.

* Ability to get the preferred gap between components.

A new LayoutManager that utilizes both of these concepts and is tuned
toward a free-form drag and drop layout model as can be provided by GUI
builders.

SwingWorker is designed for situations where you need to have a long
running task run in a background thread and provide updates to the UI
either when done, or while processing. This project is a backport of
SwingWorker included into Java 1.6.

SwingX contains a collection of powerful, useful, and just plain fun Swing
components. Each of the Swing components have been extended, providing
data-aware functionality out of the box. New useful components have been
created like the JXDatePicker, JXTaskPane, and JXImagePanel.

The Java Service Wrapper is an application which has
evolved out of a desire to solve a number of problems
common to many Java applications:
- Run as a Windows Service or Unix Daemon
- Application Reliability
- Standard, Out of the Box Scripting
- On Demand Restarts
- Flexible Configuration
- Ease Application installations
- Logging

Trang is a command line converter for XML schema languages. The
following languages are supported:

* RELAX NG (XML syntax)
* RELAX NG compact syntax
* XML 1.0 DTDs
* W3C XML Schema

W3C XML Schema is not supported for input.

Trang can also derive a schema from XML documents.

Trang will try to build human-readable schemas; aspects of the input
schema will be preserved as much as possible (including definitions,
spreading over files, annotations, and comments).

tunctl is a tool to set up and maintain persistent TUN/TAP network
interfaces, enabling user applications access to the wire side of a
virtual nework interface. Such interfaces is useful for connecting VPN
software, virtualization, emulation and a number of other similar
applications to the network stack.

tunctl originates from the User Mode Linux project.

update-alternatives creates, removes, maintains and displays
information about the symbolic links comprising the alternatives
system. It is possible for several programs fulfilling the same or
similar functions to be installed on a single system at the same time.
For example, many systems have several text editors installed at once.
This gives choice to the users of a system, allowing each to use a
different editor, if desired, but makes it difficult for a program to
make a good choice of editor to invoke if the user has not specified a
particular preference.

Velocity is a Java-based template engine. It permits anyone to use the
simple yet powerful template language to reference objects defined in
Java code.
When Velocity is used for web development, Web designers can work in
parallel with Java programmers to develop web sites according to the
Model-View-Controller (MVC) model, meaning that web page designers can
focus solely on creating a site that looks good, and programmers can
focus solely on writing top-notch code. Velocity separates Java code
from the web pages, making the web site more maintainable over the long
run and providing a viable alternative to Java Server Pages (JSPs) or
PHP.
Velocity's capabilities reach well beyond the realm of web sites; for
example, it can generate SQL and PostScript and XML (see Anakia for more
information on XML transformations) from templates. It can be used
either as a standalone utility for generating source code and reports,
or as an integrated component of other systems. Velocity also provides
template services for the Turbine web application framework.
Velocity+Turbine provides a template service that will allow web
applications to be developed according to a true MVC model.

werken.xpath is an implementation of the W3C XPath Recommendation, on
top of the JDOM library. It takes as input a XPath expression, and a
JDOM tree, and returns a NodeSet (java.util.List) of selected
elements. Is is being used in the development of the
as-yet-unreleased werken.xslt (eXtensible Stylesheet Language) and the
werken.canonical (XML canonicalization) packages.

A Java/XML binding compiler takes as input a schema description (in
most cases an XML schema, but it may be a DTD, a RelaxNG schema,
a Java class inspected via reflection, or a database schema). The
output is a set of Java classes: * A Java bean class matching the
schema description. (If the schema was obtained via Java
reflection, the original Java bean class.)

* Read a conforming XML document and convert it into the equivalent
Java bean.

* Vice versa, marshal the Java bean back into the original XML
document.

The Web Services Description Language for Java Toolkit (WSDL4J) allows
the creation, representation, and manipulation of WSDL documents
describing services. This codebase will eventually serve as a
reference implementation of the standard created by JSR110.

Xalan is an XSLT processor for transforming XML documents into HTML,
text, or other XML document types. It implements the W3C
Recommendations for XSL Transformations (XSLT) and the XML Path
Language (XPath). It can be used from the command line, in an applet or
a servlet, or as a module in other program.

Welcome to the future! Xerces2 is the next generation of high
performance, fully compliant XML parsers in the Apache Xerces family.
This new version of Xerces introduces the Xerces Native Interface
(XNI), a complete framework for building parser components and
configurations that is extremely modular and easy to program.

The Apache Xerces2 parser is the reference implementation of XNI but
other parser components, configurations, and parsers can be written
using the Xerces Native Interface. For complete design and
implementation documents, refer to the XNI Manual.

Xerces 2 is a fully conforming XML Schema processor. For more
information, refer to the XML Schema page.

Xerces 2 also provides a partial implementation of Document Object
Model Level 3 Core, Load and Save and Abstract Schemas [deprecated]
Working Drafts. For more information, refer to the DOM Level 3
Implementation page.

Welcome to the future! Xerces2 is the next generation of high
performance, fully compliant XML parsers in the Apache Xerces family.
This new version of Xerces introduces the Xerces Native Interface
(XNI), a complete framework for building parser components and
configurations that is extremely modular and easy to program.

The Apache Xerces2 parser is the reference implementation of XNI but
other parser components, configurations, and parsers can be written
using the Xerces Native Interface. For complete design and
implementation documents, refer to the XNI Manual.

Xerces 2 is a fully conforming XML Schema processor. For more
information, refer to the XML Schema page.

Xerces 2 also provides a partial implementation of Document Object
Model Level 3 Core, Load and Save and Abstract Schemas [deprecated]
Working Drafts. For more information, refer to the DOM Level 3
Implementation page.

xinetd takes the abilities of inetd and appends additional
functionality:

- Access Control

- Prevention of 'denial of access' attacks

- Extensive logging abilities

- Clear configuration file

xml-commons is focused on common code and guidelines for xml projects.
It's first focus will be to organize and have common packaging for the
various externally-defined standards code relating to XML - things like
the DOM, SAX, and JAXP interfaces.
As the xml-commons community forms, we also hope to serve as a holding
area for other common xml-related utilities and code, and to help
promulgate common packaging, testing, documentation, and other
guidelines across all xml.apache.org subprojects.

This is xml-apis from the java-bootrapping-tools package. DO NOT
INSTALL ... THIS IS JUST FOR PACKAGING & BOOTSTRAPPING JAVA PURPOSES!!

XML Im-/Exporter is a low level library to assist you in the straight
forward process of importing and exporting XML from and to your Java
classes. All of this is designed having performance and simplicity in
mind.

XMLBeans is a tool that allows you to access the full power of XML in a
Java friendly way. It is an XML-Java binding tool. The idea is that you
can take advantage the richness and features of XML and XML Schema and
have these features mapped as naturally as possible to the equivalent
Java language and typing constructs. XMLBeans uses XML Schema to
compile Java interfaces and classes that you can then use to access and
modify XML instance data. Using XMLBeans is similar to using any other
Java interface/class, you will see things like getFoo or setFoo just as
you would expect when working with Java. While a major use of XMLBeans
is to access your XML instance data with strongly typed Java classes
there are also API's that allow you access to the full XML infoset
(XMLBeans keeps full XML Infoset fidelity) as well as to allow you to
reflect into the XML schema itself through an XML Schema Object model.

XMLBeans is a tool that allows you to access the full power of XML in a
Java friendly way. It is an XML-Java binding tool. The idea is that you
can take advantage the richness and features of XML and XML Schema and
have these features mapped as naturally as possible to the equivalent
Java language and typing constructs. XMLBeans uses XML Schema to
compile Java interfaces and classes that you can then use to access and
modify XML instance data. Using XMLBeans is similar to using any other
Java interface/class, you will see things like getFoo or setFoo just as
you would expect when working with Java. While a major use of XMLBeans
is to access your XML instance data with strongly typed Java classes
there are also API's that allow you access to the full XML infoset
(XMLBeans keeps full XML Infoset fidelity) as well as to allow you to
reflect into the XML schema itself through an XML Schema Object model.

The API interfaces are what driver developers must implement when
creating a new driver and are the interfaces that applications are
developed against. Along with the interfaces a concrete DriverManager
implementation is also provides.