Prepackaged JMS function selectors
Several JMS function selectors come with the product.
The following prepackaged JMS function selectors can be used for your services.
Note that selections are filtered. If you only had one operation on an interface, for example, then the one operation function selector would be available.
| Function selector | Description |
|---|---|
| JMS function selector for simple JMS data bindings | This function selector follows the JMS standard of defining a message class with JMS data bindings for the body or payload which contains the message itself. Each subclass has a different body type. This function selector uses the JMSType property of the message to select the operation name. |
| JMS header property function selector | The default function selector returns the value
of the JMS String Property, TargetFunctionName, from the header. To
identify the JMS, MQ JMS or generic JMS messages, the default behavior
is for the import to set the JMS header property, TargetFunctionName,
to the name of the interface operation name, and the default function
selector used by the export extracts the TargetFunctionName property
from the JMS header to correctly identify the incoming message. This function selector is used within an SCA context as it is using XML in the message body, so it could be used in a module to module scenario. It is configurable with a data handler. You can specify the JMS header property used to do the map. By default, the header property is a user-defined one: TargetFunctionName. |
| JMS service gateway function selector | This function selector should be used in conjunction with a binding using the service gateway interface. It determines if the request is a one-way or two-way operation by examining the JMSReplyTo property set by the client. |
| One operation function selector | This function selector returns the one single operation that is on the interface. |
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-01-20 10:38