On Wed, Dec 1, 2010 at 1:17 AM, Prabath Siriwardana <[email protected]>wrote:
> > > On Wed, Dec 1, 2010 at 1:05 AM, Prabath Siriwardana <[email protected]>wrote: > >> >> >> On Wed, Dec 1, 2010 at 12:53 AM, Hiranya Jayathilaka <[email protected]>wrote: >> >>> >>> >>> On Tue, Nov 30, 2010 at 11:52 PM, Prabath Siriwardana >>> <[email protected]>wrote: >>> >>>> When I set the WSO2 Registry as the Discovery Proxy for the WSAS - all >>>> the services deployed in WSAS will be discovered and listed in GReg - and >>>> will be available for ESB via it's discovery client.. >>>> >>>> But, when I un-deploy services, Discovery proxy doesn't get updated - >>>> and an invalid service that doesn't exist is listed as discovered.. [ >>>> although the end point column kept blank for such services in discovery >>>> client] >>>> >>>> Shouldn't we remove the services from the Discovery Proxy once they get >>>> un-deployed...? >>>> >>> >>> The behavior you are expecting was there in the very first cut of the >>> discovery implementation but it was changed after a review. Now when a >>> service is undeployed we remove the endpoint details from the discovery >>> proxy and the service resource is marked inactive. You can still discover >>> them but since there are no endpoints, the client can figure out that the >>> service in unavailable at the moment. In a real life system this means >>> either the server is temporarily down or the service has been temporarily >>> deactivated. It is little unlikely for a service to just vanish without a >>> trace in a production system. >>> >>> If you want, you can configure the discovery proxy to not return inactive >>> services on probes. Set the following parameter in the axis2.xml of GReg: >>> >>> <parameter name="skipInactiveServices">true</parameter> >>> >>> IMO this is a much cleaner and flexible approach. WDYT? >>> >> >> +1 - was not aware of this parameter... Thanks for the nice explanation... >> > > > Thinking from a user perspective I guess better we default this to 'true'.. > WDYT? > Fine by me. If there are no objections from others I can make the fix in the trunk for a future release. Thanks, Hiranya > > Thanks & regards, > -Prabath > > >> >> Thanks & regards, >> -Prabath >> >> >> >>> >>> Thanks, >>> Hiranya >>> >>> >>>> -- >>>> Thanks & Regards, >>>> Prabath >>>> >>>> http://blog.facilelogin.com >>>> http://RampartFAQ.com >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> >>> -- >>> Hiranya Jayathilaka >>> Senior Software Engineer; >>> WSO2 Inc.; http://wso2.org >>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>> Blog: http://techfeast-hiranya.blogspot.com >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Thanks & Regards, >> Prabath Siriwardena >> >> >> http://blog.facilelogin.com >> http://RampartFAQ.com >> > > > > -- > Thanks & Regards, > Prabath Siriwardena > > http://blog.facilelogin.com > http://RampartFAQ.com > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
