Hey John,
For server-side the Transport Id is required on servlet level to initialize
the proper transport. It is also required when constructing factory beans
to select the transport to use. The reason is because there is no clear way
(at least right now) to get it from servlet. So to answer your question, yes,
sadly we have to have both set and they should match.
It would be great to have a single setting, however the transport has to
be initialized way before any kind of features / factory beans are. This is
the only reason to have both.
For the client-side, there are no changes, the transport doesn't need to be
modified, plain old HTTP.
Thanks.
Best Regards,
Andriy Redko
JDA> Hi,
JDA> So I've finally been able to confirm an issue.
JDA> When CXF's SSE libraries are on the classpath, if the transportId of the
JDA> servlet does not match the transport ID set with the SSE component, then no
JDA> services are discovered.
JDA> IMHO, there may be cases where the SSE libraries are present (client only)
JDA> and no server runtimes are there. In this case, the transport ID will not
JDA> match.
JDA> I'm curious, do both need to be set? What is the benefit/need on the
JDA> servlet layer needing the transport ID set when the underlying feature also
JDA> does it?
JDA> John
