+1 Also, It may be good to revisit the error handling logic and policy (configuration) from different view points radically. An endpoint has a proper life-cycle and the errors are just conditions that make the state-transition. The policy + implementation is to represent that. There may be some other views.
Thanks, Indika On Mon, Mar 7, 2011 at 5:17 PM, Supun Kamburugamuva <supu...@gmail.com>wrote: > In lot of production systems there are hundreds of endpoints deployed. > These endpoints carry lot of redundant configurations. So it is better to > have a template based endpoint configuration. > > Here is a proposed configuration > > <endpoints> > <endpoint name="" uri="" template=""/> > <endpoint name="" uri="" template=""/> > <endpoint name="" uri="" template=""/> > </endpoint> > > <endpoint-template name=""> > <address> > <suspendOnFailure> > <errorCodes>23123</errorCodes> > <progressionFactor>1.0</progressionFactor> > </suspendOnFailure> > <markForSuspension> > <errorCodes>1231</errorCodes> > </markForSuspension> > <retryConfig> > <errorCodes>1231</errorCodes> > </retryConfig> > </address> > </emdpoint-template> > > Based on the endpoint-temaplate configuration multiple endpoints will be > created with the url and name defined in the endpoints configuration element > at the run-time. > > Thanks, > -- > Supun Kamburugamuva > Technical Lead & Product Manager, WSO2 Inc.; http://wso2.com > Member, Apache Software Foundation; http://www.apache.org > WSO2 Inc.; http://wso2.org > E-mail: su...@wso2.com; Mobile: +94 77 431 3585 > Blog: http://supunk.blogspot.com > > > >
