camel-cxf-kafka-connector source 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.

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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.

To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.

Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut].

Enum values:

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.

Enable schema validation for request and response. Disabled by default for performance reason.

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.

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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.

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.