<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I have noticed that at the moment we don't have a solution for how to deal with server changes that need to happen before the deployment (e.g. adding a security domain).<div><br></div><div>At the moment this is hacked up by having the @Deployment method connect with a hard coded URL, and performing any setup it needs to do.</div><div><br></div><div>I have come up with a solution to this: <a href="https://github.com/jbossas/jboss-as/commit/5bbdbb1f7428300982aeafc8e73864e817246ac7">https://github.com/jbossas/jboss-as/commit/5bbdbb1f7428300982aeafc8e73864e817246ac7</a></div><div><br></div><div>If you need to do any setup in your test class you simply annotate it @ServerSetup(MySetupClass.class) (where MySetupClass implements ServerSetupTask).</div><div><br></div><div>You can then do any server setup/cleanup necessary in your MySetupClass using the ManagementClient that is passed to the method.</div><div><br></div><div>At the moment the implementation is quite simple (only one action per test, superclasses are not examined etc) but if more functionality is required it should be fairly easy to implement.</div><div><br></div><div>Stuart</div><div><br></div></body></html>