You can try embedded ActiveMQ broker with "VM connector" (i.e.vm://default) to organize cross war communication. It's a heavier than VM component, but much powerful solution.
2013/7/30 keesvandieren [via Camel] <[email protected] > > Have the same need here: > > We need to do transparent publish-subscribe from one producer to multiple > consumers across multiple war applications in one container. > > The problem I am facing: only the consumers of one of the wars is > notified, never consumers of both wars are notified. > > Is this supported by the VM component? If not, what alternate component is > recommended to use? > > More details: > I have created a test-project: > https://github.com/keesvandieren/camel-wicket-atmosphere, which shows the > problem. Readme.txt describes how to run the project and see only war being > notified. > > Thanks in advance for your time. > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/VM-queue-for-2-camel-context-tp5485770p5736464.html > To unsubscribe from VM queue for 2 camel context, click > here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5485770&code=c3RhbmlzbGF2LnR5dXJpa292QGdtYWlsLmNvbXw1NDg1NzcwfC0xMzUzMDQwNDIx> > . > NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- С уважением, Станислав Тюриков. -- View this message in context: http://camel.465427.n5.nabble.com/VM-queue-for-2-camel-context-tp5485770p5736466.html Sent from the Camel - Users mailing list archive at Nabble.com.
