Versions Compared

Old Version 4

changes.mady.by.user Harald Wellmann

Saved on

compared with

New Version 5

changes.mady.by.user Harald Wellmann

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Despite its name pax-exam-container-wildfly80, this test container supports all 8.0.x and 89.1.x releases of WildFly and all newer ones, as long as the WildFly embedded API does not change in an incompatible way. It does not support WildFly 10.x or higher. With the WildFly Core split of the 9.x release line, a new embedded API was introduced in WildFly Core, while the old JBoss AS API still exists. This old API was removed in WildFly 10.0.0.Beta1. WildFly 9.x can be used with pax-exam-container-wildfly80 or pax-exam-container-wildfly90.

This is the standard lifecycle of the JBoss WildFly container:

  1. If the directory configured in pax.exam.wildfly80.home is empty or does not exist, the latest WildFly distribution Maven artifact (currently 8.1.0.Final) is downloaded and installed in that directory.
  2. The directory configured in pax.exam.wildfly80.config.dir (defaulting to src/test/resources/wildfly80-config) is used as WildFly configuration directory by setting the system property wildfly80.server.config.dir.
  3. If pax.exam.wildfly80.home is non-empty, Pax Exam does not copy any configuration files and works with the existing installation in that directory, throwing an exception if the JBoss module launcher cannot be found in the expected place.
  4. WildFly is started via org.jboss.as.embedded.EmbeddedServerFactory.create().
  5. Any Java EE modules configured by the user are deployed.
  6. A WAR probe is built and deployed.
  7. All tests contained in the probe are executed within the container.
  8. All Java EE modules (including the WAR probe, if any) are undeployed.
  9. JBoss AS is stopped.
  10. The framework storage is deleted (depending on the configuration options).

...