|
|
|
|
Use a Service Activator to receive asynchronous client requests and messages. On receiving a message, the Service Activator locates and invokes the necessary business methods on the business service components to fulfill the request asynchronously.
|
|
|
This section explains how to use features of the JMS API to achieve the level of reliability and performance your application requires. Many people choose to implement JMS applications because they cannot tolerate dropped or duplicate messages and require
|
|
|
A requestor is a special object that converts a message exchange into an RPC style call. Under the covers, a requestor sends a message to a queue and waits for a reply from a temporary queue. The ReplyTo field in the message is set to the temporary queue
|
|
|
Messaging provides high-speed, asynchronous, program-to-program communication with guaranteed delivery and is often implemented as a layer of software called Message Oriented Middleware (MOM).
|
|
|
Sometimes something that appears trivial turns out to be a lot more involved. Doing JMS request/reply from an EJB is such a case. Let's take a look...
|
|
|
To send and receive messages through the JMS interface, an application must first create a connection to the BPC.cellname.Bus, create a session, then generate message producers and consumers.
|
|
|
A temporary destination can only be consumed by the connection that created it.The life span of temporary destinations is only for the duration of the connection where they are created.When you close the connection that has a temporary destination, the de
|
|
|
The simplest solution is to use Camel as a Spring Remoting provider which allows you to hide all the JMS API from your business logic and letting Camel provide the request/response handling code for you.However if you wish to write the JMS client code you
|
|
|
Sending messages with JMS between app servers?
|
