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 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 use
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?
Regards,
Jeroen Hoffman
[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=68721
[2]
https://github.com/apache/freemarker/blob/2.3
jsp/errors/403.jsp
>
>
> Previously on this list it mentioned using the glassfish version. Think
> glassfish is eclipse?
>
>
> org.glassfish.web
> jakarta.servlet.jsp.jstl
> 3.0.1
>
>
> Seemed to work OK.
>
>
>
> On Mon, 5 Feb 2024 at 15:5
On Mon, Feb 5, 2024 at 4:05 PM Mark Thomas wrote:
> >
> > Are there plans to release the 2.0.0 version?
>
> No plans.
>
> Tomcat 10.1.x onwards uses the 1.2.5 taglibs release converted for
> Jakarta EE using the Tomcat migration tool.
>
Thanks for the quick answer!
Could you share some details
base [1] has been reworked 4 years ago to use
jakarta, development version is 2.0.0-SNAPSHOT.
Are there plans to release the 2.0.0 version?
Regards,
Jeroen Hoffman
[1] https://github.com/apache/tomcat-taglibs-standard
-
To
