Use SDO 2.1.1 in SCA applications
The Service Component Architecture (SCA) implementation complies with Service Data Objects (SDO) 2.1.1 (JSR 235). Use SDO 2.1.1 in the SCA applications.
Read SDO data binding for SCA applications to better understand how to work with SDO in SCA Java clients and implementations. For more information, read about using business exceptions with SCA interfaces.
Consider installing a Rational Application Developer product with SCA Development Tools that we can use to assemble service-oriented application components based on open SCA specifications. See the Rational Application Developer documentation.
SDO is supported in both the OSOA and OASIS applications. Unless otherwise specified, the information in this topic pertains to applications for both the OSOA and OASIS specifications.
To use SDO 2.1.1 in an SCA application, access the default HelperContext programmatically in a Java or JEE (Java EE) component implementation type and then develop one or more SCA composites that use SDO following a bottom-up or top-down approach.
- Develop one or more SCA components that use SDO.
- Decide whether you are going to use a top-down or bottom-up approach to developing the SCA component implementations.
The section on top-down and bottom-up development in SDO data binding for SCA applications describes the approaches. The top-down approach is typically preferred in SCA service architecture and development.
- Use a top-down approach (starting from WSDL and XSD files) or a bottom-up approach (starting from Java files) to develop SCA composites that use SDO.
- Use a top-down approach to develop SCA composites.
- Use a bottom-up approach to develop SCA composites.
- Access the default HelperContext programmatically.
We can access the default HelperContext programmatically in a Java or Java EE component implementation type. We cannot access the default HelperContext programmatically in a Spring component implementation type.
Restriction: We cannot use array types for Java parameters. We cannot map from schema elements declared with the attribute maxOccurs="unbounded" to array types. Instead, map the element to a List, such as a List<DataObject> or List<String>.
Restriction: For the bottom-up approach, we cannot use Java collection types for either Java parameters or return types. The DataObject itself can serve as a container. For example, instead of List<DataObject> personsList where the contained DataObject instances are each a person, pass DataObject persons where the children of the root element are each a person.
- For a top-down development approach, package your WSDL and XSD files in an SCA contribution.
Packaging WSDL and XSD files in an appropriate contribution enables the component to access the schema definitions. The section on schema registration in SDO data binding for SCA applications describes the registration.
Consider packaging your WSDL and XSD files so that they can be accessed across various parts of the application from a shared in-memory instance. For details, see Implement shared scopes in SCA applications that use SDO.
- Deploy the SCA composites that use SDO in an SCA business-level application.
See topics on SCA contributions and shared scopes for information on how to establish a shared SDO scope. Otherwise, there are no special deployment considerations for applications using the SDO data binding.
Results
You have developed and deployed an SCA composite that uses SDO in a business-level application.
What to do next
Test the deployed SCA composites.
Subtopics
- (dist)(zos) SDO data binding for SCA applications
Service Data Objects (SDO) is a framework for data application development that provides an architecture and APIs. Product support for Service Component Architecture (SCA) includes an implementation of SDO 2.1.1 interfaces. To work with SDO in SCA Java clients and implementations, it is helpful to understand SDO data binding concepts.
- (dist)(zos) Use a top-down approach to develop SCA components that use SDO
Use a top-down approach that starts from WSDL or XML definition files to develop Service Component Architecture (SCA) component implementations that use Service Data Objects (SDO) 2.1.1 (JSR 235).
- (dist)(zos) Use a bottom-up approach to develop SCA components that use SDO
Use a bottom-up approach that starts from Java files to develop Service Component Architecture (SCA) component implementations that use Service Data Objects (SDO) 2.1.1 (JSR 235).
- (dist)(zos) Access default HelperContext objects in SCA applications
A Service Component Architecture (SCA) application can access a Service Data Objects (SDO) 2.1.1 HelperContext object. This object either uses DefaultHelperContext annotation or implements a (API) that uses the commonj.sdo.helper.SDO class.
- (dist)(zos) Implement shared scopes in SCA applications that use SDO
We can package the WSDL and XSD files so they can be accessed across various parts of a Service Component Architecture (SCA) application that uses Service Data Objects (SDO) 2.1.1.
Related concepts
SDO data binding for SCA applications SCA contributions Service Data Objects version 2.1.1 Data access with Service DataObjects, API versions 1.0 and 2.01
Related tasks
Use a top-down approach to develop SCA components that use SDO Use a bottom-up approach to develop SCA components that use SDO Access default HelperContext objects in SCA applications Implement shared scopes in SCA applications that use SDO Create and accessing SDO HelperContext objects Use business exceptions with SCA interfaces
Related information:
JSR 235: Service Data Objects OASIS Service Data Objects (SDO) TC