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.Ĭ-total-connections By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. 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. Whether the producer should be started lazy (on the first message). To use a custom .HttpContext when executing requests. The option is a .common.HttpConfiguration type. To use the shared HttpConfiguration as base configuration. The option is a .http.HttpClientConfigurer type. To use the custom HttpClientConfigurer to perform configuration of the HttpClient that will be used. The option is a .common.HttpBinding type.Ĭ-client-configurer To use a custom HttpBinding to control the mapping between Camel message and HttpClient. The option is a .HeaderFilterStrategy type. To use a custom .HeaderFilterStrategy to filter header to and from Camel message. This is enabled by default.Ĭ-filter-strategy Whether to enable auto configuration of the http component. Setting this to false, allows to only include the headers from the HTTP response (not propagating IN headers).Ĭ-user-agent-disabledĭisables the default user agent set by this builder if none has been provided by the user. If this option is true then IN exchange headers will be copied to OUT exchange headers according to copy strategy. Notice if bridgeEndpoint=true then the cookie store is forced to be a noop cookie store as cookie shouldn’t be stored as we are just bridging (eg acting as a proxy). By default the .client.BasicCookieStore is used which is an in-memory only cookie store. The maximum number of connections per route.Ĭ-compression-disabledĭisables automatic content decompression.Ĭ-management-disabled The time for connection to live, the time unit is millisecond, the default value is always keep alive.Ĭ-per-route A negative value is interpreted as undefined (system default).Ĭ-state-disabledĬ-time-to-live A timeout value of zero is interpreted as an infinite timeout. The timeout in milliseconds used when requesting a connection from the connection manager. A negative value is interpreted as undefined (system default).Ĭ-request-timeout ![]() ![]() The option is a .HttpClientConnectionManager type.ĭetermines the timeout in milliseconds until a connection is established. If this has been configured then this is always used for all endpoints created by this component. ![]() To use a custom and shared HttpClientConnectionManager to manage connections. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.Ĭ-connection-manager 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. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk.Ĭ-caching-disabledĬ-retries-disabledĭisables automatic request recovery and re-execution. Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. If setting this option to true, then the producers will not cache the response body stream but use the response stream as-is as the message body.Ĭ-java-serialized-object The http producer will by default cache the response body stream. If you use Servlet to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times. DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support reading the stream multiple times. However you can set this option to true when you for example need to access the raw stream, such as streaming it directly to a file or other persistent store. By default Camel will cache the Servlet input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. Determines whether or not the raw input stream from Servlet is cached or not (Camel will read the stream into a in memory/overflow to file, Stream caching) cache.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |