You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Yaron A (JIRA)" <ji...@apache.org> on 2014/10/26 12:00:35 UTC
[jira] [Issue Comment Deleted] (CAMEL-7848) Netty-Http component:
add support for registry's encoders and decoders
[ https://issues.apache.org/jira/browse/CAMEL-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yaron A updated CAMEL-7848:
---------------------------
Comment: was deleted
(was: I could not get the fix to work and it seems that there is no new snapshot which includes your fix commit, I looked here: http://tlvmvnrepository/artifactory/simple/apache-camel-cache/org/apache/camel/camel-netty4-http/2.14.1-SNAPSHOT/
how can I get an updated snapshot?)
> 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)