This is primarily a bug fix release, which addresses some issues which were recently discovered and improves things here and there. It is compatible to version 0.6.0.
For detailed release notes, you can find the changelog here.
This is primarily a bug fix release, which addresses some issues which were recently discovered and improves things here and there. It is compatible to version 0.6.0.
For detailed release notes, you can find the changelog here.
Hi Christian,
ReplyDeleteThanks for the cool project. Looks like a very clean interface.
Your contact information on your profile (ICQ) is 404). I would like to contact you directly, if possible, about adding some extensions.
Hi,
Deletetry mail to xmpp-rocks@googlegroups.com. Maybe you have to subscribe to the mailing list first: https://groups.google.com/forum/#!forum/xmpp-rocks
Nice library. I like it a lot. Very clean and modern. Are there any plans for a server side implementation? Something developer orientated, that can be embedded into large applications.
ReplyDeleteCheers
Hi, thanks :-). No sorry, there are no plans for implementing an XMPP server. It's just too much effort. I am a bit involved in Openfire development and know there would be a lot of things to do...
Deletehello. sorry to bother you, but I searched the documentation and couldn't find an event on when the client is successfully( or not) connected to server, before login process. The reason I need this is because sometimes( not all the time) I receive this error. This is happening only in 10% of the time, but it's frustrating. Is there a solution?
ReplyDeletejava.lang.IllegalStateException: You must be connected to the server before trying to login.
at rocks.xmpp.core.session.XmppSession.preLogin(XmppSession.java:291)
at rocks.xmpp.core.session.XmppClient.login(XmppClient.java:330)
at rocks.xmpp.core.session.XmppClient.login(XmppClient.java:308)
at rocks.xmpp.core.session.XmppClient.login(XmppClient.java:280)
at rocks.xmpp.core.session.XmppClient.login(XmppClient.java:257)
at objects.clients.xmpp.XmppVisitorClient.lambda$2(XmppVisitorClient.java:105)
at objects.clients.xmpp.XmppVisitorClient$$Lambda$31/301886358.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
never mind, I found it: xmppClient.addSessionStatusListener
DeleteThanks
Hi. Is it possible that you call connect() simultaneously from different threads? If so, you could try wrapping it in a synchronized block.
DeleteI've seen this as well and it needs fixing.
Actually the error appears when you call this in the same thread. My code was something like this:
Delete//in the same thread
xmppClient.connect();
xmppClient.login( ... );
To make it work I did something like this:
1) xmppClient.connect(); //Thread 1
2) xmppClient.addSessionStatusListener(e ->{
if(e.getStatus()==Status.CONNECTED){
xmppCLient.login( ... ); // Thread 2
}
});
Huh, that's weird... You could try 0.6.2, but I never saw this happen in the same thread.
Deleteok. I'm currently using 0.6.1 . Like I said most of the time 90% it worked in single thread. I'll also re-check my code, maybe I did something wrong that broken the login.
DeleteYou could contact me via mail (christian.schudt at gmx.de) or in the mailing list https://groups.google.com/forum/#!forum/xmpp-rocks to discuss further issues.
DeleteThis comment has been removed by the author.
ReplyDelete