1 2 Previous Next 15 Replies Latest reply on Feb 3, 2014 4:59 PM by evidence01 Go to original post
      • 15. Re: Switchyard - Control JMS redelivery. Best practices
        evidence01

        On that topic, i have setup

                  ReferenceInvocation m = null;
                  try { 
                       m = putFlowInEsb.newInvocation("enqueueFlowData").setProperty("javax.jms.JMSXGroupID", flow.getGuid())
                                 .invoke(flow);
                  } catch (Exception e) {
                       e.printStackTrace();
                       
                       throw e;
                  }
        

         

        Is this the correct way to send a JMSXGroupID to the outbound JMSProducer for a JMS endpoint binding. I do see that it sets the exchanges property correctly but I was unable to see if the propagation to camel and jms took place.

         

        Basically this would remove the need for me to maintain a extra camel route after my bean just to set JMS header properties for outbound JMS message flow. I currently use   setHeader headerName="JMSXGroupID" in camel todo this.

         

        Any insight would be great since i was unable to trace Exchange property propagation to JMS.

        1 2 Previous Next