Hi Carlos, Yes, sure, the systests/rs-sse holds a test suite for SSE and different application containers.
https://github.com/apache/cxf/tree/master/systests/rs-sse/rs-sse-jetty/src/test/java/org/apache/cxf/systest/jaxrs/sse/jetty https://github.com/apache/cxf/tree/master/systests/rs-sse/rs-sse-tomcat/src/test/java/org/apache/cxf/systest/jaxrs/sse/tomcat https://github.com/apache/cxf/tree/master/systests/rs-sse/rs-sse-undertow/src/test/java/org/apache/cxf/systest/jaxrs/sse/undertow What you may have run to is the suble but important detail: the transport id should be set on servlet and factory bean levels, and it should much (this is is what you are missing probably, it is usually not needed in most cases). The Wiki page I referred to explains that (with upcoming 3.2.3 this should be simplified and would need only factory bean to have transport set). We also have a few sample projects: https://github.com/apache/cxf/tree/master/distribution/src/main/release/samples/jax_rs/sse_spring https://github.com/apache/cxf/tree/master/distribution/src/main/release/samples/jax_rs/sse_tomcat We have had the discussion recently on dev@ list about not relying on Atm for SSE implementation, that would make things much more simple and straigthforward. If you could submit the PR with your async implementation (even as a draft), the team could review it and validate the idea. Thanks. Best Regards, Andriy Redko CSA> Hi Andriy, CSA> could you point me to the tests that are started with the special CSA> transport id? Just to see where we are doing something wrong, because in CSA> our case changing the transport id breaks most of the regular endpoints. CSA> In the meantime we have put together an impl that does not rely on CSA> atmosphere, just uses asyncContext, and does not need any special CSA> transport. Would you think this could be an interesting contribution or CSA> is atmosphere needed for some reason? CSA> It could also use a review by someone with CXF super knowledge. CSA> Bests. CSA> Carlos. CSA> El 12/3/18 a las 16:09, Andrey Redko escribió: >> Hi Carlos, >> That's right, SSE in CXF requires dedicated transport, however it is fully >> compatible with the existing HTTP transport (regular endpoints). Both SSE >> and non-SSE endpoints should work just fine. Here is a link to the wiki, >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75974373, >> which will be a part of the official documentation section shortly. >> Thanks. >> Best Regards, >> Andriy Redko >> On Mon, Mar 12, 2018, 8:25 AM Carlos Sierra Andrés <[email protected]> >> wrote: >>> Hi there, >>> as you might already know we are implementing Aries JAX-RS OSGi spec on >>> top of CXF. We have found a problem when trying to add SSE support, >>> because it looks like it needs to use a special "transport id", so it >>> can't be used to have both regular SSE endpoints and regular endpoints >>> in the same application. Is this correct or are we doing something wrong? >>> Bests. >>> Carlos.
