[jetty-dev] [jira] (JETTY-1503) Jetty 8.1.2 scans all classes on classpath if there is >= 1xServletContainerInitializer with HandlesTypes on the classpath, regardless of metadata-complete="true"

Jan Bartel
commented on JETTY-1503

Jetty 8.1.2 scans all classes on classpath if there is >= 1xServletContainerInitializer with HandlesTypes on the classpath, regardless of metadata-complete="true"

The official word from the servlet spec group is that ServletContainerInitializers are independent of metadata-complete:

http://java.net/jira/browse/SERVLET_SPEC-36

Therefore, scanning has to proceed if any ServletContainerInitializers are found that have a @HandlesTypes annotation. Luckily, the JSP container's ServletContainerInitializer does not have a HandlesTypes annotation, so that won't cause jetty to scan all classes.

If you're not using Spring's ServletContainerInitializer, then use jetty's "org.eclipse.jetty.server.webapp.WebInfIncludeJarPattern" as previously posted to enumerate only those jars in your WEB-INF/lib that you would like examined (ie exclude the particular spring jar - note this will also exclude it from consideration for META-INF/web-fragment.xml, META-INF/resources etc too).

Jan

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators .

For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email