Deploying a new EAR in WildFly 15.0.1.Final - changes don't take effect

notify Mar 4, 2019 1:12 PM

Only really noticed it WildFly 15. When I deploy an EAR, which has changes to the JSF PrimeFaces front end the changes aren't always available on deployment and take a number of re-deploys and clearing of caches to see them in the front end.

Every time I deploy a newly built EAR I do the following.

Remove the old EAR using the HAL Management Console

Stop WildFly (control c)

rm -rf /usr/local/Cellar/wildfly-as/15.0.1.Final/standalone/tmp

Restart WildFly

Deploy the new EAR using the HAL Management Console

Clear the Google Chrome cache

Anything I'm missing.

1. Re: Deploying a new EAR in WildFly 15.0.1.Final - changes don't take effect

jamezp Mar 5, 2019 2:08 PM (in response to notify)

Doing all of that should not be required. You should just simply have to redeploy the application. Clearing the tmp directory and stopping WildFly should never be required. Clearing the Chrome cache or doing a full refresh may be required, but the other steps should not be.

--
James R. Perkins
Actions