Name | Required? | Description |
|---|
soapAction
| No | SOAP action to include inside a SOAP request when accessing remote web services |
wsAddressingAction
| No | WS-Addressing 1.0 action header to include when accessing web services. The To header is set to the address of the web service as specified in the endpoint URI (default Spring-WS behavior). |
| outputAction | No | Signifies the value for the response WS-Addressing Action header that is provided by the method. |
| faultAction | No | Signifies the value for the faultAction response WS-Addressing Fault Action header that is provided by the method. |
| faultTo | No | Signifies the value for the faultAction response WS-Addressing FaultTo header that is provided by the method. |
| replyTo | No | Signifies the value for the replyTo response WS-Addressing ReplyTo header that is provided by the method. |
expression
| Only when mapping-type is xpathresult | XPath expression to use in the process of mapping web service requests, should match the result specified by xpathresult |
timeout
| No | Camel 2.10: Sets the socket read timeout (in milliseconds) while invoking a webservice using the producer, see URLConnection.setReadTimeout() and CommonsHttpMessageSender.setReadTimeout(). This option works when using the built-in message sender implementations: CommonsHttpMessageSender and HttpUrlConnectionMessageSender. One of these implementations will be used by default for HTTP based services unless you customize the Spring WS configuration options supplied to the component. If you are using a non-standard sender, it is assumed that you will handle your own timeout configuration.
Camel 2.12: The built-in message sender HttpComponentsMessageSender is considered instead of CommonsHttpMessageSender which has been deprecated, see HttpComponentsMessageSender.setReadTimeout(). |
sslContextParameters
| No | Camel 2.10: Reference to an org.apache.camel.util.jsse.SSLContextParameters in the Registry. See Using the JSSE Configuration Utility. This option works when using the built-in message sender implementations: CommonsHttpMessageSender and HttpUrlConnectionMessageSender. One of these implementations will be used by default for HTTP based services unless you customize the Spring WS configuration options supplied to the component. If you are using a non-standard sender, it is assumed that you will handle your own TLS configuration.
Camel 2.12: The built-in message sender HttpComponentsMessageSender is considered instead of CommonsHttpMessageSender which has been deprecated. |
webServiceTemplate
| No | Option to provide a custom WebServiceTemplate. This allows for full control over client-side web services handling; like adding a custom interceptor or specifying a fault resolver, message sender or message factory. |
messageSender
| No | Option to provide a custom WebServiceMessageSender. For example to perform authentication or use alternative transports |
messageFactory
| No | Option to provide a custom WebServiceMessageFactory. For example when you want Apache Axiom to handle web service messages instead of SAAJ |
| endpointMappingKey | No | Reference to an instance of org.apache.camel.component.spring.ws.type.EndpointMappingKey |
endpointMapping
| Only when mapping-type is rootqname, soapaction, uri or xpathresult | Reference to an instance of org.apache.camel.component.spring.ws.bean.CamelEndpointMapping in the Registry/ApplicationContext. Only one bean is required in the registry to serve all Camel/Spring-WS endpoints. This bean is auto-discovered by the MessageDispatcher and used to map requests to Camel endpoints based on characteristics specified on the endpoint (like root QName, SOAP action, etc) |
| endpointDispatcher | No | Spring {@link org.springframework.ws.server.endpoint.MessageEndpoint} for dispatching messages received by Spring-WS to a Camel endpoint, to integrate with existing (legacy) endpoint mappings like PayloadRootQNameEndpointMapping, SoapActionEndpointMapping, etc. |
messageFilter
| No | Camel 2.10.3 Option to provide a custom MessageFilter. For example when you want to process your headers or attachments by your own. |
| messageIdStrategy | No | A custom MessageIdStrategy to control generation of unique message ids |
| webServiceEndpointUri | No | The default Web Service endpoint uri to use for the producer |
