On Tue, Aug 06, 2013 at 07:29:54AM -0400, Stuart Douglas wrote:
> >> Great - so this means Wildfly will recompile .jsp files
when changed,
> >> correct
> >> ? Anything else ?
> >
> >Nope, this is just the existing JSP development mode setting, its just that
> >it will all be controlled by 1 flag now.
>
> dammn - any plans on allowing jsp files to be recompiled when changed ?
I actually mean't no, it does not do anything else, the JSP development mode setting
should allow JSP's to be recompiled.
ah gotcha - you had me worried for a bit there ;)
> >> >- Disable caching so file changes are picked up
straight away
> >>
> >> Okey - haven't really noticed caching happening in the past though
(except
> >> when VFS was put in front of seam ear's in AS5 days).
> >
> >Without this Undertow will cache static resources by default, so if you
> >modify a html page it will not be picked up. We don't check for changes
> >because checking the file timestamp is actually quite a slow operation.
>
> yikes - didn't realize undertow would do caching that way....:/
I may not be that obvious, because it takes a few hits (usually 5) for Undertow to decide
to cache the page. The cache does support expiry due to max age, but at the moment it is
disabled in the AS7 integration code.
If you are deploying a non-exploded war I think that infinitive time to live makes sense,
and will give you best performance. For exploded wars I have started working on a
invalidation thing
that works using JDK7 watch service, and falls back to polling on JDK6.
great - I actually thought JDK7 would be a requirement for undertow/WF8, is that not the
case ?
/max