Hello,
It turned out that the "sjsxp" library which JAX-WS RI v2.1.3 uses makes Tomcat
behave this way. I tried a different version of JAX-WS RI (v2.1.7) which
doesn't use the "sjsxp" library anymore and it solved the issue.
A very similar issue posted on the Metro mailing list:
http://metro.1
On 15/12/2018 12:15, Kok How Teh wrote:
> Can you share with me your JSP for test? Thanks.
It was in a previous mail in this thread:
A web app with a single JSP (below) deployed to a clean Tomcat 9.0.x
install shows this is the case.
=== start JSP ===
<%= application.getAttrib
Can you share with me your JSP for test? Thanks.
On Fri, Dec 14, 2018 at 7:50 PM Mark Thomas wrote:
> On 14/12/2018 11:15, Kok How Teh wrote:
> >> Have you configued "containerSciFilter" on the Context?
> > No. I don't
> >
> >> Have you removed any JARs from Tomcat's lib directory?
> > These ar
