Update to Smack 4.0#299
Conversation
|
Hi Fowdalic, I tried to apply the PR to Apache Camel master branch, now I got the lots of unit test failures: XmppDeferredConnectionTest>CamelTestSupport.setUp:217->CamelTestSupport.doSetUp:311->CamelTestSupport.startCamelContext:477 ? FailedToCreateProducer |
|
How did you run tun the unit tests? Are there no stacktraces or exceptions? Which java runtime version are you using? I could swear What is the standard way to invoke the unit tests in Apache Camel? |
|
Now I got that looks similar to yours, investigating. |
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
|
I've pushed a new version of the commit. There are some issues I'd like to get feedback on how to solve them:
|
|
Friendly reminder: Still waiting for feedback from the maintainers. |
|
Obsoleted by b909dec |
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