You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by tkatva <tu...@gmail.com> on 2012/02/22 08:28:55 UTC
Endpoint exception handling
Hello
Camel is great but one thing I am wondering is that is there a way to catch
a Endpoint exception ? For example if I am polling on a directory and the
url is spelled wrong, can I catch that exception programmatically ? Or do
just need to check the log for it ?
Thank you
Best Regards Tuomas Katva
--
View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5504378.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Endpoint exception handling
Posted by Alex Anderson <al...@frontlinesms.com>.
Thanks for the clarification, Claus. I had assumed initially that
ExceptionHandler was the way to go, but (unsurprisingly) I couldn't
find a need way to configure it. Propagating Exceptions into the
consumer's processor will do me for now, but I look forward to seeing
more development in this area in future.
Thanks,
Alex
On 22 February 2012 16:57, Claus Ibsen <cl...@gmail.com> wrote:
> On Wed, Feb 22, 2012 at 12:02 PM, Alex Anderson <al...@frontlinesms.com> wrote:
>> Thanks for the confirmation that this is ok, Claus. Are there any
>> other ways to do this within Camel, or would there otherwise need to
>> be an external event listener to catch problems within the Endpoint?
>>
>
> There is a ExceptionHandler interface that consumers have by default.
> That is usually configured to use the logging implementation. We do
> not have exposed an easy way to configure and use a custom
> implementation, as well how to configure a specific one in an endpoint
> uri. We may do this in the future.
>
> And we have in the past talked about allowing consumers to send empty
> messages with exception into the routing engine, so people can use the
> Camel error handler for that. There is an old JIRA ticket for that.
>
> But in the end it will always be consumer specific how they deal with
> initial errors, before they hand over a message to Camel.
>
>
>> Alex
>>
>>
>> On 22 February 2012 13:16, Claus Ibsen <cl...@gmail.com> wrote:
>>> On Wed, Feb 22, 2012 at 8:59 AM, Alex Anderson <al...@frontlinesms.com> wrote:
>>>> Hi Claus & Tuomas,
>>>>
>>>> I faced a similar problem a couple of weeks ago and came to the
>>>> following solution:
>>>>
>>>> The exception can be passed to a route in the Consumer like so:
>>>>
>>>> public void handleEndpointException(EndpointException ex) {
>>>> Exchange exchange = getEndpoint().createExchange();
>>>> exchange.setException(ex);
>>>> getProcessor().process(exchange);
>>>> }
>>>>
>>>> The exception can then be handled by an onException clause():
>>>>
>>>> ...route-definition...
>>>> .onException(EndpointException)
>>>> .handled(true)
>>>> .beanRef("someService", "handleEndpointException")
>>>> .end()
>>>>
>>>> And in someService, I have the following method:
>>>>
>>>> def handleEndpointException(Exchange ex) {
>>>> EndpointException caughtException = (EndpointException)
>>>> ex.getProperty(Exchange.EXCEPTION_CAUGHT);
>>>> ...
>>>> }
>>>>
>>>> Claus, please tell me if this is foolish!
>>>>
>>>
>>> That is one way of doing it, mind that this requires end users to
>>> setup the onException(EndpointException.class) to ensure they handled
>>> that.
>>>
>>> Also it requires your consumers to implement this logic to support
>>> this kind of error handling.
>>>
>>>
>>>
>>>
>>>> Thanks,
>>>>
>>>> Alex
>>>>
>>>>
>>>> On 22 February 2012 10:42, Claus Ibsen <cl...@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> If you mean a consumer, such as eg
>>>>> from("file:foo")
>>>>>
>>>>> Then that would be consumer specific how it validates and reports
>>>>> mis-configuration.
>>>>>
>>>>> You cannot use the onException / dead letter channel for that. As its
>>>>> like chicken-egg. You need a valid message in the Camel routing
>>>>> engine, before onException / dead letter channel can be used.
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Feb 22, 2012 at 8:28 AM, tkatva <tu...@gmail.com> wrote:
>>>>>> Hello
>>>>>>
>>>>>> Camel is great but one thing I am wondering is that is there a way to catch
>>>>>> a Endpoint exception ? For example if I am polling on a directory and the
>>>>>> url is spelled wrong, can I catch that exception programmatically ? Or do
>>>>>> just need to check the log for it ?
>>>>>>
>>>>>> Thank you
>>>>>>
>>>>>> Best Regards Tuomas Katva
>>>>>>
>>>>>> --
>>>>>> View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5504378.html
>>>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> FuseSource
>>>>> Email: cibsen@fusesource.com
>>>>> Web: http://fusesource.com
>>>>> Twitter: davsclaus, fusenews
>>>>> Blog: http://davsclaus.blogspot.com/
>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> FuseSource
>>> Email: cibsen@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.blogspot.com/
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
Re: Endpoint exception handling
Posted by Claus Ibsen <cl...@gmail.com>.
On Fri, Feb 24, 2012 at 9:12 PM, tkatva <tu...@gmail.com> wrote:
> Hi Claus
>
> Thank you for your responses... My concern is that I want polling
> FTP/FTPS/SFTP/FILE-endpoints to call my custom code if error occurs... Can
> you point me to a example where I can see how I can apply this
> pollingStrategy to these endpoints ?
>
> I am constructing endpoints programmatically and creating url's based on
> values received from database. Here is part of my code:
>
> RouteDefinition routeDef = new RouteDefinition();
>
> //Endpoint url constructed from values from db
> org.apache.camel.Endpoint fromEnd = camel.getEndpoint(fromUrl);
>
> routeDef.from(fromEnd);
>
> //Add "to" endpoints which are constructed the same way
> routeDef.to(toEndpoints);
>
> Then route is added to CamelContext and started later.
>
> If you could show example how I could add pollingStrategy to
> "fromEnd"-endpoint, you would save my week or maybe whole month ... :)
>
You would need to register your custom poll strategy in the registry.
If you use Spring XML then its a <bean> tag.
If you use standalone Java, then you may want to use the
SimpleRegistry with CamelContext and add it to this strategy from java
code.
Then in the endpoint uri, you just refer to the id of your custom poll
strategy using #id
file:foo?pollStrategy=#myPollStrategy
If you use Spring XML then
<bean id="myPollStrategy" class="com.foo.MyPollStrategyImplementation"/>
> Thank you
>
> Best Regards Tuomas Katva
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5513828.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: Endpoint exception handling
Posted by tkatva <tu...@gmail.com>.
Hi Claus
Thank you for your responses... My concern is that I want polling
FTP/FTPS/SFTP/FILE-endpoints to call my custom code if error occurs... Can
you point me to a example where I can see how I can apply this
pollingStrategy to these endpoints ?
I am constructing endpoints programmatically and creating url's based on
values received from database. Here is part of my code:
RouteDefinition routeDef = new RouteDefinition();
//Endpoint url constructed from values from db
org.apache.camel.Endpoint fromEnd = camel.getEndpoint(fromUrl);
routeDef.from(fromEnd);
//Add "to" endpoints which are constructed the same way
routeDef.to(toEndpoints);
Then route is added to CamelContext and started later.
If you could show example how I could add pollingStrategy to
"fromEnd"-endpoint, you would save my week or maybe whole month ... :)
Thank you
Best Regards Tuomas Katva
--
View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5513828.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Endpoint exception handling
Posted by Claus Ibsen <cl...@gmail.com>.
On Wed, Feb 22, 2012 at 12:02 PM, Alex Anderson <al...@frontlinesms.com> wrote:
> Thanks for the confirmation that this is ok, Claus. Are there any
> other ways to do this within Camel, or would there otherwise need to
> be an external event listener to catch problems within the Endpoint?
>
There is a ExceptionHandler interface that consumers have by default.
That is usually configured to use the logging implementation. We do
not have exposed an easy way to configure and use a custom
implementation, as well how to configure a specific one in an endpoint
uri. We may do this in the future.
And we have in the past talked about allowing consumers to send empty
messages with exception into the routing engine, so people can use the
Camel error handler for that. There is an old JIRA ticket for that.
But in the end it will always be consumer specific how they deal with
initial errors, before they hand over a message to Camel.
> Alex
>
>
> On 22 February 2012 13:16, Claus Ibsen <cl...@gmail.com> wrote:
>> On Wed, Feb 22, 2012 at 8:59 AM, Alex Anderson <al...@frontlinesms.com> wrote:
>>> Hi Claus & Tuomas,
>>>
>>> I faced a similar problem a couple of weeks ago and came to the
>>> following solution:
>>>
>>> The exception can be passed to a route in the Consumer like so:
>>>
>>> public void handleEndpointException(EndpointException ex) {
>>> Exchange exchange = getEndpoint().createExchange();
>>> exchange.setException(ex);
>>> getProcessor().process(exchange);
>>> }
>>>
>>> The exception can then be handled by an onException clause():
>>>
>>> ...route-definition...
>>> .onException(EndpointException)
>>> .handled(true)
>>> .beanRef("someService", "handleEndpointException")
>>> .end()
>>>
>>> And in someService, I have the following method:
>>>
>>> def handleEndpointException(Exchange ex) {
>>> EndpointException caughtException = (EndpointException)
>>> ex.getProperty(Exchange.EXCEPTION_CAUGHT);
>>> ...
>>> }
>>>
>>> Claus, please tell me if this is foolish!
>>>
>>
>> That is one way of doing it, mind that this requires end users to
>> setup the onException(EndpointException.class) to ensure they handled
>> that.
>>
>> Also it requires your consumers to implement this logic to support
>> this kind of error handling.
>>
>>
>>
>>
>>> Thanks,
>>>
>>> Alex
>>>
>>>
>>> On 22 February 2012 10:42, Claus Ibsen <cl...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> If you mean a consumer, such as eg
>>>> from("file:foo")
>>>>
>>>> Then that would be consumer specific how it validates and reports
>>>> mis-configuration.
>>>>
>>>> You cannot use the onException / dead letter channel for that. As its
>>>> like chicken-egg. You need a valid message in the Camel routing
>>>> engine, before onException / dead letter channel can be used.
>>>>
>>>>
>>>>
>>>> On Wed, Feb 22, 2012 at 8:28 AM, tkatva <tu...@gmail.com> wrote:
>>>>> Hello
>>>>>
>>>>> Camel is great but one thing I am wondering is that is there a way to catch
>>>>> a Endpoint exception ? For example if I am polling on a directory and the
>>>>> url is spelled wrong, can I catch that exception programmatically ? Or do
>>>>> just need to check the log for it ?
>>>>>
>>>>> Thank you
>>>>>
>>>>> Best Regards Tuomas Katva
>>>>>
>>>>> --
>>>>> View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5504378.html
>>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> FuseSource
>>>> Email: cibsen@fusesource.com
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus, fusenews
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: Endpoint exception handling
Posted by Alex Anderson <al...@frontlinesms.com>.
Thanks for the confirmation that this is ok, Claus. Are there any
other ways to do this within Camel, or would there otherwise need to
be an external event listener to catch problems within the Endpoint?
Alex
On 22 February 2012 13:16, Claus Ibsen <cl...@gmail.com> wrote:
> On Wed, Feb 22, 2012 at 8:59 AM, Alex Anderson <al...@frontlinesms.com> wrote:
>> Hi Claus & Tuomas,
>>
>> I faced a similar problem a couple of weeks ago and came to the
>> following solution:
>>
>> The exception can be passed to a route in the Consumer like so:
>>
>> public void handleEndpointException(EndpointException ex) {
>> Exchange exchange = getEndpoint().createExchange();
>> exchange.setException(ex);
>> getProcessor().process(exchange);
>> }
>>
>> The exception can then be handled by an onException clause():
>>
>> ...route-definition...
>> .onException(EndpointException)
>> .handled(true)
>> .beanRef("someService", "handleEndpointException")
>> .end()
>>
>> And in someService, I have the following method:
>>
>> def handleEndpointException(Exchange ex) {
>> EndpointException caughtException = (EndpointException)
>> ex.getProperty(Exchange.EXCEPTION_CAUGHT);
>> ...
>> }
>>
>> Claus, please tell me if this is foolish!
>>
>
> That is one way of doing it, mind that this requires end users to
> setup the onException(EndpointException.class) to ensure they handled
> that.
>
> Also it requires your consumers to implement this logic to support
> this kind of error handling.
>
>
>
>
>> Thanks,
>>
>> Alex
>>
>>
>> On 22 February 2012 10:42, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> If you mean a consumer, such as eg
>>> from("file:foo")
>>>
>>> Then that would be consumer specific how it validates and reports
>>> mis-configuration.
>>>
>>> You cannot use the onException / dead letter channel for that. As its
>>> like chicken-egg. You need a valid message in the Camel routing
>>> engine, before onException / dead letter channel can be used.
>>>
>>>
>>>
>>> On Wed, Feb 22, 2012 at 8:28 AM, tkatva <tu...@gmail.com> wrote:
>>>> Hello
>>>>
>>>> Camel is great but one thing I am wondering is that is there a way to catch
>>>> a Endpoint exception ? For example if I am polling on a directory and the
>>>> url is spelled wrong, can I catch that exception programmatically ? Or do
>>>> just need to check the log for it ?
>>>>
>>>> Thank you
>>>>
>>>> Best Regards Tuomas Katva
>>>>
>>>> --
>>>> View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5504378.html
>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> FuseSource
>>> Email: cibsen@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.blogspot.com/
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
Re: Endpoint exception handling
Posted by Claus Ibsen <cl...@gmail.com>.
On Wed, Feb 22, 2012 at 8:59 AM, Alex Anderson <al...@frontlinesms.com> wrote:
> Hi Claus & Tuomas,
>
> I faced a similar problem a couple of weeks ago and came to the
> following solution:
>
> The exception can be passed to a route in the Consumer like so:
>
> public void handleEndpointException(EndpointException ex) {
> Exchange exchange = getEndpoint().createExchange();
> exchange.setException(ex);
> getProcessor().process(exchange);
> }
>
> The exception can then be handled by an onException clause():
>
> ...route-definition...
> .onException(EndpointException)
> .handled(true)
> .beanRef("someService", "handleEndpointException")
> .end()
>
> And in someService, I have the following method:
>
> def handleEndpointException(Exchange ex) {
> EndpointException caughtException = (EndpointException)
> ex.getProperty(Exchange.EXCEPTION_CAUGHT);
> ...
> }
>
> Claus, please tell me if this is foolish!
>
That is one way of doing it, mind that this requires end users to
setup the onException(EndpointException.class) to ensure they handled
that.
Also it requires your consumers to implement this logic to support
this kind of error handling.
> Thanks,
>
> Alex
>
>
> On 22 February 2012 10:42, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> If you mean a consumer, such as eg
>> from("file:foo")
>>
>> Then that would be consumer specific how it validates and reports
>> mis-configuration.
>>
>> You cannot use the onException / dead letter channel for that. As its
>> like chicken-egg. You need a valid message in the Camel routing
>> engine, before onException / dead letter channel can be used.
>>
>>
>>
>> On Wed, Feb 22, 2012 at 8:28 AM, tkatva <tu...@gmail.com> wrote:
>>> Hello
>>>
>>> Camel is great but one thing I am wondering is that is there a way to catch
>>> a Endpoint exception ? For example if I am polling on a directory and the
>>> url is spelled wrong, can I catch that exception programmatically ? Or do
>>> just need to check the log for it ?
>>>
>>> Thank you
>>>
>>> Best Regards Tuomas Katva
>>>
>>> --
>>> View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5504378.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: Endpoint exception handling
Posted by rams <ra...@gmail.com>.
Hi,
Here you used two methods of same name handleEndpointException(). Out of
these two which one should use in someService class to handle endpoint
exception. Could you please provide complete example for my understanding?
Thanks
Ram
--
View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5751466.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Endpoint exception handling
Posted by Alex Anderson <al...@frontlinesms.com>.
Hi Claus & Tuomas,
I faced a similar problem a couple of weeks ago and came to the
following solution:
The exception can be passed to a route in the Consumer like so:
public void handleEndpointException(EndpointException ex) {
Exchange exchange = getEndpoint().createExchange();
exchange.setException(ex);
getProcessor().process(exchange);
}
The exception can then be handled by an onException clause():
...route-definition...
.onException(EndpointException)
.handled(true)
.beanRef("someService", "handleEndpointException")
.end()
And in someService, I have the following method:
def handleEndpointException(Exchange ex) {
EndpointException caughtException = (EndpointException)
ex.getProperty(Exchange.EXCEPTION_CAUGHT);
...
}
Claus, please tell me if this is foolish!
Thanks,
Alex
On 22 February 2012 10:42, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> If you mean a consumer, such as eg
> from("file:foo")
>
> Then that would be consumer specific how it validates and reports
> mis-configuration.
>
> You cannot use the onException / dead letter channel for that. As its
> like chicken-egg. You need a valid message in the Camel routing
> engine, before onException / dead letter channel can be used.
>
>
>
> On Wed, Feb 22, 2012 at 8:28 AM, tkatva <tu...@gmail.com> wrote:
>> Hello
>>
>> Camel is great but one thing I am wondering is that is there a way to catch
>> a Endpoint exception ? For example if I am polling on a directory and the
>> url is spelled wrong, can I catch that exception programmatically ? Or do
>> just need to check the log for it ?
>>
>> Thank you
>>
>> Best Regards Tuomas Katva
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5504378.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
Re: Endpoint exception handling
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
See the pollStrategy option on the file/ftp components
http://camel.apache.org/file2
On Wed, Feb 22, 2012 at 8:49 AM, tkatva <tu...@gmail.com> wrote:
> Hi, thank you for your quick response...
>
> And yes I mean consumer, so is there anyway to get programmatically
> "notified" if exception occurs in consuming endpoint ? In for example
> FTP/FTPS/SFTP/FILE endpoints ? I would like to run my custom code whenever
> exception occurs in consuming endpoints ....
>
> Thank you
>
> Best Regards Tuomas Katva
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5504428.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: Endpoint exception handling
Posted by tkatva <tu...@gmail.com>.
Hi, thank you for your quick response...
And yes I mean consumer, so is there anyway to get programmatically
"notified" if exception occurs in consuming endpoint ? In for example
FTP/FTPS/SFTP/FILE endpoints ? I would like to run my custom code whenever
exception occurs in consuming endpoints ....
Thank you
Best Regards Tuomas Katva
--
View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5504428.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Endpoint exception handling
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
If you mean a consumer, such as eg
from("file:foo")
Then that would be consumer specific how it validates and reports
mis-configuration.
You cannot use the onException / dead letter channel for that. As its
like chicken-egg. You need a valid message in the Camel routing
engine, before onException / dead letter channel can be used.
On Wed, Feb 22, 2012 at 8:28 AM, tkatva <tu...@gmail.com> wrote:
> Hello
>
> Camel is great but one thing I am wondering is that is there a way to catch
> a Endpoint exception ? For example if I am polling on a directory and the
> url is spelled wrong, can I catch that exception programmatically ? Or do
> just need to check the log for it ?
>
> Thank you
>
> Best Regards Tuomas Katva
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Endpoint-exception-handling-tp5504378p5504378.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/