Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.14.0
-
None
-
Moderate
Description
Currently the camel-netty component supports setting encoders & decoders that enlisted in the registry.
It will be very helpful to have this functionality similarly supported in the camel-netty-http component too.
From what I saw, camel-netty's ClientPipelineFactory implementation (DefaultClientPipelineFactory) supports it in the getPipeline method but a similar implementation does not exist in camel-netty-http's ClientPipelineFactory implementation (HttpClientPipelineFactory).