camel-cxfrs-kafka-connector sink configuration

To lookup an existing configured CxfRsEndpoint. Must used bean: as prefix.

The service publish address.

Set the feature list to the CxfRs endpoint.

This option is used to specify the model file which is useful for the resource class without annotation. When using this option, then the service class can be omitted, to emulate document-only endpoints.

Set custom JAX-RS provider(s) list to the CxfRs endpoint. You can specify a string with a list of providers to lookup in the registy separated by comma.

The resource classes which you want to export as REST service. Multiple classes can be separated by comma.

Sets the locations of the schema(s) which can be used to validate the incoming XML or JAXB-driven JSON.

This option controls whether the PhaseInterceptorChain skips logging the Fault that it catches.

Configure a cookie handler to maintain a HTTP session.

The hostname verifier to be used. Use the # notation to reference a HostnameVerifier from the registry.

The Camel SSL setting reference. Use the # notation to reference the SSL Context.

This option tells the CxfRsProducer to inspect return codes and will generate an Exception if the return code is larger than 207.

If it is true, the CxfRsProducer will use the HttpClientAPI to invoke the service. If it is false, the CxfRsProducer will use the ProxyClientAPI to invoke the service.

This option is used to tell CxfRsProducer to ignore the message body of the DELETE method when using HTTP API.

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.

This option allows you to configure the maximum size of the cache. The implementation caches CXF clients or ClientFactoryBean in CxfProvider and CxfRsProvider.

Sets whether synchronous processing should be strictly used.

To use a custom CxfBinding to control the binding between Camel Message and CXF Message.

To use a custom configured CXF Bus.

This option is used to set the CXF continuation timeout which could be used in CxfConsumer by default when the CXF server is using Jetty or Servlet transport.

This option could apply the implementation of org.apache.camel.component.cxf.jaxrs.CxfRsEndpointConfigurer which supports to configure the CXF endpoint in programmatic way. User can configure the CXF server and client by implementing configure\{Server/Client} method of CxfEndpointConfigurer.

Will set the default bus when CXF endpoint create a bus by itself.

To use a custom HeaderFilterStrategy to filter header to and from Camel message.

When the option is true, Camel will perform the invocation of the resource class instance and put the response object into the exchange for further processing.

When the option is true, JAXRS UriInfo, HttpHeaders, Request and SecurityContext contexts will be available to custom CXFRS processors as typed Camel exchange properties. These contexts can be used to analyze the current requests using JAX-RS API.

This option enables CXF Logging Feature which writes inbound and outbound REST messages to log.

To limit the total size of number of bytes the logger will output when logging feature has been enabled and -1 for no limit.

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.

Sets whether synchronous processing should be strictly used.

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.

To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.

Enable usage of global SSL context parameters.