ent beans and use the id of the bean as the
> scheme in the URI. So you could have something like mqremote:queueName and
> mqlocal:queueName if you gave the beans IDs of mqremote and mqlocal
> respectively.
>
> On 14 June 2016 at 17:46, Gabriel Soto wrote:
>
> > Hello,
> &
Hello,
We need to connect to two different JMS providers in two different
application containers:
1. A remote MQ running on WebSphere
2. A local WebSphere using the native JMS implementation
We are using Spring-only configuration.
I managed to properly connect to both containers individual
