Show Table of Contents
19.4. Composite Elements
Table 19.1. Composite Elements
| Name | Description |
|---|---|
|
<composite>
|
Single, top-level application element which defines a set of services, the relationships and dependencies of those services, and the linkage (if any) to services available outside the application.
|
|
<component>
|
Contains the implementation of a service and the dependencies of that service.
|
|
<service>
|
Defines the name and interface for a service. This element is used inside a component definition to declare a service and can also appear inside a composite definition to indicate that a service is visible to outside applications.
|
|
<interface.XXX>
|
The contract for a service. The type of the interface replaces 'XXX' in the definition. Supported interface types are Java and WSDL.
|
|
<binding.XXX>
|
The binding of a service. The type of the binding replaces 'XXX' in the definition. Example bindings include binding.soap and binding.camel.
|
|
<implementation.XXX>
|
The implementation of a service. The type of the implementation replaces 'XXX' in the definition. Example implementations include implementation.bean and implementation.camel.
|
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.