Hi, What is the final implementation of this? Do we have to type <jira_2.0 bla="xx"> every time we use the JIRA connector ? is there a way to configure the default version so we can keep on typing <jira bla="xx"> instead?
This may be a subjective argument, but <jira_2.0 bla="xx"> looks ugly to me. On Wed, Aug 14, 2013 at 2:29 PM, Pulasthi Supun <pulas...@wso2.com> wrote: > Hi All > > I don't think making the version optional is a good idea. For cases like > twitter even though they only have one version at a given time it would be > good to reflect the version in the configuration . > > > On Wed, Aug 14, 2013 at 2:07 PM, Piyum Fernando <pi...@wso2.com> wrote: > >> Hi, >> >> I think we need to make version an optional parameter. >> If version is not mentioned by the user ESB should use the latest of the >> available set. >> >> As Miyuru mentioned, in twitter like cases there is no need of defining >> the version. >> Migrating from older version to a newer means adding the new connector to >> the runtime. >> No need to change the configuration unless there are any API changes. >> >> One thing that could go wrong is that he/she may assume that the correct > connector version is used by looking at the configuration since it does not > show the version of the connector currently used. > > Regards, > Pulasthi, > >> If we are going to make it optional I'm +1 for the second approach. >> >> IMO <sfdc.query version="2.0"> and <sfdc.query> is better than >> <sfdc_2.0.query > and <sfdc.query > >> >> Thanks. >> >> >> >> On Wed, Aug 14, 2013 at 12:05 PM, Miyuru Wanninayaka <miy...@wso2.com>wrote: >> >>> It depends on the type of connector. >>> >>> There are some cloud APIs which only maintains one version ( like >>> twitter ). In those cases we don't have to have versions because in a given >>> time there will be only one version. >>> >>> For cases like jira, we have to have different versions as jira 3,4,5 >>> has completely different APIs. >>> >>> >>> On Wed, Aug 14, 2013 at 11:55 AM, Manuranga Perera <m...@wso2.com>wrote: >>> >>>> isn't updating form one version to another of same connector a common >>>> use cause (as opposed to using multiple versions)? >>>> if so naming it like "sdfc_2.0" would not be ideal for migration. >>>> >>>> -- >>>> With regards, >>>> *Manu*ranga Perera. >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Miyuru Wanninayaka >>> >>> Technical Lead >>> WSO2 Inc. : http://wso2.com >>> >>> Mobile : +94 77 209 9788 >>> Blog : http://miyurudw.blogspot.com >>> Flickr : http://www.flickr.com/photos/miyuru_daminda >>> >>> _______________________________________________ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Piyum Fernando >> Software Engineer >> >> Mobile: +94 77 22 93 880 >> Home: +94 31 22 75 715 >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > -- > Pulasthi Supun > Software Engineer; WSO2 Inc.; http://wso2.com, > Email: pulas...@wso2.com > Mobile: +94 (71) 9258281 > Blog : http://pulasthisupun.blogspot.com/ > Git hub profile: https://github.com/pulasthi > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
