Docker, Wildfly, your application and the dev life cycle

Hi, using docker it is very easy to have your web application available for testing in a non mocked environment. To be able to manually tweak settings we’ll enable wildflys admin interface.

The idea: have an isolated wildfly installation which runs your application and updates it automatically each time you (re-) create the war-file.

The solution:

1 create a custom wildfly image with a configured admin user

2 run the image and mount your local projects target folder to wildflys deployment folder. This way the deployment scanner will detect an update war file and redeploy the application for you

To illustrate things i setup an example project with bitbucket: dockerized wildfly

About javavolker71

when i do not write posts on this blog, don't work on or try to break my code i'm spending a reasonable amount of time
This entry was posted in JEE7, Unix, wildfly8 and tagged , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s