We have actually split up the wildfly code base recently, and the result of this is that
we now have 3 different Wildfly artifacts:
- Wildfly Core: The core platform (classloading, management etc)
- Wildfly Web: Core + Undertow
- Wildfly Full: everything else
It sounds like you want Wildfly Web, which is basically just a Servlet container, with our
modular class loading and management.
You can get it from maven central:
http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22wildfly-web-dist%22
We have not really talked about / promoted this much yet, I should be writing more about
it over the coming months.
Stuart
----- Original Message -----
From: "Robert Nikander" <rob.nikander(a)gmail.com>
To: undertow-dev(a)lists.jboss.org
Sent: Sunday, 23 November, 2014 1:03:31 AM
Subject: [undertow-dev] Undertow + modules = Wildfly?
Hi,
I’m looking for a minimal webapp server, like Undertow, but I also want JBoss
modules (or something with that kind of classloading). Any thoughts on the
differences between…
1. Using Wildfly and learning to turn stuff off. I don’t care about most of
J2EE.
2. Using only Undertow + the jars for JBoss modules.
Specifically, I’m wondering if there will be much difference in RAM usage,
and whether I could still write native Undertow handlers [1] if I go with
#1.
Rob
[1]
http://undertow.io/documentation/core/undertow-handler-guide.html
_______________________________________________
undertow-dev mailing list
undertow-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/undertow-dev