On Wed, Mar 9, 2011 at 11:11 AM, indika kumara <[email protected]>wrote:
> Spun, as we discussed off-line, we can use the same kind of approach > proposed by Udanyaga for the endpoint template. BTW, any thing can be > improved later. If it is urgent you can go with what you have done so far. > But, we have to remove 'endpointGroup' or 'endpoints' > > I'm in the process of changing it in sync with the Udayanga's approach and will remove the endpointGroup concept. Thanks, Supun.. ~ Indika > > > On Wed, Mar 9, 2011 at 10:50 AM, Supun Kamburugamuva <[email protected]>wrote: > >> On Wed, Mar 9, 2011 at 9:51 AM, indika kumara <[email protected]>wrote: >> >>> Supun, Can we avoid '<endpoints>'. When XML is used to define a data-type >>> we usually uses an outer tag (e.g array like data structure in a SOAP >>> message). But, I am not sure whether it is good to define language >>> constructs in that way. Just have a look at the WSDL 2.0 >>> >>> As I said in another email, in my opinion, It would be better if both >>> your approach and Udanyaga's (function template) represent the same concepts >>> + similar syntax. >>> >>> >> I've changed it to endpointGroup. endpoint-template is changed to >> endpointTemplate. At the moment what Udayanga is doing and this seems >> related but bit different. We need to come up with the two implementations >> and later find out a way to connect them. I did an initial implementation >> and I will commit it shortly. Or do you like to see a patch first? >> >> Thanks, >> Supun.. >> >> >>> Thanks, >>> >>> Inidka >>> >>> >>> On Tue, Mar 8, 2011 at 1:01 AM, Supun Kamburugamuva >>> <[email protected]>wrote: >>> >>>> >>>> >>>> On Mon, Mar 7, 2011 at 10:54 PM, Udayanga Wickramasinghe < >>>> [email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> On Mon, Mar 7, 2011 at 4:47 PM, Supun Kamburugamuva <[email protected] >>>>> > 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. >>>>>> >>>>>> +1 >>>>> btw are we defining configurable parameters for templates?? or are >>>>> they just static templates? >>>>> >>>>> >>>> >>>> For this case I believe it is just a static template. >>>> >>>> Thanks, >>>> Supun.. >>>> >>>> >>>>> Regards, >>>>> Udayanga-- >>>>> >>>>> *Udayanga Wickramasinghe* >>>>> Software Engineer; WSO2 Inc.; http://wso2.com, >>>>> *email: **[email protected]* <[email protected]>* cell: +94 (77) >>>>> 983-4365 >>>>> blog: >>>>> **http://udayangawiki.blogspot.com*<http://udayangawiki.blogspot.com/> >>>>> * >>>>> twitter: >>>>> **http://twitter.com/udayanga_wick*<http://twitter.com/udayanga_wick> >>>>> * >>>>> * >>>>> >>>> >>>> >>>> >>>> -- >>>> 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: [email protected]; Mobile: +94 77 431 3585 >>>> Blog: http://supunk.blogspot.com >>>> >>>> >>>> >>>> >>> >> >> >> -- >> 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: [email protected]; Mobile: +94 77 431 3585 >> Blog: http://supunk.blogspot.com >> >> >> >> > -- 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: [email protected]; Mobile: +94 77 431 3585 Blog: http://supunk.blogspot.com
