This section lists products that have been OSS/J certified and describes what you need to do to certify your products. It also lists non certified components or products that use or plan to use OSS/J.

The OSS/J product certification process is totally open and free of charge. It relies on self-testing and self-certification by application developers. No third party testing/auditing is required.

The certification process is simple. The owner of the certified product makes the claim that the product meets the technical requirements for compatibility with a specific OSS/J API specification, publishes technical evidence in support of this claim, and assumes responsibility for the claim.

In accordance with the Java Community Process, each OSS/J API consists of a Specification, a Reference Implementation (RI), and a Technology Compatibility Kit (TCK) for each of the three integration profiles that are or will be available for OSS/J APIs:

• Tightly coupled integration with Java/JVT profile (Spec, RI, TCK)
• Loosely coupled integration with XML/JMS profile (Spec, RI, TCK)
• Cross operational boundaries integration with Web Services (Spec, RI, TCK) 

Certified Products
This category is for products that implement OSS/J APIs (server side). To be designated as a Certified product, the product shall: (1) implement at least one integration profile, (2) pass all associated TCK tests, (3) post the TCK report on a public page of the company Web site, and (4) complete the process to list the product on the OSS/J Web site.  Certification Process » 
 
Qualified Products
This category is for products that are clients of OSS/J APIs certified implementations or RIs (client side). To be designated as a Qualified product, the following is required:(1) an appropriate Questionnaire shall be answered to the satisfaction of the OSS/J Adoption Team and of the OSS/J API Spec Lead, (2) the Questionnaire shall be posted on a public page of the company Web site, and (3) the process for listing the product on the OSS/J Web site shall be completed.  Qualification Process » 

Referenced Components
Referenced Components are non-OSS/J certified software components or products that use/implement or will use/implement parts or full current final OSS/J APIs. The information about how these components take advantage of OSS/J is provided by the submitting companies and it is at their sole discretion. The OSS/J members don't verify the validity of such information.  Submission Process »

The OSS/J Certification Process for a product applies to a version and an integration profile of a single API at a time. Although OSS/J has demonstrated that OSS/J Certified products are interchangeable and interoperable at run time, the certification does not apply to integrated or end-to-end OSS solutions consisting of several products and using several APIs.