camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Luo (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-7141) Custom HeaderFilterStrategy does not work when set it on either component or endpoint uri
Date Fri, 17 Jan 2014 17:58:19 GMT

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

Joe Luo updated CAMEL-7141:
---------------------------

    Description: 
Setting custom HeaderFilterStrategy on either NettyHttpComponent or NettyHttpEndpoint uri
does not work. The only way to get it to work is to create a NettyHttpBinding bean and set
the custom HeaderFilterStrategy as a property of the NettyHttpBinding bean and then set the
custom NettyHttpBinding bean onto either NettyHttpComponent and NettyHttpEndpoint uri.

The reason it does not work was that when applying the custom HeaderFilterStrategy, it is
not set on NettyHttpBinding object as the NettyHttpBinding object always uses default HeaderFilterStrategy.


I have attached the patch file. It might not be necessary to modify NettyHttpComponent class
but I thought it'd be better to initialize configuration, nettyBinding and headerFilterStrategy
in their getter method only when needed rather than in constructor of the NettyHttpComponent.

  was:
Setting custom HeaderFilterStrategy on either NettyHttpComponent or NettyHttpEndpoint url
does not work. The only way to get it to work is to create a  NettyHttpBinding bean and set
the custom HeaderFilterStrategy as a property and then apply the custom NettyHttpBinding bean
onto either NettyHttpComponent and NettyHttpEndpoint. 

The reason it does not work was that when applying the custom HeaderFilterStrategy, it is
not set on NettyHttpBinding object as the NettyHttpBinding object always uses default HeaderFilterStrategy.


I have attached the patch file. It might not be necessary to modify NettyHttpComponent class
but I thought it'd be better to initialize configuration, nettyBinding and headerFilterStrategy
in their getter method rather than in constructor of the NettyHttpComponent.


> Custom HeaderFilterStrategy does not work when set it on either component or endpoint
uri
> -----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7141
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7141
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-netty-http
>    Affects Versions: 2.12.2
>            Reporter: Joe Luo
>         Attachments: NettyHttpHeaderFilterBug.patch
>
>
> Setting custom HeaderFilterStrategy on either NettyHttpComponent or NettyHttpEndpoint
uri does not work. The only way to get it to work is to create a NettyHttpBinding bean and
set the custom HeaderFilterStrategy as a property of the NettyHttpBinding bean and then set
the custom NettyHttpBinding bean onto either NettyHttpComponent and NettyHttpEndpoint uri.
> The reason it does not work was that when applying the custom HeaderFilterStrategy, it
is not set on NettyHttpBinding object as the NettyHttpBinding object always uses default HeaderFilterStrategy.

> I have attached the patch file. It might not be necessary to modify NettyHttpComponent
class but I thought it'd be better to initialize configuration, nettyBinding and headerFilterStrategy
in their getter method only when needed rather than in constructor of the NettyHttpComponent.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message