Mule

Better exception strategy for tests

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix or Usage Issue
  • Affects Version/s: 1.3.3
  • Fix Version/s: None
  • Component/s: Core: API
  • Labels:
    None
  • User impact:
    Low
  • Similar Issues:
    MULE-3973 Better define reach of service vs. connector exception handling and exception handling and review/update implementation
    MULE-4515 default-service-exception-strategy does not honor exception-type-filter
    MULE-5808 Mule not invoking exception strategy when an exception is thrown in asynchronous flow
    MULE-14 Default exception strategy on the Model
    MULE-5738 When configuring <default-exception-strategy> inbound transaction is committed by default when no commit or rollback pattern is configured
    MULE-4233 Quartz connector ignores exception strategy
    MULE-6033 Missing image in the Testing+Strategies page
    MULE-4341 Transformerconfigured on an endpoint in exception-strategy are ignored
    MULE-3519 Out-of-box Retry exception Strategy
    MULE-2202 Need better way to organize/skip 'issues' tests

Description

We need a better ExceptionStrategy for tests. Currently all tests use the DefaultExceptionStrategy which clutters the log with errors even though exceptions were properly handled. Having a strategy that collects all exceptions will not only prevent the misleading logging but also allow us to catch exceptions that were swallowed, but not expected either.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Perepelytsya added a comment - 24/Apr/07 12:42 PM

Descoping the 1.4.1, unset Fix Version for some issues.

Show
Andrew Perepelytsya added a comment - 24/Apr/07 12:42 PM Descoping the 1.4.1, unset Fix Version for some issues.
Hide
Permalink
Dirk Olmes added a comment - 18/Jan/08 10:30 AM

The main objects that bear ExceptionListeners are: models, components and descriptors. The problem with the current code is that there's no way to dyanamiccaly e.g. get descriptors from a model in order to exchange the ExceptionListener there. Comonents retrieve the ExceptionListener from their descriptor at initialization time.

Also, there is no hook to make the config builder instantiate a different exception strategy for unit tests.

Conclusion: I don't think it is worthwile to investigate this any further.

Show
Dirk Olmes added a comment - 18/Jan/08 10:30 AM The main objects that bear ExceptionListeners are: models, components and descriptors. The problem with the current code is that there's no way to dyanamiccaly e.g. get descriptors from a model in order to exchange the ExceptionListener there. Comonents retrieve the ExceptionListener from their descriptor at initialization time. Also, there is no hook to make the config builder instantiate a different exception strategy for unit tests. Conclusion: I don't think it is worthwile to investigate this any further.

People

Vote (0)
Watch (0)

Dates

  • Created:
    16/Mar/07 09:55 AM
    Updated:
    18/Jan/08 10:30 AM
    Resolved:
    18/Jan/08 10:30 AM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.