OF-819 IQs of type error get falsely routed to IQ.createResult() which results in an Exception and connection termination

This can happen, if the session is in wrong status (e.g. if the user has not yet authenticated) and the client responds with an error IQ.
Only reply to an IQ if it is type get or set.

Codecleanup

and add some comments.

OF-810 RFC 6121 Routing Compliance Fix

OF-709: Update Jetty from 7.4 to 9.1.5

Fix OF-799: Select correct input radio on click into the text field.

Move all property keys regarding connection settings into a one class

Upgrade debian package dependencies to openjdk7.

Fix error message if build is started with an java version < 7

Replace deprecated toURL() with toURI().toURL() as per the JavaDoc

This fix fixes the routing, which is described in RFC 6121 8.5.3.2.1. Message

Misbehavior before: Every message addressed to a full JID, whose resource was not available was routed to the bare JID (as fallback). 8.5.3.2.1 specifies, that only chat messages should be routed to bare JID and other message types should either be ignored or bounced with an error.

Behavior now: non-chat messages are delegated to the offline message strategy, which decides, if the message should be ignored or bounced with an error, depending on the settings in offline-messages.jsp.

OF-811 Remove deprecated xml-not-well-formed error in favor of not-well-...

for now.

Fix eclipse project files

OF-736 Openfire should return <incorrect-encoding></incorrect> SASL failure, when not using base64 encoding

and raise those values to 1.7

OF-466

No need to emit a warning message for the MUC history reload limit.

Remove ant-subdirtask since it's automatically generated from source by
the 'anttasks' target.

OF-804 Joining a locked MUC room should return <item-not-found/> instead of <recipient-unavailable/>