WFLY-2468 MappingModuleDefinition is incorrectly constructing the write-attribute handler
WFLY-1469 WFLY-160 add support for runtime reloadable operations

- new model version 2.0
- new parser version 2.0 & xsd
- better runtime operation tests
- all operations are runtime executable now
- update XSD & default confguration
WFLY-2532 @Transactional and TransactionPhase does not work
Fixed init script for Ubuntu 13.10

In Ubuntu 13.10 they changed /lib/lsb/init-functions making /full/path/to/executable as required parameter of pidofproc. As result this init script stopped working for Ubuntu 13.10. Why did they do that? I suppose because man page for pidofproc specifies this parameter as required. Will my change affect existing distributions? I've checked init-functions for Debian Wheezy and Ubuntu 12.04, they silently ignore all parameters except pidfile. Why path to executable is java, why not $JBOSS_SCRIPT? Because man page for pidofproc says that pid should correspond to executable, and pid corresponds to java process. Although current implementation in Ubuntu 13.10 doesn't check it (indeed any additional parameter would resolve this issue). Testing done: Manually checked that after modification the init script can start and stop service in Debian Wheezy, Ubuntu 12.04, 13.10 and there're no pending abandoned wildfly processes.
Introduced JAVA variable in Debian init script to be used with pidofproc.
Use virtual file based resource manager to make sure deployment overlays work correctly with Undertow
WFLY-2266 Make deployment overlays feature able to replace application libraries
Temprorary change to work around watch service issue
Update to work with latest Undertow
[WFLY-2519] Useless mod_cluster drained context logging (...UndertowContext@3abb2fbc)
[WFLY-2570] hornetq-server operations are not listed in domain mode

* add missing RUNTIME_ONLY flag to all hornetq-server operation handlers

JIRA: https://issues.jboss.org/browse/WFLY-2570
WFLY-2566 javax.inject.Singleton not recognized as a bean defining annotation
WFLY-2559: fixes NPEs at IronJacamarResourceCreator
simple fix where WeldStartService sets dependencies for the binding services directly, if deployment is an EAR using in-order deployment
WFLY-2564 AJP listeners not recognised as being secure
[WFLY-2469] Upgrade to HornetQ 2.4.0.CR1

HornetQ depends on Netty 4 which has changed its package from
org.jboss.netty to io.netty.

* dependency changes:
  * upgrade HornetQ to 2.4.0.CR1
  * add dependency to Netty 4.0.12 (GAV io.netty:netty-all:4.0.12)

* module changes:
  * add io.netty module for Netty 4.x (and keep org.jboss.netty module for
    Netty 3.x)
  * add hornetq-native jar to org.hornetq module (this jar contains now
    both Java classes and native libraries)
* management model changes:
  * remove servlet-connector resource that was using Netty 3.x HTTP
    tunneling Servlet and was added a workaround until HornetQ support
    one-port to be accessible over HTTP
[WFLY-2346] add messaging 1.4 XML namespace

* add support for the 1.4 messaging namespace (corresponding to 1.3.0
   mananagement model)

* managemement changes introduces in 1.4 XML / 1.3.0 management
  * new max-saved-replicated-journal-size attribute for hornetq-server
    resource
  * new group-timeout & reaper-period attributes for grouping-handler
    resource