Kabir Khan created WFLY-4346:
--------------------------------
Summary: Revisit how the model validation happens
Key: WFLY-4346
URL:
https://issues.jboss.org/browse/WFLY-4346
Project: WildFly
Issue Type: Feature Request
Components: Domain Management
Reporter: Kabir Khan
Assignee: Brian Stansberry
Fix For: 9.0.0.Beta1
Currently the ValidateModelStepHandler is triggered by AbstractAddStepHandler, and does
not seem to be triggered for writes.
Also if used in a composite along the lines of
{code}
[standalone@localhost:9990 /] batch
[standalone@localhost:9990 / #] /system-property=xxx:add(value=test)
[standalone@localhost:9990 / #] /system-property=xxx:remove
[standalone@localhost:9990 / #] run-batch
{code}
the handler will get triggered at the end for the add. It will fail for the add since
there is no such resource. While that is easy to work around by checking for a
NoSuchResourceException around the OC.readResource() it seems that what triggers the use
of the ValidateModelStepHandler should be more an intrinsic part of the controller which
knows what has and has not been added/removed/written to.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)