Keeping a customized xml configuration file for WildFly is inflexible and it can sometimes break the test suite depending on the version of WildFly, because the same xml file doesn't necessarily work with all WildFly versions.
Tests which need particular configuration changes should do that using WildFly management APIs and clean it up after themselves.
Agreed, I had this in mind as well. Thansk for opening this! We're not too familiar with using the management API from Arquillian / Maven or other automated integration tests.
Are you going to contribute this yourself? If not it would be useful to have some pointers, I suppose you might know of some examples doing similar things.
No problem, I can do that, probably around next week.
We can either use the bare ModelControllerClient capabilities from official WildFly libraries, or use the QE-developed library Creaper (https://github.com/wildfly-extras/creaper) which adds some abstraction on top of that to make it easier to use.
That depends how much of these configuration changes we expect to have in the future - if it's just about adding JMS queues, then I would say the bare ModelControllerClient will probably suffice and will be more lightweight...