You can create applications that use Service Component Architecture (SCA) OASIS specifications to asynchronously run request-response services.
To learn about asynchronous invocations of SCA services, see the SCA OASIS Java Common Annotations and APIs specification. For a list of common annotations in SCA OASIS specifications, see http://docs.oasis-open.org/opencsa/sca-j/javadoc/index.html.
An SCA client and an SCA service have independent capabilities for asynchronous invocation which can be intermixed. This means that a client can synchronously run an asynchronous service or asynchronously run a synchronous service. Typically, a client asynchronously runs an asynchronous service.
When developing an asynchronous service and client, consider the following:
Topics in the procedure cover developing SCA services and clients that run asynchronously.
Deploy the SCA composites in a business-level application.
For SCA OASIS applications, an sca-contribution.xml file is required for deployable composites in the META-INF/ directory, and not in a subdirectory.