Yes but then what about the messages that do not fail. I want them to be
moved also. If I handle the exception on the errorhandler the file-endpoint
does not register exception and the move-option is performed as if the route
was succesful.
Claus Ibsen-2 wrote:
>
> On Wed, May 26, 2010 at 10:54 AM, ankelee <andreasasm...@gmail.com> wrote:
>>
>> Hi Claus
>>
>> That's a good point.
>>
>> I want it to not be handled so the "move" option on the file endpoint in
>> the
>> beginning of my route only moves the file if the route was succesful. And
>> I
>> want to combine that with the errorhandling that the errorhandler can do
>> since I want to do some custom processing before sending the message to a
>> deadletterchannel. I would like to use moveFailed but that can't do what
>> I
>> want.
>>
>
> For custom processing you just do that on the EH configuration
>
> errorHandler(DLC stuff here).to("bean:xxx");
>
> Then Camel invokes the bean:xxx BEFORE the message is moved into the DLC.
> In fact its just another Camel route so you can continue routing here
> and do more steps.
> And after this route completes the message will be moved to the DLC.
>
>
>
>> Maybe I should do something else?
>>
>>
>>
>> Claus Ibsen-2 wrote:
>>>
>>> Hi
>>>
>>> Handled is @deprecated on <errorHandler/>. We want to keep it easier
>>> and remove stuff which would confuse people.
>>> Why would you want to not let an error handler NOT to handle an error.
>>>
>>>
>>>
>>> On Wed, May 26, 2010 at 10:26 AM, ankelee <andreasasm...@gmail.com>
>>> wrote:
>>>>
>>>> I do however see that your example in the JIRA ticket uses the handled
>>>> property - when I try to do the same I just get:
>>>>
>>>> Caused by:
>>>> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
>>>> Line
>>>> 70 in XML document from class path resource [opsigInboundRoute.xml] is
>>>> invalid; nested exception is org.xml.sax.SAXParseException:
>>>> cvc-complex-type.3.2.2: Attribute 'handled' is not allowed to appear in
>>>> element 'errorHandler'.
>>>>
>>>>
>>>>
>>>> ankelee wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Sorry I wasn't very clear. I'm using Camel 2.3 and the <errorHandler>
>>>>> tag
>>>>> in Spring DSL. I've been looking at the schema for 2.3 and also
>>>>>
>>>>> https://issues.apache.org/activemq/browse/CAMEL-1799
>>>>> and
>>>>> https://issues.apache.org/activemq/browse/CAMEL-1598
>>>>>
>>>>> and it seems that the handled-option is missing in Spring DSL?
>>>>>
>>>>>
>>>>>
>>>>> ankelee wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> From the doc pages:
>>>>>>
>>>>>> errorHandler(deadLetterChannel("jms:queue:dead").maximumRedeliveries(3).redeliverDealy(5000).handled(false));
>>>>>>
>>>>>> I can't figure out or find any information as to how do the
>>>>>> .handled()
>>>>>> in
>>>>>> Spring DSL. I wan't to leave the exception unhandled so that I can
>>>>>> have
>>>>>> my file endpoint do "move=" only if there is no exception in the
>>>>>> route.
>>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/errorHandler-%2B-.handled%28false%29%29--in-Spring-DSL.-tp28670904p28677820.html
>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> Apache Camel Committer
>>>
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>> Open Source Integration: http://fusesource.com
>>> Blog: http://davsclaus.blogspot.com/
>>> Twitter: http://twitter.com/davsclaus
>>>
>>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/errorHandler-%2B-.handled%28false%29%29--in-Spring-DSL.-tp28670904p28678072.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
>
--
View this message in context:
http://old.nabble.com/errorHandler-%2B-.handled%28false%29%29--in-Spring-DSL.-tp28670904p28678153.html
Sent from the Camel - Users mailing list archive at Nabble.com.
