By "non-ActiveMQ dynamic queue" I mean I am not using an ActiveMQ broker but rather a broker from another vendor. The vendor's JMS implementation supports dynamic queues, but it doesn't provide the "create the dynamic queue if it doesn't exist on jndi lookup" feature. I have already configured the broker to allow dynamic queue creation. However, it appears CXF does not provide a way for me to tell it to invoke session.createQueue for the destination.
smx-jms (http://servicemix.apache.org/servicemix-jms.html) uses the properties "jmsProviderDestinationName" and "destinationStyle" to trigger this behavior (as opposed to jndiDestinationName). I would like to be able to add attributes for these properties to the cxf jms:address schema in the wsdl to trigger this behavior. Again, it is the user's responsibility to ensure the broker is configured to support dynamic queue creation. Does that make sense? Should I open a JIRA for this issue? - Ron Ulhas Bhole wrote: > > Hi Ron, > > I don't get what you mean by non-ActiveMQ dynamic queue? Do you mean > standard JMS queue (not the dynamic one) If that's the case CXF JMS > transport do not try to create the JMS queue on the broker if it doesn't > exists.(unless you use dynamicQueues on ActiveMQ) > > By all means it can be done with the enhancement but the main problem I > see is some of the Message Broker requires additional privileges to > create queues some may need you to use their own interface to create > queue by admin privileges (I don't know about many JMS brokers but it > may be the case in some products). > > Regards, > > Ulhas Bhole > > rgavlin wrote: >> 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 >> > > ---------------------------- > IONA Technologies PLC (registered in Ireland) > Registered Number: 171387 > Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland > > -- View this message in context: http://www.nabble.com/CXF-Service-w-JMS-Transport---non-ActiveMQ-Dynamic-Queue-tp18479791p18485819.html Sent from the cxf-user mailing list archive at Nabble.com.
