A bit drastic to run without a context just to avoid the "NO JSP Support for ..." message.
It's easy enough to provide your own webdefault.xml that has no jsp servlet entry to avoid that message. Joakim Erdfelt / [email protected] On Wed, Sep 20, 2017 at 10:58 AM, Nils Kilden-Pedersen <[email protected]> wrote: > Not sure if this will be considered a bug or not. > > For a long time I've been using Jetty embedded without a Context > (primarily because I don't want the JSP warning), and using async servlets. > > A change in 9.4.7 broke this: > https://github.com/eclipse/jetty.project/commit/c9a1395f08a0 > 6a523ac6654d1781f8f007a09cf9#diff-354099300ebcffd0a26c128bcae98d77R2263 > > Without a context, the contextPath is null, and calling startAsync thus > fails. > > Bug, or am I making invalid assumptions? > > > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
