This performs the same fix as for PEP, but this time on the PubSub services.

The PEP Service configures leaf nodes to store -1 items by default; however
this value is not corrected by the usual post-configuration checks to 1, and
this in turn means that when gathering the items to return, the single
item is removed.

This patch corrects the issue by setting the maxPublishedItems in the default
configuration to 1 instead.

IQ requests must always be responded to, if only with an error reply. For good
measure, IQ-Ping support was added too.

Simply repeated dwd's commit 73b59106 on Ubuntu Trusty (20160104ubuntu0.14.04.1)

OF-1116: Apply workaround for Java 7/8 compatibility issue

The JDK 7 signature of ConcurrentHashMap#keySet() returns a Set, while JDK 8 signature
returns a KeySetView, which is a new class in JDK 8. As a result, using Java 7 to run
an Openfire instance that is compiled with Java 8 (using the -source/-target 1.7
compilation flags) causes a java.lang.NoSuchMethodError.

To work around this problem, this commit applies a workaround as presented by
Martin Buchholz in https://bugs.openjdk.java.net/browse/JDK-8151366

alter statements (at least in oracle 11g or earlier) do not allow the
COLUMN keyword after ADD in an ALTER statement
Conflicts:
	src/database/upgrade/23/openfire_oracle.sql

OF-1157

Will build on bamboo + debian with java7 as well

Conflicts:
	build/debian/rules

 * will maintain this on the ignite bamboo server as a symlink

The abstract implementation of GroupProvider should not hide the thrown
clause as defined by the createGroup() signature.

When validating a certificate chain, the provided chain aught to be ordered. If our
own ordering fails, we should use the first certifcate of the (unordered) chain,
instead of failing completely.

untested by me, just a simple s/7/8/ with the debian build files

Stored preferences of encryption protocols and/or cipher suites might include
non-supported items. To prevent issues, the list of preferences should be checked
against the currently supported items.

Denote Openfire 4.0.2 Release

Since the release of Openfire 3.9.3, users have reported problems with
"ghost" sessions left on the server. After reviewing the changes that
went into the 3.9.3 release, it seemed the fix for OF-464 may have had
some side effect causing this.

Since Igniterealtime's Openfire was reproducing OF-829, I did a test
whereby the functional changes of Igniterealtime/Openfire#ad08cae9
were reverted.  After 36 hours, there were no ghosts!

This will likely necessitate reopening OF-464.

IQ result should be the last stanza. This way, clients know that the
last archived message has arrived.

Some user providers might not provide a creation date for each user. There's no
reason that the Admin Console should not be able to cope with that.

With the current implementation, any user can send the register IQ to register with
a room as a 'member'. This also allows outcasts, that were banned from a room, to be
able to register again as a member, and eventually re-join the room. The solution is
to prevent outcasts from registering with the room.

In dom4j, the default namespace of an element cannot be set by adding
a namespace that has an empty-string prefix. Although the string
representation of the element will be correct, that namespace is not
being recognized as the default namespace of the element (instead, it
is a namespace like any other prefixed namespace, to be used in child
elements).

The original code depends on a whitespace to be present within the limits
of the element. This is not safe (eg: <message><foo/></message> fails).
Instead, the closing characters ( > or /> ) of the first element should
be used, as that's guaranteed to be present.