probably a classloader issue, if you have that class in the webapp you won't be able to see it from the webappclassloader itself
typically those go in the server classes a la a module -- jesse mcconnell [email protected] On Sun, Apr 24, 2016 at 1:01 PM, Rj Ewing <[email protected]> wrote: > I am trying to set a custom errorHandler for my web app, but am getting a > noSuchMethod Exception on WebAppContext: > > java.lang.NoSuchMethodException: class > org.eclipse.jetty.webapp.WebAppContext.setErrorHandler(class > biocode.fims.rest.FimsErrorHandler) > > > I'm using jetty 9. My jetty-env.xml looks like: > > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" " > http://www.eclipse.org/jetty/configure.dtd"> > > <Configure class="org.eclipse.jetty.webapp.WebAppContext"> > <Set name="errorHandler"> > <New class="biocode.fims.rest.FimsErrorHandler"/> > </Set> > </Configure> > > > When I look at > http://download.eclipse.org/jetty/9.3.8.v20160314/apidocs/org/eclipse/jetty/webapp/WebAppContext.html, > it seems that the WebAppContext should have a setErrorHandler method > > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
