PaxWeb 7.2.29 - Jetty upgrade?

Hi, Is PaxWeb 7.2.x line is still maintained? Actual version 7.2.29 uses Jetty 9.4.43.v20210629 which has some vulnerabilities. Is it possible to release a new PaxWeb 7.2.x version with newer Jetty version (as I can see PaxWeb 7.3.6 uses Jetty 9.4.48.v20220622)? -- Best regards, Daniel Stoch

[PAX WEB] Does DefaultHttpContext allow access to all resources in the bundle?

Hi, In Wicket web framework if some request url has not a dedicated/registered handler in application then WicketServlet fallbacks processing to return a resource from ServletContext as a response content: InputStream stream = getServletContext().getResourceAsStream(url); String mimeType =

Re: [PAX WEB] Configure allowed http methods

; So you made me realize, that OPTIONS method may return TRACE on Pax Web 8 > for Jetty runtime. It should be fine on Tomcat and Undertow, but I've > created https://github.com/ops4j/org.ops4j.pax.web/issues/1664 to check > this. > > regards > Grzegorz Grzybek > > wt., 28

[PAX WEB] Configure allowed http methods

e it should be done directly in Jetty configuration using jetty.xml? -- Best regards, Daniel Stoch -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubs

Re: Cannot start pax-web-jetty-bundle - Package uses conflict: Import-Package: org.ops4j.pax.web.service

e. > > PS: Karaf simplify a lot the installation thanks to the features. > > Regards > JB > > On Fri, May 8, 2020 at 12:00 PM Daniel Stoch > wrote: > >> Hi, >> >> I have a strange error when trying to run a couple of bundles (using >> Equinox) incl

Cannot start pax-web-jetty-bundle - Package uses conflict: Import-Package: org.ops4j.pax.web.service

;7.2.10" org.osgi.framework.BundleException: The bundle "org.ops4j.pax.web.pax-web-spi_7.2.10 [20]" could not be resolved. Reason: Missing Constraint: Import-Package: org.ops4j.pax.web.service; version="7.2.10" How to solve this problem (what can be wron

Re: NullPointerException in JettyServerWrapper.configureSessionManager after upgrade to Pax-Web 7.2.3 (PAXWEB-1095)

Thank you, it was really fast :) -- Best regards, Daniel W dniu wtorek, 6 listopada 2018 09:10:20 UTC+1 użytkownik Grzegorz Grzybek napisał: > > Thanks - done! > > regards > Grzegorz Grzybek > > pon., 5 lis 2018 o 17:47 Daniel Stoch > > napisał(a): > >>

Re: NullPointerException in JettyServerWrapper.configureSessionManager after upgrade to Pax-Web 7.2.3 (PAXWEB-1095)

I've created ticket for this: PAXWEB-1186 <https://ops4j1.jira.com/browse/PAXWEB-1186> as we talked in other thread. -- Best regards, Daniel W dniu wtorek, 30 października 2018 13:54:37 UTC+1 użytkownik Daniel Stoch napisał: > > Hi, > > After upgrade from Pax-Web

Re: [PAX-WEB] Plan to release pax web 7.2.4 soon and idea for 7.3.x

> > Am Mo., 5. Nov. 2018 um 08:39 Uhr schrieb Grzegorz Grzybek < > gr.gr...@gmail.com >: > >> Thanks for reminding - checking. >> >> regards >> Grzegorz Grzybek >> >> pon., 5 lis 2018 o 08:32 Daniel Stoch &

Re: [PAX-WEB] Plan to release pax web 7.2.4 soon and idea for 7.3.x

Hi, What about a NullPointerException in JettyServerWrapper.configureSessionManager in 7.2.3 about which I wrote in an earlier message? Maybe I should create a JIRA ticket for this? -- Best regards, Daniel W dniu piątek, 2 listopada 2018 17:03:48 UTC+1 użytkownik Jean-Baptiste Onofré napisał:

NullPointerException in JettyServerWrapper.configureSessionManager after upgrade to Pax-Web 7.2.3 (PAXWEB-1095)

Hi, After upgrade from Pax-Web 4.4.1 to 7.2.3 I have a NullPointerException in JettyServerWrapper.configureSessionManager. I am using Servlet service registration. It looks like SessionIdManager is not initialized? In the previous versions of PaxWeb there was a lazy initialization of SessionId