AS7-6751 JCA lookup UserTransaction in context java:comp instead of java:jboss
Upgrade JBossTS to Narayana 5.0.0.M2
JBTM-1483 Add TXFramework support to XTS Subsystem
JBTM-986.JBTM-1447. WSTX and JTAOverWSAT handlers
AS7-6706 Move Webservices client-config management into an MSC service
JBTM-1516 XTS: Common configuration is not available
AS7-6586 BZ-923382 don't close the EntityManager from the Arjuna reaper thread (to avoid concurrency violation)
[AS7-6752] Activating deferred module phase may return prematurely
Update javadoc script to match new modules dir structure.
Update pom.xml javadoc incl, excl and groups.
AS7-6751 Enabling data source fails if its not persistent
Upgrade to 1.0.6.Final of remote-naming
[AS7-6711] allow read-only access for active operations
[AS7-6699] HornetQ backup mode

When HornetQ is configured to be a backup, it will start and remain
passive (its resources are not deployed, it does not accept any
connections, etc.)

For AS7 hornetq-server's children resources, that means that:
* read-attribute on runtime attributes is a no-op (returns undefined)
* execute an operation on a queue will throw an exception warning the
  user that HornetQ is in backup mode
* add active runtime r/o attribute to hornetq-server

For AS7 services, there are some substantial changes too.
HornetQService default does *not* start the HornetQ server. This is done
by JMSService. This means that any service must not depend on
HornetQService but JMSService to make sure that the server is
effectively started.
JMSService is started asynchronously and the server start is completed
when:
* the HornetQ server has been activated (immediately when it is a live
  node, or after failover if it is a backup)
* and the JMSServerManager is started (and can deploy JMS resources)

It is important for other services depending on messaging services
(queue, jms-queue, topic, connection-factory &
pooled-connection-factory) that these services must NOT be started
until a backup hornetq-server fails over.