THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Table of Contents |
|---|
Introduction
The JAX-RS 2.1 introduced the support of server-sent events (SSE).
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:cxf="http://cxf.apache.org/blueprint/core"
xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs"
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://cxf.apache.org/blueprint/core http://cxf.apache.org/schemas/blueprint/core.xsd
http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/blueprint/jaxrs.xsd">
<bean id="sseFeature" class="org.apache.cxf.jaxrs.sse.SseFeature" />
<cxf:bus>
<cxf:features>
<cxf:logging />
</cxf:features>
</cxf:bus>
<jaxrs:server id="sseSampleService" address="/">
<jaxrs:serviceBeans>
<ref component-id="..." />
</jaxrs:serviceBeans>
<jaxrs:providers>
<ref component-id="..." />
</jaxrs:providers>
<jaxrs:features>
<ref component-id="sseFeature" />
</jaxrs:features>
</jaxrs:server>
</blueprint> |
...
Before 3.2.5 release
Although SSE in general works on top of HTTP transport, the SSE implementation in CXF uses the dedicated one, based on Atmosphere framework. This transport only required on the server-side (client side works over normal HTTP) and is fully compatible with HTTP transport.
...