After banning, the user is not kicked from the room. The user is added
to the ban list so they can't re-join the room or post messages, but
they are not kicked out of the room so the user can still receive messages
sent to the room.

The problem is an additional check for isMembersOnly() was only allowing users
to be kicked from members only chat rooms. Whenever a user is marked as an
outcast they should be kicked from the room regardless of if the room is a
members only room or not.

Looks like this problem was introduced in commit
822abb01

Based on the MUC spec it should be sending "outcast" on banning.

Looks like this was introduced in commit 822abb01

Denote Openfire 4.0.0 Release

OF-454 Reflect presence to originator

Only use SSLv2Hello for client-mode

OF-1004: Apply i18n to admin console

Fix some javadoc warnings

OF-821: Count occupants by nickname

OF-1034 Check for existing sessions properly

Returns the count of nicknames rather than the number of connections
(full JIDs), which will now also match the list of occupants.

solve the memory leak problems which is caused by add LocalMUCRoom ob…

OF-821: Prevent duplicates for MUC item query

Drop unnecessary null check.

Corrects issue with multiple JIDs sharing a nickname (masquerading)

Replaced the 'set this var with this translation' definition for
a functional equivalent but easier-on-the-eyes definition.

Fix implementation bug for XEP0049.

OF-1033: Should use the correct status code.

OF-1029: Allow web.xml override via overlay

OF-1033: Users should be notified of MUC service shutdown

Fix implementation bug for XEP0049. The comment in Line 105: "If the name and namespace of the element matches another" is correct, but the implementation is wrong, it checks "username and namespace" rather than "name and namespace".

Cleanup websocket plugin

This commit notifies all users that are in a MUC on the local server node of
a shut down of the service. The notification conforms to XEP-0045.

In order to prevent a prolonged shut down, this commit:
- ensures that a shutdown routine is executed just once (instead of for each
  type of interface being shut down: module,component and listener)
- the presence stanza that is sent is constructed using in-memory objects
  only (no database lookups)
- all notification occurs in a thread pool, which will concurrently process
  them, but will terminate forcibly after a certain amount of time.

Update dependencies and documentation to prep for pending Openfire 4.0
release.

OF-1028 Stream Management refactoring

Instead of rerequesting ack for every unack'ed stanza over the
threshold, do this only for every few stanzas. This prevents a storm
of ack-requests when data is transmitted to the client faster than it
can respond.