THe JMS flow does not provide publish/subscribe semantics. I would use either JMS endpoints or the WS-Notification component for that.
On Fri, Dec 12, 2008 at 12:01, silvia_magrelli <[email protected]> wrote: > Hello, > I'm using servicemix 3.2.1 and I have deployed in the JBI > environment three BeanSEs. > > Each of this component have to send an info to the others in publish > subscribe modality. > ( They all subscribe to the same topic and they receive the informations form > the others filtering the own information ). > > To implement pub\sub with topic, I have used Jms-BCs with > pubSubDomain=true so according to my > understanding of the NMR, my components comunicate through a topic ( provided > by servicemix's activemq broker ) outside the NMR itself, and the binding > between each jms-BC and the relative Bean-SE is instead provided by the NMR > (using the proper configuration in the xml files and the methods provided by > servicemix API in the BeansSEs). > > What I'd like to know is if it's possible to use the JMS Flow modality of the > NMR to have my components (BeansSEs) to comunicate each other transmitting a > simple string in publish subscribe modality. > ( I work with only a JBI container and my components are > deployed inside of it) > > If the answer is yes, I'd like to know wich kind of configuration I have to > make. I understand that I have to configure the JMSFlow in servicemix.xml but > not very well > how to tell each component to communicate with the topic > that the JMS Flow will provide. > (I'm not so sure of the last assertion) > > I' d be very happy of any type of help in understanding better > that kind of flow in servicemix architecture. > Thank for any help you'd like to provide me and sorry for my bad > english. > greetings, > silvia > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
