lazzexus/Kafkatorio
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

mucking about trying to get camel-kafka-connect websockets working

Browse source
This commit is contained in:
Adam 2021-12-26 22:55:06 +01:00
parent 83c991842f
commit abada0bf4b
14 changed files with 122 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

12
modules/infra-kafka-connect/src/main/resources/configs/websocket-sink-lua-topics.json5
View file

@ -14,7 +14,7 @@
// mandatory properties (for a complete properties list see the connector documentation):
// The URI to use such as http://hostname:port/path
"camel.sink.path.httpUri": "http://localhost:8095/ws",
"camel.sink.path.httpUri": "localhost:8095/ws",
// If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back.
// camel.sink.endpoint.bridgeEndpoint=
// The initial in-memory buffer size used when transferring data between Camel and AHC Client.
@ -29,8 +29,16 @@
// camel.sink.endpoint.connectionClose=
// Configure a cookie handler to maintain a HTTP session
// camel.sink.endpoint.cookieHandler=
// 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.
// 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.
// camel.sink.endpoint.lazyStartProducer=
// To enable streaming to send data as multiple text fragments.
// camel.sink.endpoint.useStreaming=
// To use a custom AhcBinding which allows to control how to bind between AHC and Camel.