GitHub user Flowdalic opened a pull request: https://github.com/apache/camel/pull/299
Update to Smack 4.0.4 Remove Presence Packet listener in XmppConsumer. It never worked, since the processPacket() method does check if the given Packet is instanceof Message, so the filtered Presence Packets never got processed. XMPPError.getCode() is no more. Integer error codes have been deprecated from XMPP for a while. Use getType() instead. Use the connection packet reply timeout, instead of the global one in SmackConfiguration (where the method name was changed to SmackConfiguration.getDefaultPacketReplyTimeout()). Use JivePropertiesManager for Packet properties. Fixes CAMEL-7903 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Flowdalic/camel smack40 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/299.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #299 ---- commit 220a61392062654b1c559afc46f4af9fc8c996fd Author: Florian Schmaus <f...@geekplace.eu> Date: 2014-10-12T14:24:04Z Update to Smack 4.0.4 Remove Presence Packet listener in XmppConsumer. It never worked, since the processPacket() method does check if the given Packet is instanceof Message, so the filtered Presence Packets never got processed. XMPPError.getCode() is no more. Integer error codes have been deprecated from XMPP for a while. Use getType() instead. Use the connection packet reply timeout, instead of the global one in SmackConfiguration (where the method name was changed to SmackConfiguration.getDefaultPacketReplyTimeout()). Use JivePropertiesManager for Packet properties. Fixes CAMEL-7903 ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---