I have an application that relies heavily on JMS. For some operations, the ordering of the messages is very important. According to the JMS 1.02 Spec (4.4.10 & 4.6), message ordering is only guaranteed for a Topic's Producer within a TopicSession. If many different objects (ejbs) need to send messages on a particular topic, and I need the order of the messages honored, should I put a TopicSession and Producer into some wrapper object and then place the wrapper in JNDI, and have each object that wants to send a message on that topic lookup the wrapper in JNDI? Should I be concerned with placing a managed resource in JNDI? Is this even possible?