The problem here was, that the presence's 'to' attribute was overridden on each iteration, making the if statement fail after the first iteration.

ofmeet plugin - ready for openfire 3.10 beta release

OF-859: Fix SQL syntax error [pubsub]

Update statement for default node configuration was missing a comma

OF-857: Properly configure Jetty connectors

Update for earlier fix to properly construct and initialize HTTP/S
connectors using configurable resource limits.

OF-857: Improve thread pool management

Update default QTP configuration for admin console and BOSH connectors;
added new configuration property "adminConsole.serverThreads" with a
default of 2

OF-859: Pubsub fix; misc cleanup

This fixes a problem with a static final reference in the Node.class. It
also addresses a couple of minor issues discovered during pubsub
testing:
- PubSubPersistenceManager should return an editable collection rather
than a read-only collection for published items
- SequenceManager defaults should use a blocksize of 5 for frequently
used tables
- LocaleUtils should catch and log a MissingResourceException and return
the key in lieu of the missing value (by convention)

OF-857: Fix C2S locking issues

Updates the MINA 2.0.9 core to fix a locking issue documented here:
https://issues.apache.org/jira/browse/DIRMINA-995

Also updates connection manager and thread pool configurations to better
allocate resources within the JVM.

Don't return incorrect-encoding when receiving '='

when performing SASL authentication.

Since 3eadecb6 Openfire would return
incorrect-encoding when a SASL auth packet would contain just a single
equals sign ('='). But this is correct (client) behavior according to
RFC 6120 6.4.2.

Related to OF-736

07:25:42 PM SENT (2109957412): <stream:stream xmlns='jabber:client' to='igniterealtime.org' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
07:25:42 PM RCV  (2109957412): <?xml version='1.0' encoding='UTF-8'?><stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="igniterealtime.org" id="1d96e3b3" xml:lang="en" version="1.0">
07:25:43 PM RCV  (2109957412): <stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</mechanism><mechanism>JIVE-SHAREDSECRET</mechanism><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compression xmlns="http://jabber.org/features/compress"><method>zlib</method></compression><auth xmlns="http://jabber.org/features/iq-auth"/><register xmlns="http://jabber.org/features/iq-register"/></stream:features>
07:25:43 PM SENT (2109957412): <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'>=</auth>
07:25:43 PM RCV  (2109957412): <failure
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><incorrect-encoding/></failure>

Open Meetings Plugin version 0.0.3

Conflicts:
	src/plugins/ofmeet/plugin.xml

OF-565 use thread local instead of map with threads hashcode as key (this could lead to collissions)

Change OF min version to 3.9.4

Since OF 3.9.3 has a bug whereby it thinks 3.10.0 is older than 3.9.3,
this causes a problem as OF 3.9.3 will attempt to install plugins that
it can not run.  This change puts the 3.10.0 plugins at a release that
will not happen, which keeps them affectively from getting installed.

Resolve the error when deleting group administrators

Reinstall the Configure encryption issues

REST API plugin version 0.1.0

Doesn't filter iq results that needs to be delivered to local muc users.

Ofmeet plugin. change date format to US

Openfire Meetings plugin. Initial release

fix enabling https admin port without http enabled

If the http admin port is disabled enabling https fails because it tries to copy from an uninitialized httpd configuration. An exception is generated and the server runs but you have no admin interfaces.

The only httpd configuration parameter that might have needed to be copied is setSendServerVersion. This just makes a new 'empty' connection and sets that parameter before continuing on as usual.

According to the documentation you're supposed to be able to use https admin without http admin. This situation appears to be a side effect of some code changes later on where someone just forgot to consider this.

More info here in my bug report:
https://igniterealtime.jiveon.com/message/241471