the ones who develop JSPs may battle with this already: once you change a JSP and upload it, the new version doesn't become active until after the next aveksa_server restart. Alternatively, as discussed in @JSP Validation in 7.2 you could version your JSPs.
Both have disadvantages. The former takes ages and I don't want spent valuable time waiting for this thing to come back and the latter creates tons of file that I may need to clean up one-by-one and I may need to change config here and there to adjust to the new file name.
The quickest way I found out is to disable the compiler cache altogether. On development systems this is totally doable, low risk and can be rolled-back easily.
- find your
aveksa-standalone-full.xml(standard install in
- edit it and fine the line
<jsp-config/>and change it to
<jsp-config development="true" check-interval="1" modification-test-interval="1" recompile-on-fail="true"/>
- Save the file and restart the server
Hope this helps