Hi all, In terms of schema validation too I believe that having sdfc_2.0 might be a better approach, since the two versions can probably have two separate configuration models. So, even if we don't support two versions side-by-side, it makes it easier for us to maintain validation logic.
Thanks, Senaka. On Tue, Aug 13, 2013 at 10:04 AM, Samisa Abeysinghe <[email protected]> wrote: > When we say "a new version of a connector" that is another connector of > similar kind, that we can use side by side right? If that is the case, > "sfdc_2.0" > looks more fitting than using version as an attribute. > > > On Tue, Aug 13, 2013 at 10:00 AM, Kasun Indrasiri <[email protected]> wrote: > >> One possibility is to embed the version in to the connector name itself. >> So that the invocation would looks like either >> >> <sfdc_2.0.query > >> <batchSize>200</batchSize> >> <queryString>select test</queryString> >> </sfdc_2.0.query> >> >> or as follows. >> <sfdc.query version="2.0"> >> <batchSize>200</batchSize> >> <queryString>select test</queryString> >> </sfdc.query> >> >> With this both ESB and DevS can handle multiple versions. >> >> Other alternative is to introduce a versioning strategy in to connector >> (former: mediation-lib) itself. However,IMO, this needs to be done along >> with versioning support for all other artifacts such as sequence, >> endpoints, proxy services etc. >> >> >> >> On Mon, Aug 12, 2013 at 10:43 PM, Sanjiva Weerawarana >> <[email protected]>wrote: >> >>> Have we thought about $subject? Can someone elaborate the architecture >>> for versioning of connectors please? Need to get that right. >>> >>> The tooling team also has to handle connector versions. >>> >>> Both ESB runtime and tool have to be able to load multiple connector >>> versions at once (think data migration scenarios). >>> >>> Sanjiva. >>> -- >>> Sanjiva Weerawarana, Ph.D. >>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ >>> email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880| +1 >>> 650 265 8311 >>> blog: http://sanjiva.weerawarana.org/ >>> >>> Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Kasun Indrasiri >> Software Architect >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +94 71 536 4128 >> Blog : http://kasunpanorama.blogspot.com/ >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- * <http://us13.wso2con.com/> * * * *Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
