Table of Contents

OSS/J Functional APIs alignment

• SOA Enablement (aka Summer/winter) Release and other releases in 2007:
  • OSS Common API v 1.5 (or Maintenance 5)
  • DG 2.0 (DG 2.0 is under review until end of Feb 2008)
  • Specificatrion aligned with J2SE 1.4, RI and TCK using JDK 5 (without usage of Java SE 5 specific features like annotations)
  • Specificatrion aligned with J2EE 1.4, RI and TCK using JavaEE 5 SDK (without usage of Java EE 5 specific features)
  • Java AVK for the enterprise 5

OSS/J Functional APIs checklist

• extend/inherit from the current OSS Common API Specs
• extend/inherit from the current OSS Common API RI
• the RI must pass the current OSS Common API TCK. Test results shall be posted under the "Documents & Files" section of the jsrXXX-public java.net project.
• the RI must pass the Jsr TCK. Test results shall be posted under the "Documents & Files" section of the jsrXXX-public java.net project.
• the RI must pass the JavaEE AVK (static and dynamic tests). Test results shall be posted under the "Documents & Files" section of the jsrXXX-public java.net project.
• all documents must follow the naming convention
• a Questionnaire for Qualified Products of the API (clients) is provided. The questionnaire shall at least include the "General" questions and follow the following format.
• all current source code and draft/stable documents (editable) are under the private java.net project. (assuming http://tmforum.org/ossj/downloads is the repository for public code).
• The private project under java.net shall provide all the necessary instructions to build and package the API. (example)
• the API bundle must follow the CraftingReleaseBundles (Bundle names, etc) and:
  • CraftingTheAPISpecification
  • CraftingTheAPIReferenceImplementation
  • CraftingTheAPITCKSpecification
• the three Integration Profiles must be supported:
  • Java (Specs, RI, TCK)
  • XML/JMS (Specs, RI, TCK)
  • WS (Specs, RI, TCK)
• the javadoc must be available online under the public project (including links to OSS Common API) under the url https://jsrXXX-public.dev.java.net/nonav/javadocs/x.Y/index.html where XXX is the JSR number and x.y the version number of the API (example [[https://jsr144-public.dev.java.net/nonav/javadocs/1.5/index.html[jsr144]], See jsr144-public project content as example)
• the XML Schema and WSDL must be available online at their respective Namespace location (please contact TMForum (Antonio or Vincent) for information)