Development mode/hot redeploy with Undertow

[christian.bauer]

First, it took me a while to figure out that Undertow is by default caching static resources. It will bite you after a few reloads, very annoying. You have to remove the <servlet-container default-buffer-cache="default"/> setting to disable the caching, this should be documented!

Then I found this discussion about the global development mode, which sounds like the right approach:

[undertow-dev] Undertow development mode

This change apparently didn't make it into Wildfly beta1, and I haven't seen any discussion why. Then I found this change:

https://github.com/wildfly/wildfly/commit/6164704623c46184d75a624c1b9739028267b205#diff-72d237aa7931ff1ac3ced177f978dec8

Does that mean JSPs will be recompiled if <jsp-config development="true"/> is set? This doesn't seem to have any effect, at least not with an exploded WAR deployment.

So how do you guys work with this? Redeploy after every change in a template? Run out of permgen space every 5 minutes?

[jaikiran]

Are you using the latest nightly build or the Beta1 version of WildFly?

[rhusar]

+1 There are likely to be changes since Beta1, so I would recommend to build master and use that before CR1/Final comes out.

[christian.bauer]

Tried the snapshot from yesterday, same behavior.

[jaikiran]

Christian Bauer wrote:

Does that mean JSPs will be recompiled if <jsp-config development="true"/> is set? This doesn't seem to have any effect, at least not with an exploded WAR deployment.

I would expect the changes to the JSP be picked up when that flag is set, even in case of exploded deployments. If that's not happening in the latest nightly build, as you state, then I think it's a bug and I think you should create a WFLY JIRA here https://issues.jboss.org/browse/WFLY