Clebert, are you changing the core bridge to support Artemis' internal AMQP message representation or are you implementing a bridge that uses the AMQP protocol?
Justin On Thu, Jul 27, 2017 at 1:19 PM, Clebert Suconic <clebert.suco...@gmail.com> wrote: > On Thu, Jul 27, 2017 at 2:07 PM Justin Bertram <jbert...@redhat.com> > wrote: > > > Thanks for the explanation. That seems like it would be a good use-case > > for Camel bridging between two JMS providers. > > > > Regardless I will have to fix the core bridge to load balance amqp as well. > > > > > > > Justin > > > > On Thu, Jul 27, 2017 at 12:54 PM, Clebert Suconic < > > clebert.suco...@gmail.com > > > wrote: > > > > > Check back in a week. I'm working on it. > > > > > > On Thu, Jul 27, 2017 at 1:34 PM adagys <andrius.da...@r3.com> wrote: > > > > > > > Thanks, I'll have a look at Dispatch. > > > > > > > > The use-case is a distributed ledger platform, where we have a > > > peer-to-peer > > > > network of nodes operated by different parties. Each node runs an > > Artemis > > > > broker, and maintains queues for messages to other nodes, which get > > > > forwarded using core bridges. We'd like to support a scenario where > > some > > > of > > > > the nodes run a non-Artemis AMQP broker, and it's still possible to > > > > interoperate (the non-Artemis broker might also require some > additional > > > > bridging support). > > > > > > > > For more context: > > > > https://docs.corda.net/key-concepts-ecosystem.html#network-structure > > > > <https://docs.corda.net/key-concepts-ecosystem.html# > network-structure> > > > > > > > > > > > > > > > > -- > > > > View this message in context: > > > > http://activemq.2283324.n4.nabble.com/Artemis-AMQP- > > > bridges-tp4728934p4728978.html > > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > > > > -- > > > Clebert Suconic > > > > > > -- > Clebert Suconic >
