I’'m working on a simple implementation of OOB. I extended IQ with OutOfBandData and overrode the getChildElementXML() w/ the elements in JEP-0096.
This afternoon, I was sending my jabber:iq:oob packets and could pull the URL out and print it in the other client. then I moved some code around and now my packets seem to be bouncing back from the server (Jive Messenger) w/ a 503 error.
I compose my OutOfBandData iq and it looks like this when the XMPPConnection puts it on the queue:
candidate@crossfire never gets this message, however, proctor@crossfire is now parsing an error message it appears to have received from itself. The stream in the parser looks like this:<?xml version=''1.0'' encoding=''utf-8''?>
xmlns=“jabber:client” from=“CROSSFIRE” id=“da9fe5f5”>
<iq from=“proctor@CROSSFIRE/Smack” to=“proctor@CROSSFIRE/Smack”
<iq from=“proctor@CROSSFIRE/Smack” to=“candidate@CROSSFIRE” id=“pTxdt-4”
My XML seems ok and it appeared to work earlier this evening (of course we all say that). The error doesn’‘t appear to be generated anywhere in the smack library. I’‘ve put a breakpoint on the setError method on packet and it never gets called. The only thing I can think of is that the server is bouncing the message back at me. I can send other messages before and after this one w/o trouble. Those are of type Message though so maybe that’'s the difference.