Skip to content

JMS API

Jump to bottom
Marco Rietveld edited this page May 31, 2013 · 4 revisions

JMS Api

There are two parts to the JMS interface:

  • Queue use
  • Message structure

Queue use

The JMS service reads queues from the following queues:

KIE.SESSION
KIE.TASK

Responses to request messages from either queue will be placed on the following queue:

KIE.RESPONSE.ALL

The name of the response queue name is configurable, using the following System property:

kie.services.jms.queues.response

The JMS service uses the same JAXB object that the REST api */execute methods use:

org.kie.services.client.serialization.jaxb.JaxbCommandsRequest

Instances of this object are marshalled into XML, serialized into bytes (String.getBytes()) and placed in a JMS ByteMessage. Instances are expected to contain the necessary information (deploymentId and processInstanceId if necessary) for the commands included in the instance to be executed.

In response to a JaxbCommandsRequest, a JaxbCommandsResponse object is returned, which contains a list of JaxbCommandResponse implementation instances.

Clone this wiki locally