@jc:ebxml Annotation

Specifies JCX class-level annotations for the ebXML control.

Note: For most attributes, annotations can also be specified at the instance and method level. The order of precedence is:

1. JCX method level.

2. JCX instance level.

3. JCX class level.

Syntax

jc:ebxml  
   [from="initiatorID"] | [from-selector="{xquery-expression}"]
   [to="participantID"] | [to-selector="{xquery-expression}"]
   [ebxml-service-name="ebxml-service-name"]
   [ebxml-action-mode="default | non-default"]

Attributes

from

Business ID of the initiator. Must match the business ID for the trading partner as defined in the TPM repository.

from-selector

XQuery expression that selects the business ID of the initiator. To learn how to specify the initiator business ID dynamically, see "Dynamically Specifying Business IDs" in Using an ebXML Control.

Note: This attribute is not available for all methods at the control type level in the control definition file (JCX file). It only applies to the send method in the control definition or to control instance declarations in the business process file (JPD file).

Business ID of the participant. Must match the business ID for the trading partner as defined in the TPM repository.

to-selector

XQuery expression that selects the business ID of the participant. To learn how to specify the participant business ID, see "Dynamically Specifying Business IDs" in Using an ebXML Control.

Note: This attribute is not available for all methods at the control type level in the control definition file (JCX file). It only applies to the send method in the control definition or to control instance declarations in the business process file (JPD file).

ebxml-service-name

Name of an ebXML service. For initiator and participant business processes that participate in the same conversation, the settings for ebxml-service-name must be identical. This service name corresponds to the eb:Service entry in the ebXML message envelope.

ebxml-action-mode

Action mode for this ebXML control. Determines the value specified in the eb:Action element in the message header of the ebXML message, which becomes important in cases where multiple message exchanges occur within the same conversation. One of the following values:

- default—Sets the eb:Action element to SendMessage (default name).

- non-default—Sets the eb:Action element to the name of the method (on the ebXML control) that sends the message in the initiator business process. For sending a message from the initiator to the participant, this name must match the method name of the Client Request node in the corresponding participant business process. For sending a message from the participant to the initiator, the method name in the callback interface for the client callback node in the participant business process must match the method name (on the ebXML control) in the control callback interface in the initiator business process. Using non-default is recommended to ensure recovery and high availability.

If unspecified, the ebxml-action-mode is set to non-default.