Deploying from command line with WildFly
wildfly comes with a Command Line Interface (CLI) with access to administrative tasks.
The CLI is also usable in "non-interactive" mode from scripts. The following command deploys an application:
$WILDFLY_HOME/bin/jboss-cli.sh --connect --command="deploy --force [PATH_TO_WAR]"
Undeploying an application works adequately:
$WILDFLY_HOME/bin/jboss-cli.sh --connect --command="undeploy x-ray.war"
WildFly'S CLI, similarly to GlassFish'S, is only thin wrapper over a HTTP interface. You could also interact with the server directly over HTTP.
Also the CLI returns proper exit codes and gives you so feedback about the command. Exit codes are a significant benefit over copying a file to a deployment directory.
See you at Java EE Workshops at MUC Airport or on demand and in a location very near you: airhacks.io!
you could also extend the loadr github project with wildfly support.
Posted by Robert on January 16, 2014 at 10:12 AM CET #
I'm actually thinking about extending loadr to support tomee and wildfly.
thanks you for your comment!,
Posted by Adam Bien on January 16, 2014 at 10:30 AM CET #
How much can be done via CLI? Insert/change values in JNDI trees, manipulate JVM settings, ...? How does this compare with Glassfish's asadmin command?
Posted by Kovica on January 17, 2014 at 08:27 AM CET #
in glassfish then you create a domain, all apps, configs,...are in this domain.
When you're doing integration tests, build tests etc with jenkins, it's easy to delete the whole domain and recreate it, to have always a clean starting point.
What's the alternative to a "standalone" glassfish domain in standalone widlfly configuration?
Posted by Jan on April 28, 2014 at 11:14 AM CEST #