+

Search Tips   |   Advanced Search

Open source software APIs

The WebSphere Application Server product includes a variety of open source software packages.

The specific version provided by the product might vary over time. To understand what version is currently provided, a developer can extract the META-INF/MANIFEST.MF file from the JAR files in the plugins or dev directory and look for an Export-Package: directive. The version of each package is listed in this directive.


Open source software usable by applications

Open Source Software Documentation
Apache Axiom Specific usage outlined in the Information Center, all other usage is not supported.
Apache Axis2 Specific usage outlined in the Information Center, all other usage is not supported.
Apache Commons Logging See topic Jakarta Commons Logging
Apache OpenJPA See the Apache OpenJPA User's Guide. A copy of this document is included with the Information Center.
Apache Aries Specific usage outlined in the Information Center, all other usage is not supported.
Apache Wink See topic End-to-end paths for web services - RESTful services
Apache WSIF See topic Web Services Invocation Framework (WSIF)
Codehaus Jackson See topic Use Jackson with plain old Java objects (POJOs)
EclipseLink See the EclipseLink Documentation Center. Note that only the EclipseLink implementation of the JPA 2.1 specification is provided with WAS. Usage of extensions that are commonly packaged with EclipseLink, such as Moxy, JPARS, and DBWS, are not supported.


Open source software not intended for direct application use

Some of the open source software included in the product is not intended for direct application use. This might be for a variety of reasons such as the package is not included entirely or it has been modified with WAS specific behaviors. Applications that want to use these packages or want to use different versions of the open source software listed can override the WAS included open source packages with their own. This requires packaging the open source software in the application and setting the classloader policies of the module and application to load classes from the parent last.

This is the list of software not intended for direct application use:

  • WAS detailed system requirements