Get rid of standalone-full-testqueues.xml file in integration tests

Description

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.

Environment

None

Activity

Show:
Sanne Grinovero
August 17, 2017, 10:22 AM

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.

Jan Martiška
August 17, 2017, 10:54 AM

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...

Assignee

Jan Martiška

Reporter

Jan Martiška

Labels

None

Suitable for new contributors

None

Feedback Requested

None

Components

Affects versions

Priority

Major
Configure