Index Changes

Difference between version and version     

Back to Invoke Activity TSL, or Invoke Activity TSL Info


At line 2 changed 3 lines.
!! THIS PAGE IS UNDER CONSTRUCTION
The ''invoke'' activity sends a message exchange to a service endpoint. All invocations are synchronous, meaning the transformation process will suspend and wait for a response from the consumed endpoint before continuing process execution. It is expected, though not explicitly required, that the message parts of the exchange sent to the invoked service endpoint (declared via the "inputVariable" attribute) will have values assigned prior to invocation.
At line 15 added 1 line.
This required attribute indicates the partnerLinkType of the consumed service endpoint. Though transformation processes do not explicitly define partnerLinks, an implicit partnerLink is created when this activity is executed.
At line 18 added 1 line.
This required attribute is the name of the consumed service endpoint's role. In BPEL parlance, this would be the 'partnerRole'.
At line 21 added 1 line.
This required attribute is the name of the operation to invoke on the service endpoint.
At line 24 added 2 lines.
This attribute is the [variable declaration|VariablesTSL] for the message sent to the invoked endpoint. In the JBI environment, this is equivalent to calling MessageExchange.getInMessage(). If this attribute is not specified, the value will default to the name of the input message as specified in the operation's definition.\\
\\__NOTE:__ It is expected, though not explicitly required, that the message parts of the exchange this attribute specifies will have values assigned prior to invocation. That is, if the message exchange "input" in the example below has two parts, then two ''[transform|TransformActivityTSL]'' activities should precede the ''invoke'' activity to assign XML data to each message part.
At line 25 changed 1 line.
This attribute is the [variable declaration|VariablesTSL] for the message received from the invoked endpoint as a reply. For InOut operations in the JBI environment, this is equivalent to calling MessageExchange.getOutMessage(). For InOnly operations, the status received from the invoked endpoint will be assigned to this variable. If this attribute is not specified, the value will default to the name of the output message as specified in the operation's definition.
At line 31 added 6 lines.
The example below does not specify/indicate a endpoint provider, meaning the invoked endpoint can be provisioned by any service engine or even an external service (i.e. outside the JBI environment).
{{{
<invoke partnerLinkType="ns1:myPLTexample" roleName="partnerRole" <!-- identifies the implemented portType -->
opName="exampleOperation"
inputVariable="input" outputVariable="output"/> <!-- variable declarations -->
}}}

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-9) was last changed on 02-Apr-08 11:58 AM, -0700 by KevanSimpson