On 11-Jun-24 18:28, Mark Thomas wrote:
On 11/06/2024 12:30, Mark Thomas wrote:
I need to confirm that it doesn't break the original fix but my plan
is to check clazz after line 2311 and rethrow the original exception
if it is null.
Testing with the original reproducer looks good.
Fixed
On 11/06/2024 12:30, Mark Thomas wrote:
I need to confirm that it doesn't break the original fix but my plan is
to check clazz after line 2311 and rethrow the original exception if it
is null.
Testing with the original reproducer looks good.
Fixed in:
- 11.0.x for 11.0.0-M21 onwards
-
On 07/06/2024 09:04, Jeroen Hoffman wrote:
On 06-Jun-24 18:17, Mark Thomas wrote:
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,
On 06-Jun-24 18:17, Mark Thomas wrote:
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
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,
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
