-
1. Re: Update deployment scanner with management API
ctomc May 29, 2015 10:17 AM (in response to sanjeev.gour)Sanjeev Gour wrote:
The code is this-
ModelNode request = new ModelNode();
request.get(ClientConstants.OP).set("read-resource");
request.get("scanner").set("default");
request.get(ClientConstants.OP_ADDR).add("subsystem", "deployment-scanner");
Well, you have wrong address here
you should have something like this
ModelNode request = new ModelNode();
request.get(ClientConstants.OP).set("read-resource");
request.get(ClientConstants.OP_ADDR).add("subsystem", "deployment-scanner").add("scanner","default");
-
2. Re: Update deployment scanner with management API
sanjeev.gour Jun 4, 2015 7:57 AM (in response to ctomc)It worked for me.
Thank you Tomaz.
-
3. Re: Update deployment scanner with management API
sanjeev.gour Jun 4, 2015 8:07 AM (in response to sanjeev.gour)A related question. A change to this property is ultimately reflected in the standalone.xml file, so if I enable the zip deployment at runtime, it is persisted on next restart remains enabled. I know when I want to enable it and but looking for an appropriate place for disabling it again after all the zip artifacts are deployed. I have some workarounds like I can disable it on server shutdown but just wanted to check if there is a better way.
Thanks.