Re: JAX-RPC and Tomcat 10

On 21/07/2020 14:44, Romain Manni-Bucau wrote: > Yes, was thinking to tomee in particular since it does not use tomcat as > a lib but really as the container so if the container fails then it can > become hard if not "disabl-able" somehow (at least with subclassing or > something programmatic). I

Re: JAX-RPC and Tomcat 10

Yes, was thinking to tomee in particular since it does not use tomcat as a lib but really as the container so if the container fails then it can become hard if not "disabl-able" somehow (at least with subclassing or something programmatic). Romain Manni-Bucau @rmannibucau

Re: JAX-RPC and Tomcat 10

On 21/07/2020 14:26, Romain Manni-Bucau wrote: > Hi Mark, > > e) c as default + add a toggle to behave as a? (thinking to container > extending tomcat where this shouldn't fail probably) So keep the attributes in ContextService and friends that record the JAX-RPC so they are accessible to downstr

Re: JAX-RPC and Tomcat 10

Hi Mark, e) c as default + add a toggle to behave as a? (thinking to container extending tomcat where this shouldn't fail probably) Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

JAX-RPC and Tomcat 10

All, JAX-RPC has been removed in Jakarta EE 9. Implementations are free to continue supporting it if they wish. My preference would be to remove JAX-RPS support in Tomcat 10. I am working on this at the moment and am wondering how to handle the JAX-RPC elements we can't entirely remove. There