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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [jetty-users] How to prevent No Spring WebApplicationInitializer types detected on classpath?

From: Rossen Stoyanchev <rstoyanchev@xxxxxxxxxxxxx>
Date: Wed, 2 Oct 2013 16:20:56 -0400
Delivered-to: jetty-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jetty-users>
List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>

Hi Miguel,

You can check section 8.2.4 of the Servlet spec that describes the
ability for frameworks to provide web fragments. I believe it is
applied irrespective of metadata-complete and it catches out a lot of
people.

I think simply adding an <absolute-ordering/> element to your web.xml
should prevent it. See section 8.2.2 for details.

Regards,
Rossen

References:
- [jetty-users] How to prevent No Spring WebApplicationInitializer types detected on classpath?
  - From: Miguel Almeida
- Re: [jetty-users] How to prevent No Spring WebApplicationInitializer types detected on classpath?
  - From: Rossen Stoyanchev
- Re: [jetty-users] How to prevent No Spring WebApplicationInitializer types detected on classpath?
  - From: Miguel Almeida

Prev by Date: Re: [jetty-users] maven-jetty-plugin - how to add directory to container classpath
Next by Date: Re: [jetty-users] How to prevent No Spring WebApplicationInitializer types detected on classpath?
Previous by thread: Re: [jetty-users] How to prevent No Spring WebApplicationInitializer types detected on classpath?
Next by thread: Re: [jetty-users] How to prevent No Spring WebApplicationInitializer types detected on classpath?
Index(es):
- Date
- Thread

Breadcrumbs