On 25/04/2010 10:53, Pid wrote: > On 24/04/2010 00:07, Mark Thomas wrote: >> On 23/04/2010 16:51, Pid wrote: >>> Are ServletContainerInitializer implementations also discovered from the >>> common classloader automatically? >> >> They should be, providing the JAR isn't listed as one of the JARs to >> skip for annotations. But I haven't tested it... > > I'm not getting an SCI onStartup method to fire at all at the moment, in > a WEB-INF/lib/sci-test.jar, in WEB-INF/classes, or in the common > classloader.
Just tried a clean TC7 build. Looks like I've managed to break this. Looking at a fix now... >> I'd need to check the spec but AFAICR the spec says they only *have* to >> be found in the web app. > > I'd formed the impression that the intention is/was that they could be > found in the entire classloader tree, from the reference to the > discovery mechanism being semantically equivalent to the jar services > mechanism and the suggestion that a JSP container could be implemented > this way. I'm finding Servlet 3.0 a little opaque in parts. Having re-read section 8.2, the implication is that they should be found in the entire tree. The default configuration should do this. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
