Yes it is a good way, why doesn't it feel right to you?
In JBossMQ there is now notion where a client must be (except for an MDB) so a client (consumer or publisher can be local or remote). The Connection/Session take care of how the message are aknowledged even when they are remote.
So your client on Server 'A' could even be a remote client on Server 'C'.
Have fun - Andy
I guess the idea of "Messaging" to me seemed most natural in the form of sending a message from point A to point B and point B was waiting (listening) to receive. A remote listener did not seem as natural, but I am glad to see that this design is not a bad one necessarily. Thanks for the speedy reply.
The idea of messaging is that a message producer on Box A sends a message to a JMS server on (another) Box B which then sends the message to one or more message consumers on a Box C.
Where the boxes are doesn't matter as long as any client can connect to the JMS server.