Please submit a documentation change.
Historically, only reloadable was being done. This caused a lot of questions
as to why changes in web.xml were not being picked up. As some refactorings
came, it became easier to perform a stop, then start on the webapp instead of
classloader reload.
-Tim
Hello,
I was unsure if this or -dev was the best place to send this, so I
decided to go with user first.
I recently spent some time tracking down why we would get application
restarts when code changes were pushed to our production environment,
despite having reloadable=false in the
