I assume this is expected behaviour so I have logged it against documentation. I set antiResourceLocking in the context.xml file for my application, I then made some changes to a "running" JSP, expecting Tomcat to detect the changes and re compile. Reading around I found that using antiResourceLocking causes tomcat to copy the webapp to a temp folder. My guess is that the jsp file I am editing in the webapps/app directory is no longer the one that tomcat is using, and hence I see no changes. Probably should say this in the Context Reference documentation.
You're right, will update documentation right now.
Fixed, thank you for reporting this.
Is there any workaround? Thanks