It might be that Jetty has a lot more instrumented as gbeans (eg filtermappings, servletholders etc etc) than tomcat so we see this error message because the gbean relationship
level is awry, whereas if tomcat is not so instrumented with
the filtermappings etc as gbeans then this error can't occur.

Jan

Greg Wilkins wrote:
Also might be an idea to check the tomcat deployer - because either it is suppressing a warning or it has the invoker servlet configured by default. neither are optimal
cheers



Reply via email to