ср, 24 июн. 2020 г. в 19:25, <tomcat-s...@stiprus.com>: > > I have a web application which is failing in RestEasy initialization with an > NPE. It worked for many years until I added a large number of jar > dependencies because of a new development effort. I've debugged the code by > stepping through the Tomcat source to the point I've found where it is > failing. It seems to be a Tomcat bug but of course I'm not convinced since it > is highly more likely it is my problem. > > Tomcat version is 9.0.36, though the failure happens in the Tomcat 8 versions > I've tried as well. > > The NPE is triggered by a single "return null" statement in > org.apache.catalina.core.ApplicationContext line 933. Below is a code snippet > of where the return statement is. In my failing scenario the wrapper is NOT > null and isOverridable is already returning false. So it falls through to > return null. > > So here is my question: Why in the world in the code below does the return > null statement even exist? It seems like the return null at line 933 is the > precondition the code is trying to establish.
This method is documented in the specification of Servlet API (in their javadoc) to return null if such servlet has already been registered. See Java EE 8 javadoc https://javaee.github.io/javaee-spec/javadocs/javax/servlet/ServletContext.html#addServlet-java.lang.String-java.lang.Class- (Following the links from Specifications page https://cwiki.apache.org/confluence/display/TOMCAT/Specifications K.Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
