dynamic_router question

[rukus]

in jboss-esb.xml:

<!-- Note that only queues that are listened to (input) require jms-provider definitions. jms-provider definitions are not required for these queues as the quickstart only notifies the queues (output): queue/qsdynamicrouter_3_Request, queue/qsdynamicrouter_1_Request, queue/qsdynamicrouter_2_Request -->

i can't understand it....
why we don't need to specify those queues??

[burrsutter]

You don't need to specify a listener/JMS provider for a queue that you are only "pushing" messages to. The listener/JMS provider comes into play when wish to respond automatically to inbound messages.

Burr

[rukus]

"burrsutter" wrote:
You don't need to specify a listener/JMS provider for a queue that you are only "pushing" messages to. The listener/JMS provider comes into play when wish to respond automatically to inbound messages.

Burr

hmm... automatically respond? Can you explain it?

[burrsutter]

The ESB via its gateways/listeners will automatically receive an inbound message to a queue. And then your service and action chain will be executed. You can then in that action chain do anything you wish to do with that message.

[rukus]

"burrsutter" wrote:
The ESB via its gateways/listeners will automatically receive an inbound message to a queue. And then your service and action chain will be executed. You can then in that action chain do anything you wish to do with that message.

hmm and where is response here?

[burrsutter]

If the client is ESB aware then the response from the ESB is handled automatically.

The quickstart call "native_client" demonstrates this. It uses a plain vanilla, non-ESB mediated WS to invoke an ESB JMS-based Service and waits for a response.

If the client is not aware of the ESB, let's say it is a VB client that uses SOAP to interact with the ESB, then the response from the ESB is handled automatically.

If the client is not aware of the ESB, let's say it is a COBOL client that drops a file in a folder which invokes the ESB Service (the ESB polls), then it you need to push out a new file to the same folder or a new folder so the COBOL application can "see" the response.

Just out the various quickstarts and you will see a number of ways to get a "response" back to the initial requestor. We've done a very good job of showing this for ESB unaware clients but we need to add more examples to that "native_client" quickstart as well.