camel-cxf-kafka-connector sink configuration

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

The service publish address.

The data type messages supported by the CXF endpoint. One of: [PAYLOAD] [RAW] [MESSAGE] [CXF_MESSAGE] [POJO].

Enum values:

The WSDL style that describes how parameters are represented in the SOAP body. If the value is false, CXF will chose the document-literal unwrapped style, If the value is true, CXF will chose the document-literal wrapped style.

Configure a cookie handler to maintain a HTTP session.

This option will set the default operationName that will be used by the CxfProducer which invokes the remote service.

This option will set the default operationNamespace that will be used by the CxfProducer which invokes the remote service.

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.

Which kind of operation that CXF endpoint producer will invoke.

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.

This option controls whether the CXF component, when running in PAYLOAD mode, will DOM parse the incoming messages into DOM Elements or keep the payload as a javax.xml.transform.Source object that would allow streaming in some cases.

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.

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

This option could apply the implementation of org.apache.camel.component.cxf.CxfEndpointConfigurer which supports to configure the CXF endpoint in programmatic way. User can configure the CXF server and client by implementing configure{ServerClient} 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.

Whether to merge protocol headers. If enabled then propagating headers between Camel and CXF becomes more consistent and similar. For more details see CAMEL-6393.

To enable MTOM (attachments). This requires to use POJO or PAYLOAD data format mode.

To set additional CXF options using the key/value pairs from the Map. For example to turn on stacktraces in SOAP faults, properties.faultStackTraceEnabled=true.

Sets whether SOAP message validation should be disabled.

This option enables CXF Logging Feature which writes inbound and outbound SOAP 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.

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

This option is used to set the basic authentication information of password for the CXF client.

This option is used to set the basic authentication information of username for the CXF client.

The bindingId for the service model to use.

The endpoint name this service is implementing, it maps to the wsdl:portname. In the format of ns:PORT_NAME where ns is a namespace prefix valid at this scope.

This option can override the endpointUrl that published from the WSDL which can be accessed with service address url plus wsd.

The class name of the SEI (Service Endpoint Interface) class which could have JSR181 annotation or not.

The service name this service is implementing, it maps to the wsdl:servicename.

The location of the WSDL. Can be on the classpath, file system, or be hosted remotely.

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 controls whether the CXF component, when running in PAYLOAD mode, will DOM parse the incoming messages into DOM Elements or keep the payload as a javax.xml.transform.Source object that would allow streaming in some cases.

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.