On 02/07/2020 14:14, Vitor Medina Cruz wrote: > On Wed, Jul 1, 2020 at 6:48 PM Mark Thomas <ma...@apache.org> wrote:
<snip/> >> @WebFiler, @WebListener and @WebServlet are deployment annotations so >> scanning for these is controlled by the JarScanner. >> >> If an SCI has an @HandlesTypes annotation then all JARs that are >> potential SCI sources will be scanned for matches. To put it another >> way, the JarScanner configuration does NOT control the search for >> @HandlesTypes matches. Any JAR eligible to provide an SCI will be >> scanned for @HandlesTypes. Those JARs are controlled by <absolute-ordering> >> > > Ok, and if a jar doesn't provide a web-fragment name? In this old post( > http://tomcat.10.x6.nabble.com/Why-does-absolute-ordering-in-web-xml-without-others-kill-classpath-scanning-td5029985.html) > it is said : > > "Tomcat will give these a name equal to the name of the JAR file so you can > use it in ordering. That is a Tomcat specific feature." > > This is/holds true? I tried with no success It should do. So for foobar-0.3.jar the name should be "foobar-0.3.jar" Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
