I’‘ve been playing with the new IQ facilities and it looks good. However, the jabber people have thrown a monkey wrench into the works. One particular IQ protocol, “Last Active” (JEP-0012), returns data as an attribute of the query tag instead of as sub-elements. Seems rather pointless for them to do it that way since as far as I’‘ve seen, there aren’'t any others that do it that way.
Anyway, as a solution, perhaps the parseIQ method of the IQProvider interface could leave the parser on the opening query tag instead of advancing it to the next tag (which in the case would be the closing query tag) so the routine could get access to the attributes of the query tag.
I haven’‘t tried it yet, but I’'m assuming that my parseIQ routing will be able to back up the parser to point the the query tag again as a work-around.
Also, it would be convenient if the attributes were used to set beans by parseIQWithIntrospection…
Also, are you planning on using this same try of mechanism for handling “x” stuff embedded in message packets as well?
Thanks & take care,