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

Freeman Fang resolved SMXCOMP-722.
----------------------------------

    Fix Version/s: servicemix-http-2010.02
                       (was: servicemix-bean-2010.02)
       Resolution: Fixed

apply patch on behalf of Ioannis Canellos with thanks
http://svn.apache.org/viewvc?rev=980660&view=rev

> Http Component & Http Provider Endpoint do not offer a way to change the 
> Jetty expiration time.
> -----------------------------------------------------------------------------------------------
>
>                 Key: SMXCOMP-722
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-722
>             Project: ServiceMix Components
>          Issue Type: Improvement
>          Components: servicemix-http
>    Affects Versions: servicemix-http-2008.01, servicemix-http-2009.01, 
> servicemix-http-2009.02
>            Reporter: Ioannis Canellos
>            Assignee: Freeman Fang
>             Fix For: servicemix-http-2010.02
>
>         Attachments: patchfile.txt
>
>
> A couple of weeks ago I submitted a patch that added support for Jetty Client 
> Expiration (read timeout) on the Http Provider Endpoint 
> :https://issues.apache.org/activemq/browse/SMXCOMP-717
> In most cases it is useful to be able to change the expiration time (the 
> amount of time the endpoint will wait for response) on the component and the 
> provider when using jettyClientPerProvider.
> I am attaching a patch that adds a new property called providerExpirationTime 
> on HttpConfiguration and HttpProviderEndpoint.
> The patch also updates:
> The HttpComponent to save / load the property from the components.property 
> file. 
> The HttpProviderEndpoint so that it is possible to set this property 
> explicitly per provider.
> Finally, it adds a new unit test that tests the above using the following 
> scenarios:
> test expiration using providerExpirationTime set on HttpComponent 
> configuration.
> test expiration using providerExpirationTime set on the provider.
> test no expiration.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to