activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <>
Subject [jira] Commented: (AMQNET-201) WCF binding to support request reply message exchange
Date Mon, 07 Feb 2011 23:14:57 GMT


Jim Gomes commented on AMQNET-201:

I don't see anything inherently wrong with modifying the Apache.NMS.WCF provider to support
a request/reply message exchange.  The link that was referenced in AMQNET-126 is somewhat
dated, and I think newer WCF will easily support request/reply.  However, I am not a WCF user,
so this is in an area that I can't help much.  I've done some searches and there are lots
of blogging examples for this.  One such blog of interest may be the following:

Hopefully, there's smoeone interested in submitting a patch to support request/reply in the
Apache.NMS.WCF provider.

> WCF binding to support request reply message exchange
> -----------------------------------------------------
>                 Key: AMQNET-201
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: WCF
>    Affects Versions: 1.1.0
>            Reporter: Mark Pollack
>            Assignee: Jim Gomes
>            Priority: Minor
> I remember a while back there was some discussion on a JIRA issue where there was an
explicit decision not to implement the request reply message exchange pattern in the WCF binding.
 I think this is not the correct decision.  Request/Reply is a natural interaction for messaging
systems, though clearly not the default.  Implementation options are to use a temporary queue
as the return destination or to setup a standard queue but create a message listener with
a selector.   Just for reference the TIBCO WCF binding supports request reply message exchange.
 A customer driven motivation behind this is that usually everyone creates request/reply endpoints
over http transport in WCF. When they want to switch transports to messaging they discover
(in MSMQ case) that they can't and would have to redesign their entire web services design
to accomodate using JMS transport.  This is simply not needed.  Please reconsider and let's
discuss more.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message