JCA JMSProcessor should have the ability to :

1) send a configurable type of JMS message (Object, text, byte) to a remote destination that is not registered in the local JNDI naming directory. Doing so probably necessitates use of proprietary Hornetq client libraries

2) optionally set the proprietary Hornetq String property that indicates to the Hornetq broker to track for possible duplicate messages to ensure idempotent operation