On 16 Jun 2016, at 10:29, Kabir Khan <kabir.khan(a)jboss.com>
wrote:
> On 15 Jun 2016, at 23:19, Kabir Khan <kabir.khan(a)jboss.com> wrote:
>
> I have written up analysis/design notes for the new notification registrar mechanism
at
https://developer.jboss.org/wiki/DesignNotesForAbilityToRegisterAListener...
>
> My main doubt is about the usefulness of the
NotificationRegistrarContext.getModelControllerClient() method.
The only reason this
is there is it was there in Brian's original draft. I think I'd like to remove it
for now
> The NotificationRegistrarContext is used by
NotificationRegistrar.registerNotificationListeners(), which in turn is called by a
service's start() method. The service is installed by an add handler. Is my memory of
calling the ModelControllerClient execute methods at this stage a bad thing correct? I
mention that the MCC can be cached for later use by the handlers, which on one hand I
think should be ok since the handlers are executed on asynchronously,
Actually, WFCORE-1157 makes the server state lifecycle events synchronous, so the above
isn't 100% true
> but on the other hand having notification handlers mess around with the model seems a
bit strange as well.
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev