I was hoping you'd say - 'just run widget x!' I think we'll end up wrapping NMS in a service, with a configuration file to define which queue on the MSMQ side should talk to which queue on the AMQ side, and so on.
Having researched MSMQ for most of the day today it's very sad to see that it provides very little interoperability outside the Microsoft space. James.Strachan wrote: > > On 5/2/07, notacrime <[EMAIL PROTECTED]> wrote: >> >> We're faced with having to integrate with a Microsoft application that >> uses >> MSMQ as it's messaging bus. We use AMQ, and STOMP, and would like to >> create >> a bridge between the MSMQ queues and AMQ. Is there an easy way to do >> this? > > NMS does have support for MSMQ (though it could use a little work to > polish some of the rough edges) so an NMS bridge could be created to > go from one NMS provider to another (e.g. MSMQ <-> ActiveMQ or MSMQ > <-> Stomp etc.) > > -- > James > ------- > http://macstrac.blogspot.com/ > > -- View this message in context: http://www.nabble.com/MSMQ---ActiveMQ-Bridge--tf3683635s2354.html#a10299368 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
