Versions Compared

Old Version 5

changes.mady.by.user Harald Wellmann

Saved on

compared with

New Version Current

changes.mady.by.user Harald Wellmann

Saved on

Key

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

Pax Exam's WildFly container is a Java EE container without any OSGi support. This By default, this container launches WildFly embedded in the same VM and deploys any Java EE modules configured by Pax Exam options and a WAR test probe built on the fly from the classpath contents. Alternatively, if pax.exam.wildfly80.remote.host is set, the container deploys all modules to a running server via the HTTP management interface.

Info

Despite its name pax-exam-container-wildfly80, this test container supports all 8.x and 9.x releases of WildFly. 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 WildFly container:

  1. If pax.exam.wildfly80.remote.host is set, continue with step 6.
  2. 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.
  3. 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.
  4. 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.
  5. WildFly is started via org.jboss.as.embedded.EmbeddedServerFactory.create().
  6. A deployment manager is created for the given embedded or remote host, using the given management port.
  7. Any Java EE modules configured by the user are deployed.
  8. A WAR probe is built and deployed.
  9. All tests contained in the probe are executed within the container.
  10. All Java EE modules (including the WAR probe, if any) are undeployed.
  11. JBoss AS is stopped.
  12. The framework storage is deleted (depending on the configuration options)If pax.exam.wildfly80.remote.host is not set, the embedded WildFly container is stopped.