Sanjiva Weerawarana wrote:
> Please look to reduce the number of configurable settings .. 
What sort of?, I don't see any configurable parameter that we can get 
rid of at least for the moment...
> otherwise we'll need to have a truth table documented and explanations 
> of what all the combos mean! Its like enabling REST in the ESB ;-).
What is enabling REST in ESB, there is no such thing, unless you want to 
switch from SOAP to REST there is no configuration required at least on 3.0

Ruwan
>
> Sanjiva.
>
> On Tue, Aug 3, 2010 at 8:40 AM, Kasun Indrasiri <[email protected] 
> <mailto:[email protected]>> wrote:
>
>
>
>     On Tue, Aug 3, 2010 at 7:42 AM, Miyuru Wanninayaka
>     <[email protected] <mailto:[email protected]>> wrote:
>
>         Hi Kasun,
>
>         On Mon, Aug 2, 2010 at 10:43 PM, Kasun Indrasiri
>         <[email protected] <mailto:[email protected]>> wrote:
>
>             Hi folks, 
>
>             In ESB 2.x/3.x, if a proxy service is failed during the
>             creation/deployment, then the ESB cannot be started. This
>             prevents, an user from accessing the Management Console
>             and only way to restore the system is to edit the
>             configuration that resides in the files system(3.x). In a
>             scenario where we have several proxy services (+ other
>             sequences etc), the system becomes crappy, even if one
>             proxy is failed during the startup.
>
>             So, introducing a configuration parameter to switch on/off
>             fail-safe mode for proxy services would be a better way of
>             handling these issues. (We have a similar approach for
>             enabling fail-safe mode for publishing WSDLs).
>
>             A given proxy service may fail in two different stages.
>
>             _Deployment-time failures _
>             _
>             _
>                  - We have the complete configuration for the proxy
>             service but it failed when we are deploying it.
>                  - e.g. Missing security policy etc.
>                  - Axis2SynapseController - deployProxyServices()  
>                  - ProxyService -buildAxisService(..)   // hot deployment 
>
>             _Creation-time failures  _
>
>                  - The proxy service's configuration cannot be built.
>                  - e.g. WSDL based proxies with unavailable wsdls
>
>
>         To handle missing wsdls we already have
>         a parameter enablePublishWSDLSafeMode, but this parameter is
>         disabled by default. May be we can set this to enabled by
>         default. 
>
>      
>     The purpose of the 'enablePublishWSDLSafemode' is to handle cases
>     where the publishing WSDL is not available. So WSDL based proxies
>     cannot be made fail-safe by using 'enablePublishWSDLSafemode=true'. 
>
>          
>
>                  - A proxy service configuration may get created when
>             we are starting the ESB. 
>                  - MultiXMLConfigurationBuilder - createProxyServices(..)
>
>
>             I have locally did the required changes to address
>             failures in above stages and tested it.(We can add a new
>             property to synapse.properties
>             (enableFailsafeProxyServices) and use it to check whether
>             fail-safe mode is switch on or not.)
>             However, I have some doubts over handling 'Proxy service
>             creation-time failures'. If we are going to handle such
>             scenarios, then we also have to handle cases like WSDL
>             Endpoints failures. Do we really want to handle this?
>
>             WDYT?
>
>
>         +1 for handling proxy creation time failures.  We can set this
>         services as faulty services. AFIK data services doing the same
>         thing.
>
>
>             Thanks.
>             Kasun
>
>
>             -- 
>             Kasun Indrasiri
>             Senior Software Engineer
>             WSO2, Inc.; http://wso2.com
>             lean.enterprise.middleware
>
>             cell: +94 71 536 4128
>             Blog : http://kasunpanorama.blogspot.com/
>
>             _______________________________________________
>             Carbon-dev mailing list
>             [email protected] <mailto:[email protected]>
>             https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>
>         -- 
>         Thanks,
>         Miyuru
>
>         _______________________________________________
>         Carbon-dev mailing list
>         [email protected] <mailto:[email protected]>
>         https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>
>     -- 
>     Kasun Indrasiri
>     Senior Software Engineer
>     WSO2, Inc.; http://wso2.com
>     lean.enterprise.middleware
>
>     cell: +94 71 536 4128
>     Blog : http://kasunpanorama.blogspot.com/
>
>     _______________________________________________
>     Carbon-dev mailing list
>     [email protected] <mailto:[email protected]>
>     https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>
> -- 
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
> email: [email protected] <mailto:[email protected]>; phone: +1 408 754 
> 7388 x51726; cell: +94 77 787 6880 | +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware
> ------------------------------------------------------------------------
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>   


-- 
Ruwan Linton
Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.com

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: [email protected]; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
tweet: http://twitter.com/ruwanlinton


_______________________________________________
Carbon-dev mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to