Description of problem:

• It has been observed that if we use "JMS" binding or "Camel" binding (used with JMS URI) at SwitchYard Composite Reference, and if the target queue does not exist in the container's JMS destination then SwitchYard does not complain about the absence of a queue. The issue occurs even if we try to deploy the application in FSW 6.0.0 or if SwitchYard service tries to send messages to this queue.
• On the other hand if we use Camel routes to send messages to the JMS destination then it complains as usual if the Camel route tries to send messages to a queue which does not exist. Here is the exception for an example.
  ~~~
  21:38:38,029 ERROR [org.apache.camel.processor.DefaultErrorHandler] (http-localhost/127.0.0.1:8080-11) Failed delivery for (MessageId: ID-mhussain-csb-45214-1430149501418-13-3 on ExchangeId: ID-mhussain-csb-45214-1430149501418-13-4). Exhausted after delivery attempt: 1 caught: org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: There is no queue with name CamelJMSQueue: org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: There is no queue with name CamelJMSQueue
  at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316)
  ...
  at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) [camel-core-2.10.0.redhat-60024.jar:2.10.0.redhat-60024]
  at org.switchyard.bus.camel.audit.FaultProcessor.process(FaultProcessor.java:46) [switchyard-bus-camel-1.1.1-p5-redhat-1.jar:1.1.1-p5-redhat-1]
  at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) [camel-core-2.10.0.redhat-60024.jar:2.10.0.redhat-60024]
  ...
  Caused by: javax.jms.JMSException: There is no queue with name CamelJMSQueue
  at org.hornetq.jms.client.HornetQSession.createQueue(HornetQSession.java:402)
  at org.springframework.jms.support.destination.DynamicDestinationResolver.resolveQueue(DynamicDestinationResolver.java:101)
  at org.springframework.jms.support.destination.DynamicDestinationResolver.resolveDestinationName(DynamicDestinationResolver.java:66)
  at org.springframework.jms.support.destination.JmsDestinationAccessor.resolveDestinationName(JmsDestinationAccessor.java:100)
  at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.access$000(JmsConfiguration.java:160) [camel-jms-2.10.0.redhat-60024.jar:2.10.0.redhat-60024]
  at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate$1.doInJms(JmsConfiguration.java:173) [camel-jms-2.10.0.redhat-60024.jar:2.10.0.redhat-60024]
  at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:466)
  ... 181 more
  ~~~

Version-Release number of selected component (if applicable):

• FSW 6.0.0

How reproducible:

• Always