jungm commented on PR #2945:
URL: https://github.com/apache/tomee/pull/2945#issuecomment-5847257644

   Finished the removal, `openejb-http` is gone now:
   
   - Merged `main` (conflicts in the example poms from TOMEE-3234).
   - `openejb-http` deleted: the servlet bridge moved to `openejb-server`, the 
Tomcat-only classes to `tomee-catalina`; `HttpSession`, `ServletSessionAdapter` 
and `BasicAuthHttpListenerWrapper` were dead and are removed.
   - `WsService` registers `PortAddressRegistry` before checking for a 
`WsRegistry`, so `@WebServiceRef` clients work outside TomEE again. Both 
services check their registry once in `start()`, the other null checks are gone.
   - ApplicationComposer: `@EnableServices(jaxrs/jaxws)`, the jaxrs/jaxws 
service aliases and `@JaxrsProviders` handling removed, `@RandomPort("http")` 
fails fast. `applicationcomposer-maven-plugin` ships `openejb-ejbd` instead of 
`openejb-cxf-rs`.
   - Leftovers removed: `SWClassLoader.getWebResource`, the itests `http` mode, 
CXF deps of the cdi-embedded TCK, stale docs; the JAX-RS tests use 
`ArquillianUtil` for the embedded check.
   - Jetty dependency management dropped, it only existed for the 
`openejb-http` Jetty backend.
   
   Verified: `clean install -DskipTests -Pstyle,rat`; tests of openejb-core 
(4118), openejb-junit5, the server modules, 
tomee-catalina/jaxrs/webservices/embedded, the OpenEJB Arquillian adapter; 
Arquillian on TomEE embedded: JAX-RS 169, JAX-WS 32, web profile 159, all 
green. tomee-remote suites not run.
   
   Not covered: the cdi-embedded TCK doesn't start on this branch with or 
without these changes (HtmlUnit's xalan misses its serializer, then a cdi-tck 
api/impl mismatch). The standalone assembly's NOTICE still lists libraries it 
no longer bundles (CXF and older ones), separate cleanup.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to