TemporaryQueue visibility and access

Question

I have a question about how an application (A) can send messages to a temporary queue created another application (B). If A is consuming messages sent by B, for which B set the ReplyTo field to a temporary queue it created, then A can grab the Destination and reply.
However, what if application C also wants to send messages to B through its temporary queue, but C hasn't received any messages from A first.
If A did a TemporaryQueue.getQueueName() and provided this name (via a config file etc) to application C, could app C then gain a handle to the B's temporary queue? Is it possible for A to serialize the temporary queue and store it where C could unserialize it and being sending to it?
All questions pertain to Sun ONE IMQ 3.5 on Linux. Thanks.

Answer 1

Temporary destinations has lifetime of its connection
on which it's created. Temporary destination names
are created internally by the JMS provider. This implies
1. You should not rely on temporary destination name
itself can indicates it's a temporary destination,
and you can't create a temporary destination by
taking name argument (no API for that)
2. A newly created temporary destination may not be
serializable due to that it contains its connection
info which may not be serializable
However, you should be able to serialize the temporary
destination object received in getJMSReplyTo unpon A
received the message sent by B, then C can deserialize
the temporary destination.