Skip to content

Commit

Permalink
fix: upgrade Apache Camel model to 3.21.3
Browse files Browse the repository at this point in the history
  • Loading branch information
tadayosi committed Dec 20, 2023
1 parent 4388550 commit be58b8f
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
<version>1.0</version>

<properties>
<version.org.apache.camel>3.21.2</version.org.apache.camel>
<version.org.apache.camel>3.21.3</version.org.apache.camel>

<version.camel.catalog.maven.plugin>1.0.0</version.camel.catalog.maven.plugin>
<version.groovy.maven.plugin>2.1.1</version.groovy.maven.plugin>
Expand Down
2 changes: 1 addition & 1 deletion src/components-camel-model.json
Original file line number Diff line number Diff line change
Expand Up @@ -44254,7 +44254,7 @@
"kind": "parameter",
"type": "boolean",
"defaultValue": "false",
"description": "This options controls what happens when a consumer is processing an exchange and it fails. If the option is false then the consumer continues to the next message and processes it. If the option is true then the consumer breaks out, and will seek back to offset of the message that caused a failure, and then re-attempt to process this message. However this can lead to endless processing of the same message if its bound to fail every time, eg a poison message. Therefore its recommended to deal with that for example by using Camel\u0027s error handler.",
"description": "This options controls what happens when a consumer is processing an exchange and it fails. If the option is false then the consumer continues to the next message and processes it. If the option is true then the consumer breaks out. Using the default NoopCommitManager will cause the consumer to not commit the offset so that the message is re-attempted. The consumer should use the KafkaManualCommit to determine the best way to handle the message. Using either the SynchCommitManager or the AsynchCommitManager the consumer will seek back to the offset of the message that caused a failure, and then re-attempt to process this message. However this can lead to endless processing of the same message if its bound to fail every time, eg a poison message. Therefore its recommended to deal with that for example by using Camel\u0027s error handler.",
"title": "Break On First Error",
"required": false,
"deprecated": false
Expand Down
2 changes: 1 addition & 1 deletion src/index.ts
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,6 @@ import { dataformats } from './dataformats-camel-model.json'
import { languages } from './languages-camel-model.json'
import { components } from './components-camel-model.json'

const apacheCamelModelVersion = '3.21.2'
const apacheCamelModelVersion = '3.21.3'

export { definitions, rests, dataformats, languages, components, apacheCamelModelVersion }

0 comments on commit be58b8f

Please sign in to comment.