Hello, I'm dani, developer of emite gwt xmpp library.
I'm having problems entering in a new instant room. Here are the stanzas:
---- (i've changed < and > 's by #)
SERVER:
<presence to="test1@localhost/1221677570386"
from="testroom1@rooms.localhost/user1221677570514"
xmlns="jabber:client">
<x xmlns="http://jabber.org/protocol/muc#user">
<item role="moderator" affiliation="owner"
jid="test1@localhost/1221677570386" />
<status code="201" />
</x>
</presence>
CLIENT:
<iq id="rooms_1"
to="testroom1@rooms.localhost/user1221677570514"
from="test1@localhost/1221677570386" type="set">
<query xmlns="http://jabber.org/protocol/muc#owner">
<x xmlns="jabber:x:data" type="submit" />
</query>
</iq>
SERVER:
<iq xmlns='jabber:client'
from='testroom1@rooms.localhost/user1221677570514'
to='test1@localhost/1221677570386'
id='rooms_1'
type='set'>
<query xmlns='http://jabber.org/protocol/muc#owner'>
<x xmlns='jabber:x:data' type='submit'/>
</query>
</iq>
as you can see, the server is answering the same IQ the client sent. what i am doing bad?
thanks!!
Check how other clients work. Check if it's a bug in ejabberd.
Did you try to perform the same action with a well established Jabber client? For example Psi, Gajim, or Tkabber. Those clients allow you to see the XMPP stanzas, so you can check how they work.
If you suspect that ejabberd is not compliant to some part of XEP-0045, you can check if the problem is already reported in the . If it isn't a known bug, you can comment here, and also what ejabberd version you used and how to reproduce the problem.