Hi Roberto,

In addition to setting the RESPONSE property to true, you also need to set
the To header to the value of the ReplyTo header (or at least you should
remove the To header from the message). Otherwise messages will be sent in a
loop. Have a look at [1] for a sample which shows how to do this.

Thanks,
Hiranya

[1] -
http://wso2.org/project/esb/java/2.1.3/docs/samples/message_mediation_samples.html#Sample5


On Fri, Mar 12, 2010 at 5:16 PM, Paul Fremantle <p...@wso2.com> wrote:

> Roberto
>
> The way to do this is as I described, with one more twist.
>
> 1. There is no out sequence in your model
> 2. The inSequence does the work including creating your output XML.
> 3. You replace the message body with the XML you want (or modify the
> incoming XML)
> 4. You set RESPONSE=True as described
> 5. You send.
>
> Paul
>
>
> On 12 March 2010 11:40, Cappa Roberto <
> roberto.ca...@guest.telecomitalia.it> wrote:
>
>> This is my problem:
>>
>> I have to receive a SOAP packet, doing some manipulation (omitted in my
>> preceding example, wich they are not important, like storage ecc..), after I
>> don't want to send anywere my packet, I simply want to give response  to
>> client a predefined data, constructed in the outSequence.
>>
>> Thanks
>>
>> ________________________________________
>> Da: carbon-dev-boun...@wso2.org [carbon-dev-boun...@wso2.org] per conto
>> di Paul Fremantle [p...@wso2.com]
>> Inviato: venerdì 12 marzo 2010 12.26
>> A: carbon-dev
>> Oggetto: Re: [Carbon-dev] R: ESB: avoinding send but executing outSequence
>>
>> Roberto
>>
>> Please explain what you are trying to do! I don't think I understand what
>> you are trying to acheive here - what is your use case?
>>
>> Paul
>>
>> On 12 March 2010 11:23, Cappa Roberto <
>> roberto.ca...@guest.telecomitalia.it<mailto:
>> roberto.ca...@guest.telecomitalia.it>> wrote:
>> I don't understand. I don't want to send my message in any way.
>>
>> My test proxy is:
>>
>> <syn:proxy xmlns:syn="http://ws.apache.org/ns/synapse";
>> name="Soap2GetProxy2" transports="https,http" statistics="disable"
>> trace="disable" startOnLoad="true">
>>  <syn:target>
>>     <syn:inSequence>
>>        <syn:property name="RESPONSE" value="true" />
>>        <syn:send />
>>     </syn:inSequence>
>>     <syn:outSequence>
>>        <syn:log>
>>           <syn:property name="OUTSEQ" value="OUTSEQ" />
>>        </syn:log>
>>        <syn:send />
>>     </syn:outSequence>
>>  </syn:target>
>> </syn:proxy>
>>
>>
>> If I use the property you have suggested, the outSequence log is never
>> executed, but the call remains appended. Also, what is the sense of <send>
>> in inSeq if no endpoint is defined?
>>
>>
>> Thnaks
>>
>> ________________________________________
>> Da: carbon-dev-boun...@wso2.org<mailto:carbon-dev-boun...@wso2.org> [
>> carbon-dev-boun...@wso2.org<mailto:carbon-dev-boun...@wso2.org>] per
>> conto di Paul Fremantle [p...@wso2.com<mailto:p...@wso2.com>]
>> Inviato: venerdì 12 marzo 2010 11.49
>> A: carbon-dev
>> Oggetto: Re: [Carbon-dev] ESB: avoinding send but executing outSequence
>>
>> Are you trying to just respond directly from the ESB?
>> Just add
>>
>> <property name="RESPONSE" value="true"/>
>>
>> in your sequence before you <send/> and the message will be used as the
>> service response.
>>
>> Paul
>>
>>
>>
>> On 12 March 2010 10:12, Cappa Roberto <
>> roberto.ca...@guest.telecomitalia.it<mailto:
>> roberto.ca...@guest.telecomitalia.it><mailto:
>> roberto.ca...@guest.telecomitalia.it<mailto:
>> roberto.ca...@guest.telecomitalia.it>>> wrote:
>> Hi, is there a way to avoid sending the message in the inSequence but
>> executing the outSequence? I'm trying with </drop> in the inSequence, but in
>> this case the outSequence is not executed.
>>
>> Thanks
>> _______________________________________________
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org<mailto:Carbon-dev@wso2.org><mailto:
>> Carbon-dev@wso2.org<mailto:Carbon-dev@wso2.org>>
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>>
>> --
>> Paul Fremantle
>> CTO and Co-Founder, WSO2
>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>
>> Office: +44 844 484 8143
>> Cell: +44 798 447 4618
>>
>> blog: http://pzf.fremantle.org
>> twitter.com/pzfreo<http://twitter.com/pzfreo><http://twitter.com/pzfreo>
>> p...@wso2.com<mailto:p...@wso2.com><mailto:p...@wso2.com<mailto:
>> p...@wso2.com>>
>>
>> wso2.com<http://wso2.com><http://wso2.com> Lean Enterprise Middleware
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org<mailto:Carbon-dev@wso2.org>
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>>
>> --
>> Paul Fremantle
>> CTO and Co-Founder, WSO2
>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>
>> Office: +44 844 484 8143
>> Cell: +44 798 447 4618
>>
>> blog: http://pzf.fremantle.org
>> twitter.com/pzfreo<http://twitter.com/pzfreo>
>> p...@wso2.com<mailto:p...@wso2.com>
>>
>> wso2.com<http://wso2.com> Lean Enterprise Middleware
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> Office: +44 844 484 8143
> Cell: +44 798 447 4618
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> _______________________________________________
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to