Jetty also makes it very easy to scan jar for @WebServlet, @WebFilter,
@WebListener via AnnotationConfiguration.
http://www.eclipse.org/jetty/documentation/9.4.x/configuring-webapps.html
On Wed, Oct 4, 2017 at 12:53 AM, Brian Toal <brian.t...@gmail.com> wrote:
> The chain
The chain [1] left of with:
"The relevant language is in section 8.2.1
If a framework wants its META-INF/web-fragment.xml honored in such a way
that it augments a web application's web.xml, the framework must be bundled
within the web application's WEB-INF/lib directory
Therefore, Tomcat 8.0
In my embedded tomcat app, StandardJarScanner is doing a minimal Servlet
3.0 annotation scanning, specifically only HandlesTypes. After digging in,
it appears that because the classloader that loaded StandardJarScanner is
the same that loaded StandardContext and ContextConfig
I want to decouple my solution from web.xml completely, so the goal is to
have the container to scan all jars on the classpath and look for Servlet
3.0 annotations and do the necessary (register servlet context listeners,
filters, servlets, etc). In the code below, the container starts, but none
apsule-maven-plugin
> ${capsule.maven.plugin.version}
>
>
>
> build
>
>
> your.main.class.here
> fat
>
>
>
>
>
> And then the actual
Can someone point me to a example of how to run Tomcat as a embedded
application, packaged in a uber jar? I'm not interested in running via a
war. I've struggled to find a example.
