I have a CXF Service w/JMS transport that I want to listen on a non-ActiveMQ dynamic queue. When a jndiDestinationName lookup is performed on an ActiveMQ dynamic queue, ActiveMQ creates the dynamic queue and returns it. Most other JMS providers do not seem to behave this way. Rather, when a jndiDestinationName lookup is performed on the non-ActiveMQ Dynamic Queue, a JNDI lookup error is returned rather than the dynamic queue being created.
servicemix-jms provides a property named "jmsProviderDestinationName" (as opposed to jndiDestinationName) which causes the target JMS destination to be created by the JMS provider by calling Session.createQueue. Does CXF offer a comparable property to get around this jndiDestinationName lookup problem? If not, is this something CXF would consider supporting? If so, I will open a JIRA to request the feature? See http://www.nabble.com/smx-cxf-bc-consumer-w-jms-transport-and-non-jndiDestinationName-td18475778.html for additional discussion on this topic. Thanks, - Ron -- View this message in context: http://www.nabble.com/CXF-Service-w-JMS-Transport---non-ActiveMQ-Dynamic-Queue-tp18479791p18479791.html Sent from the cxf-user mailing list archive at Nabble.com.
