[
http://mule.mulesource.org/jira/browse/MULE-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28114#action_28114
]

Rick Otten commented on MULE-3196:

----------------------------------

My impression was setting the default-service-exception strategy on the model
would apply to all of the services within that model.

Unfortunately when I do this, and get an exception, I get this error:

ERROR 2008-12-17 13:02:00,596 [JST_STN_Test.2]
org.mule.service.DefaultServiceExceptionStrategy: The Default Service Exception
Strategy has been invoked but there is no current service on the context. Please
report this to de...@mule.codehaus.org

ERROR 2008-12-17 13:02:00,602 [JST_STN_Test.2]
org.mule.service.DefaultServiceExceptionStrategy: The Default Service Exception
Strategy has been invoked but there is no current service on the context. Please
report this to de...@mule.codehaus.org

I'm testing this by sending message a bogus host name to an http outbound
endpoint.

If you have a default-service-exception-strategy for the whole model, it
shouldn't matter whether you have a specific service on the context, should it?
[ Which is why I posted the issue as a comment on this JIRA.]

When I configure the default-service-exception-strategy on the specific service,
I get this error as well. So I guess putting in a non-existent server address
for an http outbound endpoint causes an exception that can't be strategized.
:-( [ Should I open a separate JIRA for that? ]