[jira] [Reopened] (CAMEL-7848) Netty-Http component: add support for registry's encoders and decoders

["Yaron A (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yaron A reopened CAMEL-7848:
----------------------------
    Estimated Complexity: Moderate  (was: Unknown)

Sorry for this late response.
The fix did work properly in the netty-http component but there seem to be an issue with the netty4-http component.
The decoder I set, HttpContentDecompressor, is not properly applied in the current 2.14.1 snapshot version.
I managed to fix the issue by implementing my own ClientInitializerFactory which is a clone of HttpClientInitializerFactory with one small change:
the following line
pipeline.addLast("http", new HttpClientCodec());
should be placed before adding the encoders/decoders and not after.
Please review my suggestion and see if you find it as the proper solution

Thanks

> Netty-Http component: add support for registry's encoders and decoders
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-7848
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7848
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-netty-http
>    Affects Versions: 2.14.0
>            Reporter: Yaron A
>            Assignee: Willem Jiang
>             Fix For: 2.14.1, 2.15.0
>
>
> 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).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)