HORNETQ-1390 Upgrade resteasy to 3.0.9.Final
Merge pull request #1871 from abn/HORNETQ-1390

HORNETQ-1390 Upgrade resteasy to 3.0.9.Final
HORNETQ-1417 OpenWire support -- Producer Flow Control

Implement OpenWire producer flow control. Based on configuration, when
a queue's memory space is full, the producer can either be blocked (via
client side window size or server side blocking), or get a relevant
failure exception. The details are given in this link:

http://activemq.apache.org/producer-flow-control.html
Merge pull request #1870 from gaohoward/master_HORNETQ-1417

HORNETQ-1417 OpenWire support -- Producer Flow Control
HORNETQ-1418 - ha policy changes and refactoring

https://issues.jboss.org/browse/HORNETQ-1418

This patch abstracts the different HA policy configurations into their own classes. This avoids having unrelated configuration elements in the same configuration class or xml chunk.

Because of this the HornetQServerImpl class has been simplified by extracting the different Activations into their own class and moving into the Activation any code that is specific to the actual Activation. This should make it easier to extend or add any new Activation code.
Merge pull request #1872 from andytaylor/hapolicy_changes

ha policy changes and refactoring
BZ-1146506 & HORNETQ-1287  Message does not expire when it is diverted to another queue

https://issues.jboss.org/browse/HORNETQ-1287
https://bugzilla.redhat.com/show_bug.cgi?id=1146506

Diverts were not setting the expiry message during any type of divert.
It seems this was an initial design decision but I don't see a reason why
expiry should be removed between routing and diverting.
Besides this we also fixed the case where the original queue wasn't set
during divert and expiry.
HORNETQ-1419 Server doesn't deploy JMS Objects

When starting a standalone server using 'bin/hornetq run' the server
starts up but the jms objects such as Connection Factories and
Destinations configured in hornetq-jms.xml don't get deployed.

The reason behind this is that the "Run" command (Run.java) starts
the JMSServerManagerImpl without passing in a default config file and
we no longer put the default config dir into the server classpath
with the new startup method.

The fix is add a <jms> entry into hornetq.xml pointing to the default
hornetq-jms.xml file and in the "Run" command we pass the config
(if it configured) to JMSServerManagerImpl so that it will deploys
all the JMS stuff during start up.
Merge pull request #1875 from clebertsuconic/upmaster

BZ-1146506 & HORNETQ-1287  Message does not expire when it is diverted to another queue
Merge pull request #1876 from gaohoward/master_HORNETQ-1419

HORNETQ-1419 Server doesn't deploy JMS Objects
HORNETQ-1411 - Make configuration classes fluent

Make our configuration classes fluent to enable easier integration
fix test interceptor to correctly ignore large message send