Re: PAXWEB 8.0.9 Jetty - Correct way to override default context

2022-09-18 Thread dave....@candata.com
My other question would be if you are "Unregistering " the default context should it still show up in the HttpServiceRuntime.getRuntimeDTO().servletContextDTOs ? It does now Dave On Sunday, September 18, 2022 at 8:43:33 AM UTC-5 dave@candata.com wrote: > It will be a little tricky to

Re: PAXWEB 8.0.9 Jetty - Correct way to override default context

2022-09-18 Thread Dave Smith
It will be a little tricky to send my whole project in , let me see what I can do , however I have reviewed the test cases in the link provided and it looks like you are not covering my case ... I do not see a test where ... Register the default handler -> HttpContext defaultContext = wc.

Re: PAXWEB 8.0.9 Jetty - Correct way to override default context

2022-09-18 Thread Grzegorz Grzybek
Hello Actually, the initial reason of entire Pax Web 8 refactoring was the context handling - ability to register one servlet into multiple contexts and multiple servlets into one context. There are really lot of integration tests that show exactly this. I'd have to see your example and check

PAXWEB 8.0.9 Jetty - Correct way to override default context

2022-09-18 Thread Dave Smith
What is the correct way to override the default servlet context? I am doing this... @Component(service = ServletContextHelper.class,property = { Constants.SERVICE_RANKING+":Integer="+Integer.MAX_VALUE}) @HttpWhiteboardContext(name = "default",path = "/") public class NoSecurityContextImpl extends