Generally JMS ResourceAdapter only supports javax.jms.MessageListener for inflow, so it doesn't return reply message. but if we have right ConnectionFactory JNDI name which is exposed by ResourceAdapter, then we can send reply message through this ConnectionFactory and synchronize with same transaction for the inflow receiving.
One thing to note - we need to lookup Destination as well in this case. If the JMS server is remote node, Destination is supposed to be looked up from remote JNDI even if the ResourceAdapter is deployed on local node. That's a similar problem we have in JCA/JMS outbound gateway today - Destination lookup may need different JNDI properties against ConnectionFactory lookup.