Missing tearDown and cleanup calls
HORNETQ-1218 / https://bugzilla.redhat.com/show_bug.cgi?id=959789  Making sure Bridges will reconnect to their proper nodes
Merge pull request #1099 from clebertsuconic/master

HORNETQ-1218 / https://bugzilla.redhat.com/show_bug.cgi?id=959789
Update JMS API to 2.0

* update Maven GAV to

  org.jboss.spec.javax.jms:org.jboss.spec.javax.jms:1.0.0.Alpha1-SNAPSHOT

* add methods that throws UnsupportedOperationException
* no new interfaces implemented
tenative implemenation of injection for JMSContext
implementing JMS 2.0 methods
delete hornetq-jms-cdi
HORNETQ-1209 Add bodies to ConnectionFactory.createContext(*)
clean jms test
[HORNETQ-1213] JMS 2.0 MDB activation properties

* add destinationLookup property to HornetQActivationSpec
  (backed by destination field + useJNDI set to true)
* add connectionFactoryLookup property to HornetQActivationSpec
  to look up the JMS ConnectionFactory from JNDI
HORNETQ-1209 Fix Message.receiveBody* implementations.
HORNETQ-1209 Implement Message.isBodyAssignableTo(Class) and getBody(Class)
HORNETQ-1209 Change stubs to method forwarding calls
HORNETQ-1209 JMSProducer.send(dest,map) method body
HORNETQ-1209 Implement more methods of HQJMSProducer
HORNETQ-1219 Fix inconsistent 'null' property behavior.

Spec says setObjectProperty(...) should be the same as 'typed' alternatives.
Notice that our implementation of the typed variants do not ignore 'null'
values.
HORNETQ-1207 JMSProducer methods