Hi, We pre-compile our JSPs. Team Dev uses Tomcat jars for this. And team Sys keeps the Tomcat servers running and up-to-date. Running Tomcat since 5.x or maybe even before. Currently running 9.0.x.
For years it worked fine if we kept the jars versions of team Dev close to the Tomcat server version of team Sys. It was very efficient because versions didn't need to be exactly the same. And we could test versions without doing a turn-key deploy. Occasional rollback of a deploy was also possible, although the JSPs were not compiled with the exact same jar versions. Tomcat 9.0.96 was very painful in this regard. We found the reason for it in https://lists.apache.org/thread/62j98og8xn9p9ovxxj6bfqht85xg2qgz. 9.0.96 JSPs didn't work on 9.0.95 and 9.0.95 JSPs didn't work on 9.0.96 Tomcat. (I didn't check this personally, but trust my colleague in it.) Deploy needed to be turn-key with synchronization between teams on multiple clusters of servers. I'm not here to rant about it. Things can break. But I didn't find any information about solutions on the website/ML. We couldn't be sure that 9.0.97 would have a fix or just have the same incompatibility so decided to push through with 9.0.96. Anyways, I thought it is good to give some feedback about the issue as a user of the product. I think it would have been nice to have a statement about 9.0.96 and pre-compiled JSPs and how future versions would handle this situation. If I missed this statement on the website or in the ML archives than I will happily stand corrected. :-) And now we go further with development and hope that future releases will be as easy as they were before. Regards, Ronald. Â
