Even that is not sufficient since we need a mechanism
to co-relate request and response messages. This can be done by setting the
JMS correlation id (even though we don't demonstrate this in our sample).
servicemix-jms as provider: A sample servicemix-jms provider component
configuration is shown as follows:
endpoint="myProvider"
role="provider"
soap="true"
???
Access Web Services Using the JMS Channel
[ 206 ]
destinationStyle="queue"
jmsProviderDestinationName="queue/B"
connectionFactory="#connectionFactory" />
The following table lists out the main attributes used to configure the
servicemix-jms component in the provider role:
Attribute Name Type Description Mandatory or Not
service QName Service name of the exposed
endpoint.
Mandatory.
endpoint String Endpoint name of the exposed
endpoint.
Mandatory.
role String Whether a consumer or a
provider.
Mandatory. Value
should be provider.
soap boolean If it is true, the component will
parse the SOAP envelope and
pass the contents to the NMR.
Not Mandatory.
Default value is false.
Pages:
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293