Another one that is not documented.
Suppose you have a persistent Multi-User Chat Room (MUC) and room is empty. Apparently to destroy the room, the owner needs to join it, and then call the destroy() method on that room.
See, short and sweet.
Smack API: Destorying persistent Multi-User Chat Rooms
November 16th, 2008 No Comments
Tags: destroy · MUC · Multi-User Chat · Smack
Smack API: No clean way to discover if a multi-user chat room exists
November 16th, 2008 1 Comment
Here’s another one to follow the previous two posts about Smack API and Multi-User Chat issues.
Suppose you want to create a persistent room. Suppose you are not sure if that room already exists. In Smack, and I am not familiar of any other APIs, there is no non-exception-throwing way of doing this.
Fundamentally, a room [...]
Tags: existence · MUC · Multi-User Chat · Smack · XMPP · XMPPException
Openfire/XMPP Multi-User Chat name is registered as all lower-case
November 15th, 2008 2 Comments
Another observation regarding XMPP multi-user chat (aka chat-rooms) to follow on my previous entry. This one is also an odd one.
It appears that Openfire uses all-lowercase names for multi-user chat rooms. So if your room’s name is “myRoom”, it will be saved as “myroom”.
Could not find anything to require this in the XMPP specifications for [...]
Tags: Bug · lower-case · Multi-User Chat · Openfire · Smack · XMPP