Mule

Why not? This is in line with 1.x where configuring an dexception stategy on a model would use that exception strategy for components and connectors, IIRC. The name default-connector-exception-strategy is somewhat misleading then ...

I wasn't sure, it just seemed out of place given that there is a separate element for <default-service-exception-strategy>.

Looking at the code it seems that <default-service....>, <default-connector....> and <custom-exception....> all set the same attribute on the service. Not sure why we have both service and connector options and what the difference is though,,

Also, as it seems it will only allow one or the other but not both, you cannot configure both a <default-service..> and a <default-connector...> on a model. Furthermore, you could also set a <default-service..> exception strategy on the connector, so basically asking the same question as Daniel Feist... does it make sense there? And again, you have to choose one or the other, either <default-service..> or <default-connector..> on the connector, similar to the model.

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 dev@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 dev@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? ]

I figure the exception is thrown on a connector level, put the exception strategy on http connector instead.

I have hit a similar issue, however my case differs with Ricks example.

An exception is thrown from the service component, and i have a default service exception strategy defined like so:

<model name="MyModel">
<service name="MyService">
<inbound>
<inbound-endpoint ref="RequestEndPoint" />
</inbound>
<pooled-component>
<spring-object bean="persistenceObj" />
</pooled-component>
<outbound>
<pass-through-router>
<outbound-endpoint ref="AckEndpoint" />
</pass-through-router>
</outbound>
<default-service-exception-strategy
enableNotifications="false">
<jms:outbound-endpoint ref="ErrorEndpoint" />
</default-service-exception-strategy>
</service>
</model>

Which causes exact same error;

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 dev@mule.codehaus.org

Is this not a valid usecase? i.e. it doesn't make sense to have the exception stratgey defined at the connector level.

There is no more default-connector-exception-strategy in 3.x