[WFLY-3320] : Deployment scanner treats zipped content as managed.
When the deployment scanned is an archive then it is added to the content repository just like a file would be.
Merge pull request #49 from ehsavoie/WFLY_3320

[WFLY-3320] : Deployment scanner treats zipped content as managed.
WFLY-3668 Change startup script to read new logger code in 9.x
[WFLY-3603] Add global resource notifications

Runtime attributes does not store their values in the resource models
and their read handler must be called before and after their write
handler to get the old and new value of the attribute.

JIRA: https://issues.jboss.org/browse/WFLY-3603
Merge pull request #59 from jorsol/check_log_string

WFLY-3668 Change startup script to read new logger code in 9.x
Merge pull request #62 from jmesnil/WFLY-3603_runtime_attribute-value-written_notification

[WFLY-3603] Add global resource notifications
[WFLY-3169] Emit local JMX notifications

* Emit JMX notifications based on WildFly's own notifications
* Notification is not supported for remote JMX connections.
  Only code that can have access to WildFly's MBeanServerService can
  effectively add/remove notification listeners.
* WildFLy notification are not converted to their idiomatic JMX
  counterpart (eg WildFly's attribute-value-written is not converted to
  a JMX's AttibuteChangeNotificaiton)

JIRA: https://issues.jboss.org/browse/WFLY-3169