AS7-5547 ignore empty Dependencies: entry in a manifest
DomainTestSuite - added support for execution on mix of multiple JVMs.
[AS7-6379] await connection closed when reloading
Move resources to correct location
Move JCA metrics test resources
Move resources for transport guarentee test case
AS7-6782 JAX-RS EJB integration does not generate component name correctly
[AS7-6379] add missing close handler
[AS7-6781] Make non-final constants final; reduce visibility in some cases
AS7-6780 Use latest schema versions in default config

Also change StandardConfigsXMLValidationUnitTestCase to only pass if the configs are using up to date schemas
cleanup jpa dependencies
cleanup jaxr leftovers
Make osgi http-service use web-common api
Add context wrapper concept for OSGi HttpService
[AS7-6774] Add test coverage for shared HttpContext
[AS7-6777] Missing Resource Adaptor dependency

The RA Activator service created by a pooled connection-factory
service requires an explicit dependency to the default bootstrap
context service to ensure it is properly started.
[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.

* refactor messaging's SecurityActions (based on ExtensionAddHandler
  snippet)
AS7-6652 Add ability to customise timer SQL based on database type
AS7-6786 Hibernate test cases do not close the session factory
Potential OOM fix