We have an OpenAPI (Swagger 2.0) specification for our API. One of our customers uses ColdFusion and wants to have a native client SDK implemented in CFML.
It seems that Swagger Codegen does not actually support CFML/ColdFusion. However, since OpenAPIs are so common now I thought there must be some way to generate a CFML library from an OpenAPI/Swagger 2.0 Spec.
Does anyone know how to do this? Any help would be greatly appreciated.
Related
Has anyone of you already tried integrating with FrontierLink?
Found in their documentation
5.2 Building the FrontierLink Client
5.2.1 SOAP Client Environment
You must adhere to the following minimum requirements for SOAP clients in order to successfully integrate with FrontierLink:
XML 1.0
SOAP 1.1
HTTP 1.0 (1.1 preferred)
SSL based connection authenticated via X.509 Digital Certificates
WSDL1.1
A Web Services toolkit supporting WSDL 1.1 is recommended to aid your development.
In their documentation there is no sample on how to get started. I am really sorry for asking this question but what would be the code for connecting to FrontierLink? Thanks! Hoping for someone who can help :) Thank you once again!
May you please show us an example of the FrontierLink API? so that I may be able to help you further?
Just in a nutshell with what I understand when using SOAP api, you will have to call the APIs or links from your application(web/mobile) and in turn the API will return data in form of XML. you will then have to parse that data so that you may able to use that in your application.
I am using Django for my website/app and I want to integrate quickbooks. I wasn't sure whether you are using Oauth version 1.0 or 2.0. Also the documentation is more specific for PHP but the django-oauth-toolkit documentation I THINK is more geared towards hosting your own Oauth than connecting as a client. So although my main question is what version are you using any links to where I could read up on connecting with django would be greatly appreciated. I do have PHP still setup but I have been converting all my modules to django (python) and I was trying to avoid that. I thought reading the IETF protocol might help my understanding but there is the older version 1.0 by the original author and then the newer 2.0 that is currently supported. He does seem to have a pretty good beginner's guide but at the same time he seems a little 'disgruntled', if that's the right word, about the newer version. Also I believe the django-oauth-toolkit is version 2.0 protocol.
It's OAuth v1.0.
They have a bit of documentation here:
https://developer.intuit.com/docs/0100_quickbooks_online/0100_essentials/0085_develop_quickbooks_apps/0004_authentication_and_authorization
I would highly recommend you find an existing OAuth library for Django/Python - writing your own is likely going to be a painful process.
My question is concerning the Rally javascript SDK 1.32.
My line of thinking is this: SDK 1.32 seems to only return objects with APIMajorVersion 1 and MinorVersion 32, yet there exist versions from 1.33 to 1.43 as well (though they are all now deprecated as well). It makes sense to me that since SDK 2.0 must return objects from version 2.0, that there should be a way to specify what webservice version to return objects from.
My question is this: am I right that there is a way to obtain Rally objects from webservice v2.0 from SDK 1.32? If so, how would I do that?
I'm not just asking this out of laziness-- I am on the tail-end of an internship and would not necessarily have time to learn the new SDK and reimplement all that I have done on SDK 1.32.
Thanks for any responses!
This answer:
1.39 Rally API Version source for Java Script
shows how to utilize AppSDK 1.x using different versions of WSAPI.
However, AppSDK 1.x utilizes the adhoc.js Webservices endpoint for querying. This endpoint has been deprecated in Webservices 2.0. As a result, AppSDK 1.x will not work against Rally Webservices 2.0.
I'd recommend using AppSDK 2rc1, which is built on Webservices 2.0.
I was thinking into digging a little dipper into the REST type of web services and noticed that there aren't any specifications for it as opposed to SOAP web services.
Why is that?
Each language uses its own standards.
According to Wikipedia:
Unlike SOAP-based web services, there is no "official" standard for RESTful web services. This is because REST is an architecture, unlike SOAP, which is a protocol.
http://www.w3.org/Protocols/rfc2616/rfc2616.html - Http Uniform interface specification
http://tools.ietf.org/wg/httpbis/ - Latest revisions to HTTP spec
https://datatracker.ietf.org/doc/html/draft-gregorio-uritemplate-04 - URI Templates
https://datatracker.ietf.org/doc/html/draft-nottingham-http-link-header-06 - Link Headers and link relations
http://www.iana.org/assignments/media-types/ - Loads of links to specs for media types
These should be all the specs you need to get going to build a RESTful system over HTTP.
Are there specific WS-* specifications that you feel you are missing to be able to build as REST based system?
Well, at least for Java there is JAX-RS http://en.wikipedia.org/wiki/JAX-RS, but i don't know if this is based on some other standards.
OData (http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.html) is a standard for RESTful WebServices and should fit your needs (at least if you're using any MS framework).
Btw. if you want do use a standard and make the WebService as open and reusable as possible, WADL (http://www.w3.org/Submission/wadl/#x3-40001.3) the WSDL equivalent for REST could help.
I am looking for resources to show me how I can consume web services inside native C++ . Are there any popular libraries I can use?
TIA
Andrew
It really depends on what webservice architecture you are talking about... For XML-RPC IBM has a nice article showcasing XMLRPC++, for SOAP there is e.g. gSOAP or WSO2 WSF/C++, ...
There are the Axis2/C libraries, which, while C based rather than C++, are still easily employable - when I was working on Apache Tuscany, we used Axis2/C for our C++ Web Service bindings.
From the Axis2/C front page:
"Apache Axis2/C supports SOAP 1.1 and SOAP 1.2, as well as REST style of Webservices. A single service could be exposed both as a SOAP style as well as a REST style service simultaneously. It also has built in MTOM support, that can be used to exchange binary data."