How to install rest api on open-fire server version 3.9?
we have a pre implemented application on open-fire 3.9. Now we want to update the functionality with rest api. But rest api required open-fire version 4.0+.
So how is it possible?
if any one have an alternate then please help me.
You need an older version of the plugin, hoping it supports what you need.
You can download by following this link:
https://community.igniterealtime.org/thread/56342
Related
I plan to use the Microsoft.Azure.NotificationHubs to push notification through Azure notification hub in backend service of an existed project. However, I found that the project is using .NETFramework 4.5.2. As the document stated, the SDK has dependecy to .NETFramework 4.6.1 or higher.
Since the existed project is already developed well and problems could appear if I upgrade. Any other solutions please?
Due to you don't want to upgrade to .Net Framework 4.6.1 or higher. You can use REST API, create HttpClient in your existed project to send Http Request.
（notificationhubs）REST API methods
You can use HttpHelper in my sample code.
I've written a small application which accesses the REST API of Atlassian Bamboo.
As the documentation describes:
To get the latest version of the API, you can also use the latest key-word.
So I used the latest keyword to access the version. But I noticed now, after migrating to the new Bamboo version, that this wasn't the best solution, because the new version seems to have changed some things in the API and breaks my application.
Now I would like to build my application with a specific API version. But how can I tell: which is the exact version of the current API?
The only thing which the documentation is saying about this:
The API version is independent of the Bamboo release number.
The API version may, or may not, change with a new Bamboo release. The API version number will change only when the updates to the API break the API contract, requiring changes in the code which uses the API. ...
The documentation of the single Bamboo versions (like the one for 6.6.2) only uses the latest keyword as reference.
And even the REST api itself (under /rest/api/latest/info) only tells me the Bamboo version, not the API version:
<info>
<version>6.6.2</version>
<edition/>
<buildDate>2018-08-14T09:01:47.000+02:00</buildDate>
<buildNumber>60606</buildNumber>
<state>RUNNING</state>
</info>
So how do I find the exact API version of my Bamboo installation?
I've been using the NuGets from Outercurve Foundation (Facebook and Facebook.Client) and I've just updated to the latest stable version for both of them since Facebook API 2.0 and 2.1 will be depricated on the 7th August 2016 and they are forcing us to use the later verstions of their API.
Here is the thing... the website facebooksdk.net which had documentation and such was down for some time and now it redirects to hackerapp.com which has no documentation whatsoever...
Does any one know the version of Facebook API that the NuGet Facebook 7.0.6 and Facebook.Client 1.0.4 are using?
I think that the facebook button (from Facebook.client) is using the 2.1 version of the API. because I saw it in the query when it opens the browser just before the login prompt.
Does any one know which version is used? and if there is another way to login using the 2.5 or 2.6 API version?
I believe the client does not enforce any API version, so it will make unversioned calls. And in this case, it will use the default API version that is set on your Facebook App...
You can check the default API version for your app in your app's dashboard in https://developers.facebook.com
Mine is currently v2.0 (I don't know yet how to change manually that version. Facebook will certainly upgrade it when v2.0 expires)
I am using an even older version of the nuget package (6.4.2) and was able to override the version simply setting it in the endpoint being called:
Exmaple:
var client = new FacebookClient(accessToken);
dynamic facebookUser = client.Get("me"); //this will use v2.0 currently (default API version)
dynamic facebookUser = client.Get("v2.6/me"); //this will use v2.6
PS: version 2.0 will expire 7th August 2016... version 2.1 will expire only in 30 October 2016 (2 years after 2.2 was launched)
For those wanting to use Facebook.Client with Facebook API v2.5 you can use this one https://github.com/rickrvo/facebook-winclient-sdk
it's just the same as the version 1.0.4 but changed all hardcoded calls using v2.1 to use v2.5
I have a REST API that was working with Jersey 2.6 and Swagger 1.3.7. I read that Jersey 2.9 fixes a warning that I was getting so I upgraded to the latest Jersey 2.16 but then Swagger stopped working. I went back and upgraded one version at a time until I saw that Swagger was working with 2.15 so I settled on that. Now, the PUT API fails with Swagger with the following error:
The server refused this request because the request entity is in a format not supported by the requested resource for the requested method
The API works using FireFox RESTClient and specifying "application/json".
I do have "jersey-media-json-jackson" as a dependency and call "Client client = ClientBuilder.newClient().register(JacksonFeature.class);" in the program.
I tried upgrading Swagger but that did not help.
Has Swagger been verified to work with Jersey 2.15/2.16?
I've recently managed to get swagger-core to work with Jersey 2.16 with a similar issue. Keep in mind they are using the latest version (1.5.X) and not 1.3.X but the same solution will apply.
The problem is most likely with version resolution, specifically, the one of jackson-databind. For some reason, even jersey-media-json-jackson 2.16 depends on an older version of jackson-databind, even though it works fine with the latest version. Without having more details, it would be difficult to suggest a full solution, but you can follow the dependency tree and see the conflicts there.
If you do require further assistance, I'd suggest either using our mailing list, or even better, the IRC channel where we could interact online and resolve it.
I'm wondering if the Azure Notification Hubs REST API documentation is still correct and up-to-date or if there is already a newer API version than "2013-08" that can be used.
All the single pages show "Updated: February 26, 2015", but I guess it was just a meta data update of all the pages, since the API version didn't change, it's still "2013-08".
Here (and here) is an example for the REST API usage from Elio Damaggio which uses "2013-10" as the api version.
I tried all possible api version values in the format "yyyy-mm" from "2013-10" to "2015-03" and the following were working: "2013-10", "2014-01", "2014-05", "2014-08", "2014-09", "2015-01".
Does anyone use a newer API version than "2013-08" or does anyone know anything about a newer API version or documentation? Specifically, does anyone know if there is a documentation for a newer API version, e.g. "2015-01", or at least a changelog?
Got an answer on MSDN forums:
The latest version is 2015-01. All or most of features works with
starting version 2013-08.
Version in documentation indicates that minimum version required for
working that feature. Hence, all documentation is pointing to 2013-08.
...
Yes, you can use version 2015-01 instead of 2013-08. There won’t be
any difference because we didn’t do any breaking changes from 2013-08.
All the features works from version 2013-08.
Moreover, the source code for the Java REST wrapper for Windows Azure Notification Hubs on github seems to be a good reference. It is using api version "2014-09", not "2015-01" right now, but at least it includes the registration code for Amazon Device Messaging and Baidu Cloud Push which are currently missing in the REST API documentation.