-
1. Re: Wildfly SuspendController Add OperationListener
ctomc Oct 8, 2017 4:26 AM (in response to mfatih)1 of 1 people found this helpfulIf it doesn't work in domain, that just means you probably did some simple mistake in the subsystem wiring.
any chance you can share your add handlers for extension and any sub resources you might have?
-
2. Re: Wildfly SuspendController Add OperationListener
mfatih Oct 10, 2017 4:02 AM (in response to mfatih)After reviewing code, I realized i pass null ManagementResourceRegistration.registerOperationHandler method which was working standalone mode. I fixed that by following ;
OperationDefinition def= new SimpleOperationDefinitionBuilder(DESCRIBE, ControllerResolver.getResolver("schema-locations")).build();
resourceRegistration.registerOperationHandler(def, GenericSubsystemDescribeHandler.INSTANCE,false);
The extension code generation of maven archetypes is for Wildfly 8.0. It would be nice to add new archetype for wildfly 10+
Thanks for response.
-
3. Re: Wildfly SuspendController Add OperationListener
ctomc Oct 10, 2017 6:15 AM (in response to mfatih)1 of 1 people found this helpfulah describe handler, that should be even more simplified than that. yeah the archetypies are outdated, but samples are much more up-to-date
wildfly-archetypes/wildfly-subsystem-example at master · wildfly/wildfly-archetypes · GitHub
describe handler should be registered only on root resource, and as follows
registration.registerOperationHandler(GenericSubsystemDescribeHandler.DEFINITION, GenericSubsystemDescribeHandler.INSTANCE, false);
and noting else for it is needed.