On 06/06/2024 11:01, Jeroen Hoffman wrote:
Hi all,
We've found a side effect of change #68721 [1] in Tomcat 10.1.20 that
we'd like to notify you about.
We're using Apache Freemarker for back-end templating, and its NodeModel
class uses reflection to determine what classes to use for xpath,
thereby catching IllegalAccessError, see [2].
Per change #68721 a IllegalAccessError is caught as LinkageError and
turned into a Throwable, NoClassDefFoundError in our case, see [3], and
then falls through that block in NodeModel and errors out.
So this change in Tomcat alters the behaviour in Freemarker, which I
assume was unexpected. We can (and must) work around it, preventing the
IllegalAccessError, but still, maybe you'd like to improve again or have
other thoughts?
How are you getting from the original IllegalAccessError to a
NoClassDefFoundError? Tomcat should re-throw the original
IllegalAccessError.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
