cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <>
Subject Re: Handling the case where CXF Servlet doesn't match expected transport ID
Date Sun, 25 Feb 2018 04:10:14 GMT
Here's a reproducer app, if anyone else is curious.

If you comment out
you'll see the issue, but deploying this as is to tomcat will work just

On Sat, Feb 24, 2018 at 10:59 PM John D. Ament <>

> Hi,
> So I've finally been able to confirm an issue.
> When CXF's SSE libraries are on the classpath, if the transportId of the
> servlet does not match the transport ID set with the SSE component, then no
> services are discovered.
> IMHO, there may be cases where the SSE libraries are present (client only)
> and no server runtimes are there.  In this case, the transport ID will not
> match.
> I'm curious, do both need to be set?  What is the benefit/need on the
> servlet layer needing the transport ID set when the underlying feature also
> does it?
> John

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message