[
https://issues.apache.org/activemq/browse/CAMEL-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60541#action_60541
]
Marco Crivellaro commented on CAMEL-2924:
-----------------------------------------
I am using a recipientList, in order to get additional parameters needed in my
process (each for every endpoint)
I make use of resolveEndpoint to get the URI Camel is using internally to
identify the endpoint (using a map with the URI as the key).
I thought this was a bug, as this is by design I will change the way I am
currently creating the recipientList (by fist getting URI out of
resolveEndpoint).
I've got a side question about this "lenient parameters":
would it be possible to have them in FTP component as well?
we are currently facing the problem that delivering several files (different
file names) to a given FTP is creating a new FTP endpoint (and therefore
connection) each time;
I know we can set the option to disconnect after every delivery but I think it
would improve performances if we do not connect/disconnect on each file (we are
sending a huge amount of data).
I can create a new ticket for this if you think it is sensible.
Thank you for the reply I really appreciate the responses I receive each time.
> httpClient.soTimeout property is not returned when getting HTTP endpoint URI
> ----------------------------------------------------------------------------
>
> Key: CAMEL-2924
> URL: https://issues.apache.org/activemq/browse/CAMEL-2924
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 2.3.0
> Environment: Windows
> Reporter: Marco Crivellaro
>
> getting the endpoint URI of an HTTP EndPoint with httpClient.soTimeout
> property set won't return the property
> i.e:
> "http://crive.optadev.com/valde/utils/posttest.php?httpClient.soTimeout=5000";
> is returned as "http://crive.optadev.com/valde/utils/posttest.php";
> * I have noticed this using ExchangeHelper.resolveEndpoint:
> String uri =
> "http://crive.optadev.com/valde/utils/posttest.php?httpClient.soTimeout=5000";;
> uri = ExchangeHelper.resolveEndpoint(exchange, uri.trim()).getEndpointUri();
> //uri is now missing httpClient.soTimeout=5000
> * it is also happening reading @Header(Exchange.TO_ENDPOINT)
> this is not happening when using the soTimeout option in FTP component.
> I think this is a major issue as recipientList is making use of
> ExchangeHelper and therefore the option will be ingored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
