We have dealt with the problem of dealing with multiple API versions, when dealing with Jira connector.
It is important to be focused on handling the multiple back end systems APIs over implementation detail. I think we need to talk to the ESB team and see what they did with Jira connector. Do we not have a connector each for Jira for each version? Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Fri, Dec 20, 2013 at 7:39 PM, Ramindu Deshapriya <rasad...@gmail.com>wrote: > Hi Samisa, > > > Samisa Abeysinghe-4 wrote > > Which one of those in http://apidocs.sugarcrm.com/ are we going to wrap > > with the connector? > > The link you have provided outlines the developer documentations for those > maintaining their own instance of Sugar CRM, which can be used to make > modifications to the framework. > > Each instance of Sugar CRM exposes a set of web services which can be used > via their web services API. The link provided by Indika above outlines > these > services. > > A RESTful implementation of these services is outlined at > https://fpkgtt3661.trial.sugarcrm.com/rest/v10/help, however, these are > rather ambigious in terms of functionality as they directly point to > resources within an instance of Sugar CRM. > > Therefore, we are hoping to go with the SOAP web services outlined in the > link Indika provided above. > > Thank You. > > > > -- > View this message in context: > http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-SugarCRM-tp89877p90071.html > Sent from the WSO2 Architecture mailing list archive at Nabble.com. > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
