(resending...) On 10/21/2012 10:51 PM, Willem jiang wrote:
PubSub is important for the us to implement the failover mechanism. Although there could have multiple service listen to request, we can still make sure there is only one response can send it back by using the mast-salver mode.
OK, so I could use Request-Response mechanism with PubSub, but only if I use its master-slave mode and suppress a response from the other services (the slaves). Doing this would probably be outside the scope of the jms_queue sample though.
Back to the question, as CXF are now leverage the spring template and listener container to send and receive the message, we don't need to care much about the if the destination is topic or the queue. So we can still implement the Request-Response MEP with JMS using PubSub.
I'm not sure what you're referring to by "the spring template and listener container to send and receive the message", is that the architecture already shown by our jms_queue and jms_pubsub samples, or are you referring to the JMSConfig that Christian put in a while back ( http://cxf.apache.org/docs/using-the-jmsconfigfeature.html) and is in our jms_spring_config sample? And why does the new architecture make it unimportant whether a topic or queue is being used for Request-Response -- does the new architecture automatically select a master service if topic is chosen?
Thanks, Glen
