Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Date: Thu, 25 May 2017 09:20:54 -0700 (MST)
From: stalbot <steve.talbot@ahold.com>
To: users@camel.apache.org
Message-ID: <1495729254832-5800701.post@n5.nabble.com>
In-Reply-To: <CAGB5yNmxy66P8jkQOV6ef7XSk+zxO2=J65n3syZAkOhArYFsjg@mail.gmail.com>
References: <1495724656502-5800698.post@n5.nabble.com> <CAGB5yNmxy66P8jkQOV6ef7XSk+zxO2=J65n3syZAkOhArYFsjg@mail.gmail.com>
Subject: Re: Need to be able to change endpoint for recipientList when call
 is redelivered
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Thu, 25 May 2017 16:21:01 -0000

Hello, thank you for the reply and the suggestion.

My goal is not just to avoid the invalid endpoint, but to correct it to be
valid again and then redeliver.

So for some more context on what we are doing: a query parameter in the
endpoint is populated from a database, and over time it can cause the
recipientList call to fail because the value is out of date with the service
it calls.  Our code changes this query parameter so that the call will go
through and the query parameter will not be out of date with the service. 
We would like to use the redelivery feature to do this.

If we go with ".ignoreInvalidEndpoints()", the invalid call will not be
redelivered with the updated query parameter, it will just be avoided
altogether.

I am relatively new to camel and so I am not sure why our code uses
recipientList with a single endpoint but there you go.  If there is another
way to do this I am all ears! :)


--
View this message in context: http://camel.465427.n5.nabble.com/Need-to-be-able-to-change-endpoint-for-recipientList-when-call-is-redelivered-tp5800698p5800701.html
Sent from the Camel - Users mailing list archive at Nabble.com.