Messaging Scenarios Not Supported by the JMS Control

This topic describes specific messaging scenarios that are not supported by the JMS control.

To learn more about WebLogic Workshop controls, see Controls: Using Resources from a Web Service.

To learn more about the JMS control, see JMS Control: Using Java Message Service Queues and Topics from Your Web Service.

# Unsupported Scenarios

The JMS specification supports a wide variety of messaging scenarios. Some scenarios that are possible in standalone applications are not possible in the WebLogic Workshop environment due to the nature of web services.

The messaging scenarios in the following section are not supported by the JMS control. For descriptions of messaging scenarios that are supported by the JMS control, see Messaging Scenarios Supported by the JMS Control.

## Receive Unsolicited Messages from a Queue

A web service may not, via a JMS control, specify a receive queue and subsequently receive unsolicited messages from that queue.

A web service must be performing work on behalf of a specific client and, in asynchronous situations, as part of a specific conversation. When an unsolicited messages is received from a queue, it is not possible for the JMS control to determine the appropriate conversation or client with which to correlate unsolicited incoming messages.

Note: You may receive unsolicited messages in a web service, but the web service must be a direct JMS client (i.e. not using a JMS control for the queue in question). To learn how to use JMS directly, please consult the WebLogic Server documentation topic "Programming WebLogic JMS".

Related Topics

Overview: Messaging Systems and JMS

Messaging Scenarios Supported by the JMS Control