Yep,
I'm probably going to hell for not reporting this through the proper
channels, but I think I've stumbled across a bug in JabberBeans.
When Jabber sends the following packet:
<xdb type='set' action='insert' to='user@elavil' from='sessions' ns='jabber:x:offline' id='905'>
<message id='JCOM_19' to='user@elavil' from='gez@elavil/Desktoppy'>
<thread>C1E549CFFDE38C48BB550A3EB994AA13</thread>
<subject>2</subject>
<body>www</body>
<x xmlns='jabber:x:delay' from='user@elavil' stamp='20010412T22:39:51'>Offline Storage</x>
</message>
</xdb>
JabberBeans seems to lose the "action" attribute.
<xdb to="user@elavil" from="sessions" id="905" type="set" ns="jabber:x:offline">
<message to="user@elavil" from="glattdiez@elavil/Desktoppy" id="JCOM_19">
<subject>2</subject>
<thread>C1E549CFFDE38C48BB550A3EB994AA13</thread>
<body>www</body>
<x xmlns="jabber:x:delay" stamp="20010412T22:39:51" from="user@elavil">Offline Storage</x>
</message>
</xdb>
Just to call it to your attention.
Thanks for your work on JabberBeans so far, it's coming along quite nicely.
By the way, are you planning on making some sort of Offline extension class to handle
serialization of the <offline> tags necessary in the xdb response? currently I'm just
using my own extension wrapper class to do that.
Take care,
Matthew D. Diez
