Camel Spring Boot Starter for websocket-jsr356

Spring Boot Auto-Configuration

When using websocket-jsr356 with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:

  <!-- use the same version as your Camel core version -->

The component supports 5 options, which are listed below.

Name Description Default Type


Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.




Whether to enable auto configuration of the websocket-jsr356 component. This is enabled by default.



Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.




To enable customization of how a WebSocket ServerEndpoint is configured and deployed. By default DefaultServerEndpointDeploymentStrategy is used. The option is a org.apache.camel.websocket.jsr356.ServerEndpointDeploymentStrategy type.



Deprecated Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities