Return-Path: Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: (qmail 14305 invoked from network); 6 Apr 2009 16:49:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Apr 2009 16:49:21 -0000 Received: (qmail 17641 invoked by uid 500); 6 Apr 2009 16:49:18 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 17559 invoked by uid 500); 6 Apr 2009 16:49:17 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 17411 invoked by uid 99); 6 Apr 2009 16:49:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Apr 2009 16:49:17 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ruwan.linton@gmail.com designates 209.85.142.188 as permitted sender) Received: from [209.85.142.188] (HELO ti-out-0910.google.com) (209.85.142.188) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Apr 2009 16:49:09 +0000 Received: by ti-out-0910.google.com with SMTP id a6so2149442tib.15 for ; Mon, 06 Apr 2009 09:48:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=/KXss0Jai0bXHm+2uc3bKxTYveaMClCJ1Rl08ZTN5IY=; b=sZhoLT36HYOgDv5wcFj/DJQo472KHkrGSEPdyTJU3rCbi7sJWWhaMk+DF6aQYUJEIO E/klfjdgPE572Rjiix4nTbZIXjtZ2TPsIkikgLBmQj/dUjmufnVKBJBbePYb6/vNaRoS Ns7Gf45TLg8YuLKY2XJK6i4FVVptuZv7Gj2SQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=XJGwRE9bXKV0CTJhFXJlRsIXGfk6PZ33Xxpe3ntTpGqjIzj4uo5MWe0GfY6VDUTQpx r2/xSYO0hM3Yr8IXUSh0mXKcOJiydFeFpEuzT4GeRqVZCLlG/1eFYsKQMCFsp9Gw/MkS MTN2qNMta36+sKNqLYJlpdcxLmBiIBfYIf27Y= MIME-Version: 1.0 Received: by 10.110.43.16 with SMTP id q16mr6717484tiq.37.1239036527845; Mon, 06 Apr 2009 09:48:47 -0700 (PDT) In-Reply-To: References: <12AEA201F6668F4AAA121035CCFEEB1A501F1E@berwnexmb06.jcorp.ad.jamba.net> <12AEA201F6668F4AAA121035CCFEEB1A502259@berwnexmb06.jcorp.ad.jamba.net> <672a01200904032105y7486e8a6h5eb98c90fd682ad5@mail.gmail.com> <12AEA201F6668F4AAA121035CCFEEB1A50225E@berwnexmb06.jcorp.ad.jamba.net> <672a01200904040441m666cc180k88ba52d4a7d3b80d@mail.gmail.com> <672a01200904042303gd06153bofcfc170163e031bf@mail.gmail.com> <672a01200904050237i2df71b14t544a7cb4f18f3328@mail.gmail.com> Date: Mon, 6 Apr 2009 22:18:47 +0530 Message-ID: <672a01200904060948i356039fax6b980788514d269a@mail.gmail.com> Subject: Re: startup order - correct place to start transport listeners From: Ruwan Linton To: dev@synapse.apache.org Content-Type: multipart/alternative; boundary=001485f07c621b20400466e5acf3 X-Virus-Checked: Checked by ClamAV on apache.org --001485f07c621b20400466e5acf3 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I am in the process of implementing this.... I found a few issues and had to take a few decisions. Issues :- The existing approach doesn't prevent messages to be flowing into synapse before deploying proxies and so on, because the message interceptio= n handlers are attached through the module while the synapse initialization i= s handled out of the module initialization. I found it impossible to implement the listener manager initialization and startup to be different, even though I was planing to do so. Decisions :- Add the start and stop methods to the ManagedLifecycle No need of an post start method to the controller, but inside the controller.start, call the ManagedLifecycle.start() Will be able to commit the first cut soon. Thanks, Ruwan On Mon, Apr 6, 2009 at 9:39 AM, indika kumara wrote= : > Ruwan > > I never said that suggested approach is bad. if you have confidence > that approach will work , then it is good . Generally , a problem have > many solutions. I just say what I like. > You will go on your way. If it can achieve what we need , then it is a > good solution. > > Thanks > Indika > > On Sun, Apr 5, 2009 at 3:07 PM, Ruwan Linton > wrote: > > Indika, > > > > If we are going for such a change it has to go into axis2 and I think i= t > is > > late to get this to axis2 1.5, and I think this is much cleaner.... can > you > > point any issue with this approach? Any reasoning to not to add a start > > method.... > > > > Thanks, > > Ruwan > > > > On Sun, Apr 5, 2009 at 12:24 PM, indika kumara > > wrote: > >> > >> Runwan > >> > >> I personally like, if there are some fixes need to be done on > >> transport layer, if it could be done. > >> > >> BTW, it is good if we can cope (by the implementation we are going to > >> do) transparently with current and future behaviors of transports as > >> synapse always operate top on that. > >> > >> Thanks > >> Indika > >> > >> On Sun, Apr 5, 2009 at 11:33 AM, Ruwan Linton > >> wrote: > >> > Indika, > >> > > >> > I think having a start method is much cleaner than this, because > >> > > >> > listener manager doesn't support adding the transport in the > maintenance > >> > mode... > >> > if we try to start and then put the transport into the maintenance > mode > >> > even > >> > then there is a time where the transports are exposed to the externa= l > >> > users > >> > before synapse initialization > >> > Not all the transports support maintenance mode > >> > > >> > So I would go with the above proposed approach, which is much cleane= r. > >> > > >> > Thanks, > >> > Ruwan > >> > > >> > On Sun, Apr 5, 2009 at 10:57 AM, indika kumara > > >> > wrote: > >> >> > >> >> Hi All > >> >> > >> >> I am not sure but could we achieve following event sequence? > >> >> > >> >> Initializing=85=85=85=85=85. > >> >> > >> >> Initialized and start transport on graceful mode > >> >> Create synapse configuration > >> >> Create synapse environment > >> >> Initialized synapse configuration > >> >> Change the mode of listeners to fully active > >> >> > >> >> Shouting down =85=85=85=85=85=85. > >> >> > >> >> Signal to change the mode of transport into graceful > >> >> destroy synapse configuration and synapse environment > >> >> Signal to completely destroy transport > >> >> > >> >> Could we achieve what we need with above order sequence of events? = If > >> >> it can, I feel we never want to change any API. > >> >> > >> >> Thanks > >> >> Indika > >> >> > >> >> -------------------------------------------------------------------= -- > >> >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org > >> >> For additional commands, e-mail: dev-help@synapse.apache.org > >> >> > >> > > >> > > >> > > >> > -- > >> > Ruwan Linton > >> > Senior Software Engineer & Product Manager; WSO2 ESB; > >> > http://wso2.org/esb > >> > WSO2 Inc.; http://wso2.org > >> > email: ruwan@wso2.com; cell: +94 77 341 3097 > >> > blog: http://ruwansblog.blogspot.com > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org > >> For additional commands, e-mail: dev-help@synapse.apache.org > >> > > > > > > > > -- > > Ruwan Linton > > Senior Software Engineer & Product Manager; WSO2 ESB; > http://wso2.org/esb > > WSO2 Inc.; http://wso2.org > > email: ruwan@wso2.com; cell: +94 77 341 3097 > > blog: http://ruwansblog.blogspot.com > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org > For additional commands, e-mail: dev-help@synapse.apache.org > > --=20 Ruwan Linton Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ruwan@wso2.com; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com --001485f07c621b20400466e5acf3 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I am in the process of implementing this....

I found a few issues an= d had to take a few decisions.

Issues :- The existing approach doesn= 't prevent messages to be flowing into synapse before deploying proxies= and so on, because the message interception handlers are attached through = the module while the synapse initialization is handled out of the module in= itialization.

I found it impossible to implement the listener manager initialization = and startup to be different, even though I was planing to do so.

Dec= isions :- Add the start and stop methods to the ManagedLifecycle
No need= of an post start method to the controller, but inside the controller.start= , call the ManagedLifecycle.start()

Will be able to commit the first cut soon.

Thanks,
Ruwan
<= br>
On Mon, Apr 6, 2009 at 9:39 AM, indika kumara= <indika.kuma= @gmail.com> wrote:
Ruwan

I never said that suggested approach is bad. if you have confidence
that approach will work , then it is good . Generally , a problem have
many solutions. I just say what I like.
You will go on your way. If it can achieve what we need , then it is a
good solution.

Thanks
Indika

On Sun, Apr 5, 2009 at 3:07 PM, Ruwan Linton <ruwan.linton@gmail.com> wrote:
> Indika,
>
> If we are going for such a change it has to go into axis2 and I think = it is
> late to get this to axis2 1.5, and I think this is much cleaner.... ca= n you
> point any issue with this approach? Any reasoning to not to add a star= t
> method....
>
> Thanks,
> Ruwan
>
> On Sun, Apr 5, 2009 at 12:24 PM, indika kumara <indika.kuma@gmail.com>
> wrote:
>>
>> Runwan
>>
>> I personally like, if there are some fixes need to be done on
>> transport layer, if it could be done.
>>
>> BTW, it is good if we can cope (by the implementation we are going= to
>> do) transparently with current and future behaviors of transports = as
>> synapse always operate top on that.
>>
>> Thanks
>> Indika
>>
>> On Sun, Apr 5, 2009 at 11:33 AM, Ruwan Linton <ruwan.linton@gmail.com>
>> wrote:
>> > Indika,
>> >
>> > I think having a start method is much cleaner than this, beca= use
>> >
>> > listener manager doesn't support adding the transport in = the maintenance
>> > mode...
>> > if we try to start and then put the transport into the mainte= nance mode
>> > even
>> > then there is a time where the transports are exposed to the = external
>> > users
>> > before synapse initialization
>> > Not all the transports support maintenance mode
>> >
>> > So I would go with the above proposed approach, which is much= cleaner.
>> >
>> > Thanks,
>> > Ruwan
>> >
>> > On Sun, Apr 5, 2009 at 10:57 AM, indika kumara <indika.kuma@gmail.com>
>> > wrote:
>> >>
>> >> Hi All
>> >>
>> >> I am not sure but could we achieve following event sequen= ce?
>> >>
>> >> Initializing=85=85=85=85=85.
>> >>
>> >> Initialized and start transport on graceful mode
>> >> Create synapse configuration
>> >> Create synapse environment
>> >> Initialized synapse configuration
>> >> Change the mode of listeners to fully active
>> >>
>> >> Shouting down =85=85=85=85=85=85.
>> >>
>> >> Signal to change the mode of transport into graceful
>> >> destroy synapse configuration and synapse environment
>> >> Signal to completely destroy transport
>> >>
>> >> Could we achieve what we need with above order sequence o= f events? If
>> >> it can, I feel we never want to change any API.
>> >>
>> >> Thanks
>> >> Indika
>> >>
>> >> ---------------------------------------------------------= ------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> >> For additional commands, e-mail: dev-help@synapse.apache.org
>> >>
>> >
>> >
>> >
>> > --
>> > Ruwan Linton
>> > Senior Software Engineer & Product Manager; WSO2 ESB;
>> > http://wso2= .org/esb
>> > WSO2 Inc.; http= ://wso2.org
>> > email: ruwan@wso2.com; = cell: +94 77 341 3097
>> > blog: http://ruwansblog.blogspot.com
>> >
>>
>> ------------------------------------------------------------------= ---
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>
>
>
> --
> Ruwan Linton
> Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.o= rg
> email: ruwan@wso2.com; cell: +94= 77 341 3097
> blog: htt= p://ruwansblog.blogspot.com
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org




--
Ruwan Linto= n
Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 3= 41 3097
blog: http://ruwansbl= og.blogspot.com
--001485f07c621b20400466e5acf3--