I reported the bug to Tigase developer team, but they answer me the following:
Thank you for the link to the spec. The spec indeed says that only one element is allowed. I also remember discussions on the XMPP mailing lists about this and many members suggested that more elements should be allowed. This is probably the reason why most of clients accept more than 1 element in the "set" request.
The specification allows for sending only one element because it discusses a different use case. This section is about changing an item (adding, removing, updating). In this scenario it makes sense to allow for only one item in the request. However, in case of out use-case where we push entire roster, putting a single item in a request would be highly inefficient.
So I can see a few options for you:
- Modify the library you use to accept more than one item in roster "set" request
- Modify Tigase's code to push only 1 item in the "set" request
- Switch to a different library which accepts more items in "set" request out of the box. Our, Tigase JaXMPP library handles this very well.
Anybody could say me if exist a workaround in smack for Dynamic Roster?, or I have to modify the framework.
Thanks again.
