The default implementation of AbstractRemoteServiceServlet#doUnexpectedFailure(Throwable) <https://www.gwtproject.org/javadoc/latest/com/google/gwt/user/server/rpc/jakarta/AbstractRemoteServiceServlet.html#doUnexpectedFailure(java.lang.Throwable)> calls RPCServletUtils#writeResponseForUnexpectedFailure(ServletContext, HttpServletResponse, Throwable) <https://www.gwtproject.org/javadoc/latest/com/google/gwt/user/server/rpc/RPCServletUtils.html#writeResponseForUnexpectedFailure(javax.servlet.ServletContext,javax.servlet.http.HttpServletResponse,java.lang.Throwable)>, which logs the error with ServletContext#log(String, Throwable). We would like to use Log4j instead. We generally try to avoid overriding methods in 3rd party libraries, but is there another way to swap out the logger? Setting up the JUL-to-Log4j bridge <https://logging.apache.org/log4j/2.x/log4j-jul.html> isn’t a good option at the moment, making a wrapper that implements ServletContext seems much worse, and replacing the application server logger <https://logging.apache.org/log4j/2.x/jakarta.html#replace> didn’t help.
Thanks, Gerard -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/73811356-0d2d-4288-98bb-dfb88e6d5043n%40googlegroups.com.
