Re: [jetty-users] How to prevent No Spring WebApplicationInitializer typ

[Miguel Almeida <migueldealmeida@xxxxxxxxx>]

Thanks for the quick reply Rossen,

On Wed, Oct 2, 2013 at 5:40 PM, Rossen Stoyanchev <rstoyanchev@xxxxxxxxxxxxx> wrote:

You must be pulling in spring-web as a dependency. That's not required
for dependency injection so you might want to check what's pulling it
in.

Indeed. struts2-spring-plugin is using spring-web. Also, jmesa 3.0.4 is also using it (this one seems kind of odd).

So I guess I need to go down the other way, but to be honest I do not quite understand what I am supposed to be doing.

This is what I understood so far:
1) The goal of  metadata-complete=true is to tell the container that it doesn't need to scan the lib/ folder for any Servlet 3.0 specific annotations

2) This is desired, because I am not using any

3) The presence of spring-web somehow forces Jetty to scan the entire /lib nonetheless (searching for ServletContainerInitializers?)

4) By adding an empty <absolute-ordering/>, we are essentially saying no ServletContainerInitializers are to be searched

5) This is what I need in this case, because this is a Struts application.

I am sure to have said something wrong, but my limited knowledge of ServletContainerInitializers and whatnot is probably hindering these assumptions. Could you care to shed some light?

Once again, thanks for the help!

Miguel

That said there is a way to include/exclude specific web fragments
through <absolute-ordering> in web.xml. It is a Servlet spec specific
mechanism but also see this commit message:
https://github.com/spring-projects/spring-framework/commit/d309bb4bbbf41cac2c59808e0addebcaee5b9e29

Rossen
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users