[
https://issues.apache.org/jira/browse/TOMEE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222038#comment-13222038
]
David Blevins commented on TOMEE-144:
-------------------------------------
ContextConfig line 1821
protected void processAnnotationsUrl(URL url, WebXml fragment) {
if (url == null) {
// Nothing to do.
return;
} else if ("jar".equals(url.getProtocol())) {
processAnnotationsJar(url, fragment);
} else if ("jndi".equals(url.getProtocol())) {
processAnnotationsJndi(url, fragment);
} else if ("file".equals(url.getProtocol())) {
try {
processAnnotationsFile(new File(url.toURI()), fragment);
} catch (URISyntaxException e) {
log.error(sm.getString("contextConfig.fileUrl", url), e);
}
} else {
log.error(sm.getString("contextConfig.unknownUrlProtocol",
url.getProtocol(), url));
}
}
First need a larger webapp to test with. Something with no descriptors, say 5
or more jars, some classes and roughly 10 or 20 MB in size. All the jars
should have made-up names so as to not be excluded via the default excludes.
> Eliminate servlet-specific double scan
> --------------------------------------
>
> Key: TOMEE-144
> URL: https://issues.apache.org/jira/browse/TOMEE-144
> Project: TomEE
> Issue Type: Improvement
> Reporter: David Blevins
> Assignee: David Blevins
> Fix For: 1.0.0-beta-3
>
>
> Lack of cooperation at a code level causes the classpath to be scanned extra
> time while processing @WebServlet, @WebFilter and similar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
