Hi, sorry to borrow you, don't hate me. One question: will this implementation breaks 7.0 tree compatibility....or not?
Let me explain: from 7.0.1 to 7.0.70 any Tomcat upgrade is backward compatible ( for my requirements). Any upgrade means a simple drop in war in webapps folder, for me. Now these sanity checks breaks my drop in war. Right, sanity checks introduced in .72 are great but.....i have about 180 jsp with compilation error!....an huge amount of code to be revisited (and wasted time). Can i suppose that other users will have this problem? Really, there is no possibility to solve this? Thanks a lot and, again, sorry to borrow you. Best regards, Agharta Il 26 settembre 2016 17:37:03 CEST, Mark Thomas <ma...@apache.org> ha scritto: >On 26/09/2016 16:32, agharta wrote: > ><snip/> > >> I've searched cause on tomcat official changelog between .70 and .72 >but >> without success. >> >> >> So the question is: why? > >https://bz.apache.org/bugzilla/show_bug.cgi?id=60126 > >The same error handling changes are in 7.0.72. > >Mark > >--------------------------------------------------------------------- >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >For additional commands, e-mail: users-h...@tomcat.apache.org -- Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità .
