Configuration patterns do not inherit exception strategies from their parent model

Details

  • User impact:
    Medium
  • Configuration:
    Hide

    <model>
    <default-service-exception-strategy>
    <vm:outbound-endpoint path="modelout" exchange-pattern="one-way"
    connector-ref="vmConnector"/>
    </default-service-exception-strategy>

    <simple-service name="testSS2"
    address="vm://inss2">
    <test:component throwException="true" />
    </simple-service>
    </model>

    Show
    <model> <default-service-exception-strategy> <vm:outbound-endpoint path="modelout" exchange-pattern="one-way" connector-ref="vmConnector"/> </default-service-exception-strategy> <simple-service name="testSS2" address="vm://inss2"> <test:component throwException="true" /> </simple-service> </model>
  • Similar Issues:
    None

Description

If a configuration strategy is nested inside a model, it does not inherit that models exception strategy. This is inconsistent with services.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
David Dossot added a comment -

We have two options:

1. prevent patterns to be added into model (like flow which can only exist outside of model)
2. make patterns model aware (which would be inconsistent with flow)

I think #1 is better.

Show
David Dossot added a comment - We have two options: 1. prevent patterns to be added into model (like flow which can only exist outside of model) 2. make patterns model aware (which would be inconsistent with flow) I think #1 is better.
Hide
Permalink
Mike Schilling added a comment -

If we don't lose anything by removing patterns from models, then #1 makes sense to me too.

Show
Mike Schilling added a comment - If we don't lose anything by removing patterns from models, then #1 makes sense to me too.
Hide
Permalink
David Dossot added a comment -

Do you know what is our policy for non-backwards compatible schema change? Can this go into 3.0.1 or does it have to wait for 3.1?

Show
David Dossot added a comment - Do you know what is our policy for non-backwards compatible schema change? Can this go into 3.0.1 or does it have to wait for 3.1?
Hide
Permalink
Dirk Olmes added a comment -

It will have to wait for 3.1.

Show
Dirk Olmes added a comment - It will have to wait for 3.1.
Hide
Permalink
David Dossot added a comment -

OK, so at this time why don't I just log a warning when we detect a pattern in model saying that this won't be allowed in 3.1 anymore.

Show
David Dossot added a comment - OK, so at this time why don't I just log a warning when we detect a pattern in model saying that this won't be allowed in 3.1 anymore.
Hide
Permalink
Mike Schilling added a comment -

Fixed in http://fisheye.codehaus.org/changelog/mule/?cs=20203. Config patterns can no long be nested inside models

Show
Mike Schilling added a comment - Fixed in http://fisheye.codehaus.org/changelog/mule/?cs=20203. Config patterns can no long be nested inside models

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: