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

["Willem Jiang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144182#comment-14144182 ] 

Willem Jiang commented on CAMEL-7848:
-------------------------------------

Normally we don't need to add additional encoders or decoders for the Netty-Http component, as it use the stander HTTP protocol.
Can you give an example that why you apply the custom encoders or decoders to the Netty-Http endpoint?

> 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
>
> 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)