[Carbon-dev] ESB: avoinding send but executing outSequence

2010-03-12 Thread Cappa Roberto
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

[Carbon-dev] R: ESB: avoinding send but executing outSequence

2010-03-12 Thread Cappa Roberto
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

Re: [Carbon-dev] R: ESB: avoinding send but executing outSequence

2010-03-12 Thread Paul Fremantle
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.itwrote: I don't understand. I don't want to send my message in any way. My

[Carbon-dev] R: R: ESB: avoinding send but executing outSequence

2010-03-12 Thread Cappa Roberto
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

Re: [Carbon-dev] R: R: ESB: avoinding send but executing outSequence

2010-03-12 Thread Paul Fremantle
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

Re: [Carbon-dev] R: R: ESB: avoinding send but executing outSequence

2010-03-12 Thread Hiranya Jayathilaka
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

[Carbon-dev] R: R: Problem adding monitored ESB server in BAM

2010-03-12 Thread Cappa Roberto
With some other tests, the problem seems to be related to the use of remote Governance Registry instead of embedded in the ESB. I'm using the last version of the ESB and the last version of GREG. Is there any workaround for the problem? Da:

Re: [Carbon-dev] [Code Review] 10/03/2010 Multiple Instances Code Review

2010-03-12 Thread Lahiru Gunathilake
Hi devs, I have done 1,2,3,5,6,7,9,11,12,13,14,15 and will do the rest of the changes, and next major thing is to do are Testing on Windows and load-testing in multi-core machine and collect data. Regards Lahiru On Thu, Mar 11, 2010 at 11:51 AM, Supun Kamburugamuva su...@wso2.comwrote:

[Carbon-dev] Branching Carbon for the Iridium (3.0.0) Release!

2010-03-12 Thread Ruwan Linton
Folks, We are planning to branch the complete carbon platform starting from the 12 noon LKT. I will send a note before starting the branching, please commit all your changes before 12 noon and keep the rest to your local machine till I announce the branching done. Please note that doing cross

Re: [Carbon-dev] [Code Review] 10/03/2010 Multiple Instances Code Review

2010-03-12 Thread Afkham Azeez
Please create JIRAs for the items that you wont be completing Thanks Azeez On Sat, Mar 13, 2010 at 12:01 AM, Lahiru Gunathilake lah...@wso2.comwrote: Hi devs, I have done 1,2,3,5,6,7,9,11,12,13,14,15 and will do the rest of the changes, and next major thing is to do are Testing on Windows

Re: [Carbon-dev] Branching Carbon for the Iridium (3.0.0) Release!

2010-03-12 Thread Ruwan Linton
Branching started! Please refrain from committing to carbon platform. Thanks, Ruwan Ruwan Linton wrote: Folks, We are planning to branch the complete carbon platform starting from the 12 noon LKT. I will send a note before starting the branching, please commit all your changes before 12