[
https://issues.apache.org/jira/browse/CAMEL-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raul Kripalani updated CAMEL-7180:
----------------------------------
Description:
Will allow for something like:
{code}
.onCompletion().onCompleteOnly()
.onWhen(xpath("/result = 'ok'"))
.log("All good!")
.onWhen(xpath("/result = 'warn'"))
.log(LoggingLevel.WARN, "Something didn't go quite as right!")
.onOtherwise()
.log(LoggingLevel.ERROR, "Something went awfully wrong!")
.end()
{code}
This will specifically benefit route-level onComplete blocks, as only 1 is
supported per route. Currently, if you want to take decisions, you have to
create a nested choice() which feels clumsy, given that the onComplete DSL
already supports some degree of decision-making.
was:
Will allow for something like:
{code}
.onCompletion().onCompleteOnly()
.onWhen(xpath("/result = 'ok'"))
.log("All good!")
.onWhen(xpath("/result = 'warn'"))
.log(LoggingLevel.WARN, "Something didn't go quite as right!")
.onOtherwise()
.log(LoggingLevel.ERROR, "Something went awfully wrong!")
.end()
{code}
This will specifically benefit route-level onComplete blocks, as only 1 is
supported per route. So if you want to take decisions, you have to create a
nested choice() which feels clumsy, given that the onComplete DSL already
supports some degree of decision-making.
> Support multiple onWhen + onOtherwise in onComplete blocks
> ----------------------------------------------------------
>
> Key: CAMEL-7180
> URL: https://issues.apache.org/jira/browse/CAMEL-7180
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.12.2
> Reporter: Raul Kripalani
> Assignee: Raul Kripalani
>
> Will allow for something like:
> {code}
> .onCompletion().onCompleteOnly()
> .onWhen(xpath("/result = 'ok'"))
> .log("All good!")
> .onWhen(xpath("/result = 'warn'"))
> .log(LoggingLevel.WARN, "Something didn't go quite as right!")
> .onOtherwise()
> .log(LoggingLevel.ERROR, "Something went awfully wrong!")
> .end()
> {code}
> This will specifically benefit route-level onComplete blocks, as only 1 is
> supported per route. Currently, if you want to take decisions, you have to
> create a nested choice() which feels clumsy, given that the onComplete DSL
> already supports some degree of decision-making.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
