Nils, never mind... I remembered: https://github.com/eclipse/jetty.project/issues/1833
cheers On 21 September 2017 at 07:46, Greg Wilkins <[email protected]> wrote: > Nils, > > it is indeed the correct solution for the "No JSP" warning to use a > ServletContextHandler rather than the full WebAppContext. > > However it is also a bug that we require a context, and we do make effort > in other parts of the code to handle no context. So we will fix this.... > if you open an issue for it, that will help remind us to do so. > > cheers > > > On 21 September 2017 at 06:22, Nils Kilden-Pedersen <[email protected]> > wrote: > >> Seems I’m able to get this working by using a ServletContextHandler >> instead of ServletHandler, which I’m currently using, and also instead >> of going full web-app using WebAppContextHandler. >> >> >> On Wed, Sep 20, 2017 at 2:51 PM, Nils Kilden-Pedersen <[email protected]> >> wrote: >> >>> That was a recommendation given on this list, but I may have interpreted >>> it wrong: >>> >>> https://dev.eclipse.org/mhonarc/lists/jetty-users/msg07148.html >>> >>> Is there a way to do what you suggested programmatically? >>> >>> >>> On Wed, Sep 20, 2017 at 2:42 PM, Joakim Erdfelt <[email protected]> >>> wrote: >>> >>>> 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-354099300ebcffd0a26c128bca >>>>> e98d77R2263 >>>>> >>>>> 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 >>>> >>> >>> >> >> _______________________________________________ >> 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 >> > > > > -- > Greg Wilkins <[email protected]> CTO http://webtide.com > -- Greg Wilkins <[email protected]> CTO http://webtide.com
_______________________________________________ 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
