Re: [PAX WEB] 10 ways (in one of several categories) to register a servlet

2020-02-03 Thread 'Achim Nierbeck' via OPS4J
Hi, remove as much as you can, which doesn't leave it crippled. As now we do have a good Whiteboard API by the osgi spec, we should try to stick to just that one, unless it's missing something. The internal APIs to register Servlets might still be needed, but should be ok to be stripped down to

Re: [PAX WEB] 10 ways (in one of several categories) to register a servlet

2020-02-03 Thread Jean-Baptiste Onofré
Hi, I think a cleanup is required. For Pax Web 8.x, I would simply go with removing the discussed items. Regards JB On 03/02/2020 11:54, Grzegorz Grzybek wrote: > Hello > > I'm reviewing the consistency, stability and user-friendliness of Pax > Web 8 and I tell myself that if now is not the

[PAX WEB] 10 ways (in one of several categories) to register a servlet

2020-02-03 Thread Grzegorz Grzybek
Hello I'm reviewing the consistency, stability and user-friendliness of Pax Web 8 and I tell myself that if now is not the good time to review the interfaces, then we'll never do it. So, `org.ops4j.pax.web.service.WebContainer` (extension of `org.osgi.service.http.HttpService`) allows a servlet