Asankha, Thanks for the quick response.
I'm happy to wait now that I know it'll come along in the 1.0.1 release. So that I can manage expectations is there a timeframe when this is likely to appear? One other question that's related. If a reply destination is specified, is the correlation id something that needs to be set or is this managed by the endpoint? Ian. On 8/17/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote: > > Hi Ian > > For your case, you should use the property mediator to set the reply > destination name. However the 1.0 release had a bug where this property > did not propagate to the endpoint when being sent. This bug is already > fixed and will go into 1.0.1 as well as being already available in a > fresh build off the source code. Let me know if you would like a binary > of the relevant JAR file. > > asankha > > Ian Carman wrote: > > I'm trying to adapt sample 111 so that it uses a known JMS queue to > return > > the response rather than creating a temporary queue. > > > > If I add a parameter to the end of the proxy definition as follows: > > > > <parameter name="transport.jms.ReplyDestination"> > > StockQuoteResponse > > </parameter> > > > > It doesn't appear to have an affect on the JMS message sent. > > > > I've also tried to achieve the same thing using a property mediator > without > > success. > > > > I'd appreciate anyone being able to point out what I'm doing wrong or > with > > an example that might shed some light. > > > > Thanks. > > > > Ian. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
