From a design point of view it doesn’t sound right to try to hook into that message on the client. For the console to make use of that it would need to correlate some async notification from the server with the deployment request so it could inform the user of the negative effect of that request. And if we can do that in the console it makes more sense to do it server side in the operation handling and fail the operation with an error message.

On Aug 30, 2016, at 2:01 AM, Martin Stefanko <mstefank(a)redhat.com&gt; wrote: Forwarding to the mailing list. ---------- Forwarded message ---------- From: Martin Stefanko <mstefank(a)redhat.com&gt; Date: Thu, Aug 25, 2016 at 1:07 PM Subject: ContainerStateMonitor To: david.lloyd(a)redhat.com Hello David, For my issue [1] I need to propagate log massage from the ContainerStateMonitor [2] to the HAL console. As I have no experience with the wildfly-core may I ask if there is some easy way to this? What I see in HAL we are using operations directly on CLI. I would like to use something in style of events and listeners if it is possible. Thank you. [1] https://issues.jboss.org/browse/JBEAP-5036 [2] https://github.com/xstefank/wildfly-core/blob/master/controller/src/main/... Martin Stefanko Associate Software Engineer JBoss Sustaining Engineering Team Red Hat Czech s.r.o. _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev