WildFly usage

WildFly is another great Java EE implementation. It was known as JBoss AS, but changed its name some years ago (although we still have the JBoss EAP as the enterprise-production ready version). As its administration and use are slightly different from Apache TomEE and GlassFish, it's worth having a proper look at it.

Getting ready

First, you need to download it to your environment. At the time of writing, WildFly has no Java EE 8-compatible version (actually there is only GlassFish 5). However, the tasks covered here shouldn't change in a future version, as they are not attached to the Java EE specs. To download it, just visit http://wildfly.org/downloads/.

This recipe in based on version 11.0.0.Final (Java EE7 Full and Web Distribution).

Wherever possible, we will focus on doing the tasks using the configuration files.

How to do it...

Refer to the following detailed tasks.

Deploying EAR, WAR, and JAR files

For EAR and WAR files, the deployment folder is:

$WILDFLY_HOME/standalone/deployments...