Standardizing Java (tm) use within an SCA domain for SOA

Completed:

The Technical Committee was closed by TC Administration on 29 April 2016 and is no longer active.
Archives of its work remain publicly accessible and are linked from this page. OASIS appreciates the efforts of all those who participated in this TC.

The SCA-J TC defines the Java (tm) language binding for SCA components based on the SCA Assembly specification. The specifications include a client and implementation specification, a common annotations specification, an EJB binding specification and the J2EE integration specification.

Published Committee Draft Specifications

• Service Component Architecture SCA-J Common Annotations and APIs Specification Version 1.1 CSD05
• Service Component Architecture POJO Component Implementation Specification Version 1.1 CSD03
• Service Component Architecture EJB Session Bean Binding Specification Version 1.1 CD02
• Service Component Architecture POJO TestCases Specification Version 1.1 CSD01
• Service Component Architecture POJO Test Assertions Specification Version 1.1 CSD01

XSD Schemas

• SCA-J Schema Version 1.1 CD04
• POJO Schema Version 1.1 CD02
• POJO Contribution Schema Version 1.1 CD02
• EJB Binding Schema Version 1.1 CD02

Java API Packages

• Compiled SCA CAA Java API Jar CD04
• Downloadable SCA CAA API JavaDoc CD04(zip)
• Online SCA CAA API JavaDoc CD04

Maven Repository for SCA-J API Jar

See the repository definition for the OASIS SVN repository (repository id is oasis.svn) in the parent POM of any SCA Test Suite. For example, see http://tools.oasis-open.org/version-control/browse/wsvn/sca-j/TestCases_POJO_CI/pom.xml

Artifacts License

• Artifacts license file

Public Comments List

• http://lists.oasis-open.org/archives/sca-j-comment/

Issues List:

• http://www.osoa.org/jira/browse/JAVA

Source Code Repository:

• API and Annotations
• Common Annotations and APIs Test Cases
• POJO Component Test Cases

---

Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.