Java Reference
In-Depth Information
Once this is done, please ensure that your WildFly instance is running. Click on
Apply
to
save your configuration and then click on
Run
to execute the deployment of the applica-
tion. The Maven plugin will activate and once it is verified that all classes are up to date,
start deploying the applications to WildFly using the remote API. Note that you do not
need to pass any username or password for the deployment. This is possible because you
are deploying your application from the same machine that WildFly is installed on. A loc-
al user authentication is done under the hood so that programmers will not need to cover
this on their development machines.
After issuing the command, you should expect a success message on the Maven console,
as shown in the following code:
INFO: JBoss Remoting version 4.0.3.Final
[INFO]
---------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
---------------------------------------------------------------
On the other hand, on the WildFly console, you have quite a verbose output that points out
some important EJB JNDI bindings (we will return to it in a minute) and informs us that
the application has been deployed correctly. This is depicted in the following code:
09:09:32,782 INFO [org.jboss.as.server]
(management-handler-thread - 1) JBAS018562: Deployed
"ticket-agency-ejb.jar"
