uCosminexus Service Platform, Basic Development Guide
A response can be extracted from the receive queue based on either MDB or SessionBean installation. For details about how to send a normal request message, see the contents about the response queue in service invocation using an MDB (WS-R), in the manual Cosminexus Service Platform System Setup and Operation Guide.
- Organization of this subsection
- (1) Response contents
- (2) Headers and properties that are inherited
(1) Response contents
A service component sends the following contents in a response:
- Message type (StringProperty property ("CSCMessageType"))
Because the message type of the response message is XML, XML is set in the StringProperty property.
- Response message (payload (TextMessage)) from the service component
An XML (TextMessage) response message is set.
When a synchronous service component is executed and there is no response message, TextMessage without payload is sent.
(2) Headers and properties that are inherited
For the headers and properties listed below, the contents specified when the service requester sends a request for the service component are inherited by the receive queue via the response queue.
(a) Properties related to the HCSC server
- StringProperty("CSCServiceName")
This is the service name of the request destination specified by the service requester.
- StringProperty("CSCCorrelationID")
This is a correlation identifier specified by the service requester for uniquely identifying the request message from the service requester.
- StringProperty("CSCResponseFormatID")
NULL is set.
- StringProperty("CSCServiceOperationName")
This is an operation name corresponding to the service name of the request destination specified by the service requester.
(b) Headers and properties related to Cosminexus RM
- JMSReplyTo
- JMSCorrelationID
- JMSType
- JMSXGroupID
- JMSXGroupSeq
- User-specific property name
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.