OF-819 IQs of type error get falsely routed to IQ.createResult() which r...

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.

Update Junit to 4.11

Update Slf4J to version 1.7.7

Update Junit to 4.11 and add hamcrest - because the method assertThat is working with hamcrest matchers

Extract more properties related to connections

OF-709: Replace servlet.jar (2.5) with servlet-api.jar (3.1)

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