Strophe.Connection.addHandler does not work if Strophe.Connection.sendIQ is called

Question

I have a question about Strophe.Connection.addHandler and Strophe.Connection.sendIQ. The code below may work:

Strophe.Connection.addHandler(context.onMessage, null, 'message') onMessage = function (msgXML){ var to = msgXML.getAttribute('to'); var from = msgXML.getAttribute('from'); var fromBareJid = Strophe.getBareJidFromJid(from); var type = msgXML.getAttribute('type'); var elems = msgXML.getElementsByTagName('body'); var body = elems[0] var text = Strophe.getText(body); return true; } 

But if I call setContactData after addHandler is called, the onMessage method will never call back, but the onRoster method can be called after sendIQ.

 setContactData = function(){ var iq = $iq({ type: 'get' }).c('query', { xmlns: 'jabber:iq:roster' }); Strophe.Connection.sendIQ(iq, context.onRoster); } onRoster = function(iq){ $(iq).find('item').each(function(){ var jid = $(this).attr('jid'); // transform jid into an id var jid_id = CommonUtil.getNameFromJid(jid); userList = userList + "','" + jid_id; }); 

Why can't I call onMessage? What is the reason? What am I missing?

Answer 1

try the following:

 addHandler(context.onMessage, null, 'message', 'chat')//or 'normal' 

from Wrox Professional XMPP Programming with JavaScript and jQuery Book:
The addHandler () function takes one or more parameters. The first parameter is a function that is called when the corresponding stanza is received. The remaining parameters meet the criteria.
A complete list of these parameters is shown in this abbreviated definition of a function from the Strophe source code:

 addHandler: function (handler, ns, name, type, id, from) { // implementation omitted } 

If any of the criteria is null or undefined, any stanza will match. Otherwise, stanzas will only match if they meet the criteria for equality of strings in a certain part of the stanza.
The last four criteria - name, type, id and from - specify filters by stanzas element name and type, id and from attributes. These four criteria are checked only on the top-level element, and not on any of the elements descendants. The first criterion, ns, is slightly different, and it is checked for a top-level element as well as for its immediate children. You understand why soon. The name criterion will almost always be null to match any stanza or single message, presence, or iq. In the addHandler () example, a handler is created that will be called for any stanza received.
Type, identifier and criteria correspond to the main attributes and stanzas.
You can use the type to distinguish between regular chat messages and group chat messages or to separate stanzas of the IQ result from the lines of IQ errors. The id criterion is often used to process responses to specific requests, such as the IQ result associated with a particular IQ-get request.