Re: State of Pax Web 8

[JB Onofré]

I second Matt and Serge. 

As discussed together yesterday it’s really great work ! Thanks !

Regards
JB

> Le 27 juil. 2021 à 14:07, Matt Pavlovich  a écrit :
> 
> Great work!  Thank you for all the effort you’ve put forth
> 
> On Jul 27, 2021, at 1:00 AM, Grzegorz Grzybek  wrote:
> 
> 
> Hello
> 
> I'd just like to let you know that everything is under control and I didn't 
> abandon the effort.
> 
> I've added a todo.txt file[1] to Pax Web's main branch (I didn't create 
> separate GH issues for the tasks yet, as the scope may change, but at some 
> point I'll translate the remaining items to GH issues).
> 
> So currently (and for some time already) I'm patiently making existing (Pax 
> Web 7) integration tests work with Pax Web 8.
> 
> The remaining integration tests cover (~10 tests):
> - HttpContext processing[2] (that's beyond CMPN specifications)
> - Whiteboard websockets (beyond CMPN specifications)
> - DTO tests
> - JAX-RS tests
> - Jetty/Tomcat/Undertow bundles tests
> - Jetty Handlers/Connectors OSGi services
> - VirtualHosts
> - CRLs
> - Jasypt
> 
> The already working (much faster due to better listeners!) tests include 
> (almost 200 per container runtime):
> - external jetty.xml/tomcat-server.xml/undertow.xml configuration
> - HttpService/WebContainer tests (CMPN chapter 102)
> - JSP tests (custom tags, directives, includes, ...)
> - WABs (including SCIs, WebSockets, scanning and fragments)
> - JSF
> - Vaadin (new!)
> - Whiteboard (much improved, including SCR and standard services)
> 
> The most important aspects of chapters 102 (Http Service), 128 (Web 
> Applications) and 140 (Whiteboard) are implemented including the most 
> important one - 1:N mapping between web elements and _contexts_.
> 
> The other most important aspect, not related to CMPN specifications is the 
> consistency of behavior between Jetty, Tomcat and Undertow containers - only 
> ONE integration test has container specific behavior - the test checking HTTP 
> response when POST size (container-specific configuration) is exceeded.
> 
> I roughly plan to release Pax Web 8 around mid of September.
> 
> kind regards
> Grzegorz Grzybek
> ===
> [1]: https://github.com/ops4j/org.ops4j.pax.web/blob/main/todo.txt
> [2]: 
> https://ops4j1.jira.com/wiki/spaces/paxweb/pages/354025473/HTTP+Context+processing
> 
> --
> --
> --
> OPS4J - http://www.ops4j.org - op...@googlegroups.com
> 
> ---
> You received this message because you are subscribed to the Google Groups 
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to 
> ops4j+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ops4j/CAAdXmhpg%3Dn_LizOosNYnt43MZh_01CNU%2BZ0zfPFF4a9JaaQOvQ%40mail.gmail.com.

Re: State of Pax Web 8

[Matt Pavlovich]

Great work!  Thank you for all the effort you’ve put forth

On Jul 27, 2021, at 1:00 AM, Grzegorz Grzybek  wrote:


Hello

I'd just like to let you know that everything is under control and I didn't 
abandon the effort.

I've added a todo.txt file[1] to Pax Web's main branch (I didn't create 
separate GH issues for the tasks yet, as the scope may change, but at some 
point I'll translate the remaining items to GH issues).

So currently (and for some time already) I'm patiently making existing (Pax Web 
7) integration tests work with Pax Web 8.

The remaining integration tests cover (~10 tests):
 - HttpContext processing[2] (that's beyond CMPN specifications)
 - Whiteboard websockets (beyond CMPN specifications)
 - DTO tests
 - JAX-RS tests
 - Jetty/Tomcat/Undertow bundles tests
 - Jetty Handlers/Connectors OSGi services
 - VirtualHosts
 - CRLs
 - Jasypt

The already working (much faster due to better listeners!) tests include 
(almost 200 per container runtime):
 - external jetty.xml/tomcat-server.xml/undertow.xml configuration
 - HttpService/WebContainer tests (CMPN chapter 102)
 - JSP tests (custom tags, directives, includes, ...)
 - WABs (including SCIs, WebSockets, scanning and fragments)
 - JSF
 - Vaadin (new!)
 - Whiteboard (much improved, including SCR and standard services)

The most important aspects of chapters 102 (Http Service), 128 (Web 
Applications) and 140 (Whiteboard) are implemented including the most important 
one - 1:N mapping between web elements and _contexts_.

The other most important aspect, not related to CMPN specifications is the 
consistency of behavior between Jetty, Tomcat and Undertow containers - only 
ONE integration test has container specific behavior - the test checking HTTP 
response when POST size (container-specific configuration) is exceeded.

I roughly plan to release Pax Web 8 around mid of September.

kind regards
Grzegorz Grzybek
===
[1]: https://github.com/ops4j/org.ops4j.pax.web/blob/main/todo.txt
[2]: 
https://ops4j1.jira.com/wiki/spaces/paxweb/pages/354025473/HTTP+Context+processing

--
--
--
OPS4J - http://www.ops4j.org - op...@googlegroups.com

---
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
ops4j+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ops4j/CAAdXmhpg%3Dn_LizOosNYnt43MZh_01CNU%2BZ0zfPFF4a9JaaQOvQ%40mail.gmail.com.

Re: State of Pax Web 8

[Serge Huber]

Thank you so much for all this work, I cannot tell you enough how much it
is appreciated!

I've programmed my share of web containers in the past and I know how
tricky this can be to get right.

Regards,
  Serge...

Serge Huber
CTO & Co-Founder
T +41 22 361 3424
9 route des Jeunes | 1227 Acacias | Switzerland
jahia.com 
SKYPE | LINKEDIN  | TWITTER
 | VCARD



> JOIN OUR COMMUNITY  to evaluate, get trained and
to discover why Jahia is a leading User Experience Platform (UXP) for
Digital Transformation.


On Tue, Jul 27, 2021 at 8:09 AM  wrote:

> This is very nice and thank you very much Grzegorz for all your great
> work on Pax Web!
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 27/07/2021 à 08:00, Grzegorz Grzybek a écrit :
> > Hello
> >
> > I'd just like to let you know that everything is under control and I
> didn't
> > abandon the effort.
> >
> > I've added a todo.txt file[1] to Pax Web's main branch (I didn't create
> > separate GH issues for the tasks yet, as the scope may change, but at
> some
> > point I'll translate the remaining items to GH issues).
> >
> > So currently (and for some time already) I'm patiently making existing
> (Pax
> > Web 7) integration tests work with Pax Web 8.
> >
> > The remaining integration tests cover (~10 tests):
> >  - HttpContext processing[2] (that's beyond CMPN specifications)
> >  - Whiteboard websockets (beyond CMPN specifications)
> >  - DTO tests
> >  - JAX-RS tests
> >  - Jetty/Tomcat/Undertow bundles tests
> >  - Jetty Handlers/Connectors OSGi services
> >  - VirtualHosts
> >  - CRLs
> >  - Jasypt
> >
> > The already working (much faster due to better listeners!) tests include
> > (almost 200 per container runtime):
> >  - external jetty.xml/tomcat-server.xml/undertow.xml configuration
> >  - HttpService/WebContainer tests (CMPN chapter 102)
> >  - JSP tests (custom tags, directives, includes, ...)
> >  - WABs (including SCIs, WebSockets, scanning and fragments)
> >  - JSF
> >  - Vaadin (new!)
> >  - Whiteboard (much improved, including SCR and standard services)
> >
> > The most important aspects of chapters 102 (Http Service), 128 (Web
> > Applications) and 140 (Whiteboard) are implemented including the most
> > important one - 1:N mapping between web elements and _contexts_.
> >
> > The other most important aspect, not related to CMPN specifications is
> the
> > consistency of behavior between Jetty, Tomcat and Undertow containers -
> > only ONE integration test has container specific behavior - the test
> > checking HTTP response when POST size (container-specific configuration)
> is
> > exceeded.
> >
> > I roughly plan to release Pax Web 8 around mid of September.
> >
> > kind regards
> > Grzegorz Grzybek
> > ===
> > [1]: https://github.com/ops4j/org.ops4j.pax.web/blob/main/todo.txt
> > [2]:
> >
> https://ops4j1.jira.com/wiki/spaces/paxweb/pages/354025473/HTTP+Context+processing
> >
>

Re: State of Pax Web 8

[fpapon]

This is very nice and thank you very much Grzegorz for all your great
work on Pax Web!

regards,

François
fpa...@apache.org

Le 27/07/2021 à 08:00, Grzegorz Grzybek a écrit :
> Hello
>
> I'd just like to let you know that everything is under control and I didn't
> abandon the effort.
>
> I've added a todo.txt file[1] to Pax Web's main branch (I didn't create
> separate GH issues for the tasks yet, as the scope may change, but at some
> point I'll translate the remaining items to GH issues).
>
> So currently (and for some time already) I'm patiently making existing (Pax
> Web 7) integration tests work with Pax Web 8.
>
> The remaining integration tests cover (~10 tests):
>  - HttpContext processing[2] (that's beyond CMPN specifications)
>  - Whiteboard websockets (beyond CMPN specifications)
>  - DTO tests
>  - JAX-RS tests
>  - Jetty/Tomcat/Undertow bundles tests
>  - Jetty Handlers/Connectors OSGi services
>  - VirtualHosts
>  - CRLs
>  - Jasypt
>
> The already working (much faster due to better listeners!) tests include
> (almost 200 per container runtime):
>  - external jetty.xml/tomcat-server.xml/undertow.xml configuration
>  - HttpService/WebContainer tests (CMPN chapter 102)
>  - JSP tests (custom tags, directives, includes, ...)
>  - WABs (including SCIs, WebSockets, scanning and fragments)
>  - JSF
>  - Vaadin (new!)
>  - Whiteboard (much improved, including SCR and standard services)
>
> The most important aspects of chapters 102 (Http Service), 128 (Web
> Applications) and 140 (Whiteboard) are implemented including the most
> important one - 1:N mapping between web elements and _contexts_.
>
> The other most important aspect, not related to CMPN specifications is the
> consistency of behavior between Jetty, Tomcat and Undertow containers -
> only ONE integration test has container specific behavior - the test
> checking HTTP response when POST size (container-specific configuration) is
> exceeded.
>
> I roughly plan to release Pax Web 8 around mid of September.
>
> kind regards
> Grzegorz Grzybek
> ===
> [1]: https://github.com/ops4j/org.ops4j.pax.web/blob/main/todo.txt
> [2]:
> https://ops4j1.jira.com/wiki/spaces/paxweb/pages/354025473/HTTP+Context+processing
>

State of Pax Web 8

[Grzegorz Grzybek]

Hello

I'd just like to let you know that everything is under control and I didn't
abandon the effort.

I've added a todo.txt file[1] to Pax Web's main branch (I didn't create
separate GH issues for the tasks yet, as the scope may change, but at some
point I'll translate the remaining items to GH issues).

So currently (and for some time already) I'm patiently making existing (Pax
Web 7) integration tests work with Pax Web 8.

The remaining integration tests cover (~10 tests):
 - HttpContext processing[2] (that's beyond CMPN specifications)
 - Whiteboard websockets (beyond CMPN specifications)
 - DTO tests
 - JAX-RS tests
 - Jetty/Tomcat/Undertow bundles tests
 - Jetty Handlers/Connectors OSGi services
 - VirtualHosts
 - CRLs
 - Jasypt

The already working (much faster due to better listeners!) tests include
(almost 200 per container runtime):
 - external jetty.xml/tomcat-server.xml/undertow.xml configuration
 - HttpService/WebContainer tests (CMPN chapter 102)
 - JSP tests (custom tags, directives, includes, ...)
 - WABs (including SCIs, WebSockets, scanning and fragments)
 - JSF
 - Vaadin (new!)
 - Whiteboard (much improved, including SCR and standard services)

The most important aspects of chapters 102 (Http Service), 128 (Web
Applications) and 140 (Whiteboard) are implemented including the most
important one - 1:N mapping between web elements and _contexts_.

The other most important aspect, not related to CMPN specifications is the
consistency of behavior between Jetty, Tomcat and Undertow containers -
only ONE integration test has container specific behavior - the test
checking HTTP response when POST size (container-specific configuration) is
exceeded.

I roughly plan to release Pax Web 8 around mid of September.

kind regards
Grzegorz Grzybek
===
[1]: https://github.com/ops4j/org.ops4j.pax.web/blob/main/todo.txt
[2]:
https://ops4j1.jira.com/wiki/spaces/paxweb/pages/354025473/HTTP+Context+processing