Som,
Neither WebAppContext nor ServletHandlerContext are obsolete.
However, you only need to call setConfigurations in exceptional
circumstances as typically it is sufficient just to put a jar on the class
path for any Configuration instance that it contains to be discovered and
added to your
The use of both the WebAppContext class and ServletHandlerContext class
have become obsolete in jetty 11 so the recommendation to use classlist
instead of WebAppContext.setConfigurations wasn't relevant.
On Fri, 26 Mar 2021, 23:40 Joakim Erdfelt, wrote:
> What version of Jetty are you
FYI ,
The DefaultServlet is an object argument passed to
ServetHandlerContext class.
The main class which came with the heroku archetype uses WebAppContext
Class.
On Thu, 25 Mar 2021, 21:28 Jan Bartel, wrote:
>
> You're using a servlet to serve a welcome file instead of serving a static
>
In jetty 11 such features are auto configuring. You just need to add the
jar to the classpath and the feature will be discovered and added to the
webapp.
So just put jetty-annotation jar on the
classpath
On Sat, 3 Apr 2021, 06:32 Som Lima, wrote:
> Hi,
>
> I am looking for code showing how to
Hi,
I am looking for code showing how to configure embedded jetty to add
features like annotations jsf etc.
to the WebAppContext class in particular rather than adding features using
the ServletHandlerContext.
for jetty version 11.
___
jetty-users
Som,
we are not responsible for the Heroku archetypes, but that main class looks
reasonable.
With jetty-11, all that is necessary to enable JSPs is to put the jetty-jsp
jar on the classpath and it will be discovered and available to the webapp.
On Fri, 2 Apr 2021 at 13:08, Som Lima wrote:
>
