[jira] [Assigned] (CAMEL-17748) camel-any23 - Upgrade to 2.7
[ https://issues.apache.org/jira/browse/CAMEL-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-17748: --- Assignee: Claus Ibsen > camel-any23 - Upgrade to 2.7 > > > Key: CAMEL-17748 > URL: https://issues.apache.org/jira/browse/CAMEL-17748 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.14.3, 3.16.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17748) camel-any23 - Upgrade to 2.7
[ https://issues.apache.org/jira/browse/CAMEL-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17748: Fix Version/s: 3.14.3 > camel-any23 - Upgrade to 2.7 > > > Key: CAMEL-17748 > URL: https://issues.apache.org/jira/browse/CAMEL-17748 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.14.3, 3.16.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17746) add tests in camel-gson-starter
[ https://issues.apache.org/jira/browse/CAMEL-17746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang resolved CAMEL-17746. -- Fix Version/s: 3.16.0 Resolution: Fixed > add tests in camel-gson-starter > --- > > Key: CAMEL-17746 > URL: https://issues.apache.org/jira/browse/CAMEL-17746 > Project: Camel > Issue Type: Test > Components: camel-gson, camel-spring-boot-starters, tests >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.16.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17746) add tests in camel-gson-starter
[ https://issues.apache.org/jira/browse/CAMEL-17746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501544#comment-17501544 ] Freeman Yue Fang commented on CAMEL-17746: -- PR is https://github.com/apache/camel-spring-boot/pull/455 > add tests in camel-gson-starter > --- > > Key: CAMEL-17746 > URL: https://issues.apache.org/jira/browse/CAMEL-17746 > Project: Camel > Issue Type: Test > Components: camel-gson, camel-spring-boot-starters, tests >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17717) REST DSL securityRequirements cleanup
[
https://issues.apache.org/jira/browse/CAMEL-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Filotto resolved CAMEL-17717.
-
Resolution: Fixed
> REST DSL securityRequirements cleanup
> -
>
> Key: CAMEL-17717
> URL: https://issues.apache.org/jira/browse/CAMEL-17717
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Marat Gubaidullin
>Assignee: Nicolas Filotto
>Priority: Major
> Fix For: 3.16.0
>
>
> *RestDefinition* (rest.json) has *securityRequirements* property of type
> *SecurityRequirementsDefinition*
> {code:java}
> {
> "model": {
> "kind": "model",
> "name": "rest",
> "title": "Rest",
> "javaType": "org.apache.camel.model.rest.RestDefinition",
> ...
> },
> "properties": {
> ...
> "securityRequirements": { "kind": "element", "displayName": "Security
> Requirements", "label": "security", "required": false, "type": "object",
> "javaType": "org.apache.camel.model.rest.SecurityRequirementsDefinition",
> "deprecated": false, "autowired": false, "secret": false, "description":
> "Sets the security requirement(s) for all endpoints." },
> ...
> }
> {code}
> However *SecurityRequirementsDefinition* has only one property:
> *securityRequirements*
> {code:java}
> {
> "model": {
> "kind": "model",
> "name": "securityRequirements",
> "javaType": "org.apache.camel.model.rest.SecurityRequirementsDefinition",
> ...
> },
> "properties": {
> "securityRequirements": { "kind": "element", "displayName": "Security
> Requirements", "required": true, "type": "array", "javaType":
> "java.util.List", "oneOf": [
> "securityRequirement" ], "deprecated": false, "autowired": false, "secret":
> false, "description": "Security requirement configurations" }
> }
> }
> {code}
> Could we remove intermediate *SecurityRequirementsDefinition* and have
> *securityRequirements* property directly in *RestDefinition*?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17749) camel-health - Allow to enabled/disable custom health checks from camel-main configuration
[ https://issues.apache.org/jira/browse/CAMEL-17749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17749: Priority: Minor (was: Major) > camel-health - Allow to enabled/disable custom health checks from camel-main > configuration > -- > > Key: CAMEL-17749 > URL: https://issues.apache.org/jira/browse/CAMEL-17749 > Project: Camel > Issue Type: Improvement > Components: camel-main >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.16.0 > > > TODO: be able to enable|disable camel.health.camel-kafka.enabled=false via > camel-main configuration -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17749) camel-health - Allow to enabled/disable custom health checks from camel-main configuration
[ https://issues.apache.org/jira/browse/CAMEL-17749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501499#comment-17501499 ] Claus Ibsen commented on CAMEL-17749: - So you can configure this per custom health-check camel.health.camel-kafka.enabled = false For spring boot we may need a custom auto configuration that can be used. Otherwise we need to fiddle with the map config ala thread-pools, to make it generic and use the key as health check name camel.health.config[camel-kafka].enabled = false > camel-health - Allow to enabled/disable custom health checks from camel-main > configuration > -- > > Key: CAMEL-17749 > URL: https://issues.apache.org/jira/browse/CAMEL-17749 > Project: Camel > Issue Type: Improvement > Components: camel-main >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > > TODO: be able to enable|disable camel.health.camel-kafka.enabled=false via > camel-main configuration -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17749) camel-health - Allow to enabled/disable custom health checks from camel-main configuration
Claus Ibsen created CAMEL-17749: --- Summary: camel-health - Allow to enabled/disable custom health checks from camel-main configuration Key: CAMEL-17749 URL: https://issues.apache.org/jira/browse/CAMEL-17749 Project: Camel Issue Type: Improvement Components: camel-main Reporter: Claus Ibsen Fix For: 3.16.0 TODO: be able to enable|disable camel.health.camel-kafka.enabled=false via camel-main configuration -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-17727.
-
Resolution: Fixed
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
> Attachments: Screenshot 2022-03-04 at 19.00.56.png
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17727:
Attachment: Screenshot 2022-03-04 at 19.00.56.png
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
> Attachments: Screenshot 2022-03-04 at 19.00.56.png
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17748) camel-any23 - Upgrade to 2.7
Claus Ibsen created CAMEL-17748: --- Summary: camel-any23 - Upgrade to 2.7 Key: CAMEL-17748 URL: https://issues.apache.org/jira/browse/CAMEL-17748 Project: Camel Issue Type: Dependency upgrade Reporter: Claus Ibsen Fix For: 3.16.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17747) add tests in camel-cron-starter
Freeman Yue Fang created CAMEL-17747: Summary: add tests in camel-cron-starter Key: CAMEL-17747 URL: https://issues.apache.org/jira/browse/CAMEL-17747 Project: Camel Issue Type: Test Components: camel-spring-boot-starters, tests Reporter: Freeman Yue Fang Assignee: Freeman Yue Fang -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17746) add tests in camel-gson-starter
Freeman Yue Fang created CAMEL-17746: Summary: add tests in camel-gson-starter Key: CAMEL-17746 URL: https://issues.apache.org/jira/browse/CAMEL-17746 Project: Camel Issue Type: Test Components: camel-gson, camel-spring-boot-starters, tests Reporter: Freeman Yue Fang Assignee: Freeman Yue Fang -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501361#comment-17501361
]
Claus Ibsen commented on CAMEL-17727:
-
TODO: be able to enable|disable camel.health.camel-kafka.enabled=false via
camel-main configuration
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (CAMEL-17742) Camel-quartz: fix and enable SpringQuartzPersistentStoreRestartAppChangeOptionsTest
[ https://issues.apache.org/jira/browse/CAMEL-17742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17742. - Fix Version/s: 3.16.0 Resolution: Fixed > Camel-quartz: fix and enable > SpringQuartzPersistentStoreRestartAppChangeOptionsTest > --- > > Key: CAMEL-17742 > URL: https://issues.apache.org/jira/browse/CAMEL-17742 > Project: Camel > Issue Type: Test > Components: camel-quartz >Affects Versions: 3.16.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Minor > Fix For: 3.16.0 > > > Test _SpringQuartzPersistentStoreRestartAppChangeOptionsTest was disabled > with update of spring 5.3.12 to 5.3.13. Test should be fixed and enabled -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501300#comment-17501300
]
Claus Ibsen edited comment on CAMEL-17727 at 3/4/22, 2:39 PM:
--
TODO: camel-kafka health check repository that embeds the checks, then its only
1 hc from camel pov *DONE*
was (Author: davsclaus):
TODO: camel-kafka health check repository that embeds the checks, then its only
1 hc from camel pov
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17745) camel-spring-boot - AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17745: Affects Version/s: 3.16.0 > camel-spring-boot - AutoConfigurations models aren't updated > > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Affects Versions: 3.16.0 >Reporter: John Poth >Priority: Minor > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17739) Camel Google Secret Manager Properties Source: Support the usage of client default instance
[ https://issues.apache.org/jira/browse/CAMEL-17739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17739. -- Resolution: Fixed > Camel Google Secret Manager Properties Source: Support the usage of client > default instance > --- > > Key: CAMEL-17739 > URL: https://issues.apache.org/jira/browse/CAMEL-17739 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.16.0 > > > Like use default credentials providers for AWS, but in this case we'll > leverage the GOOGLE_APPLICATION_CREDENTIALS env variable, which is ugly as > hell, but it's the default. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17745) camel-spring-boot - AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17745: Fix Version/s: 3.16.0 > camel-spring-boot - AutoConfigurations models aren't updated > > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Affects Versions: 3.16.0 >Reporter: John Poth >Priority: Minor > Fix For: 3.16.0 > > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17743) camel-spring-boot - Schema generation fails for Resilience4jConfigurationCommon
[ https://issues.apache.org/jira/browse/CAMEL-17743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17743: Fix Version/s: 3.16.0 > camel-spring-boot - Schema generation fails for > Resilience4jConfigurationCommon > --- > > Key: CAMEL-17743 > URL: https://issues.apache.org/jira/browse/CAMEL-17743 > Project: Camel > Issue Type: Task > Components: camel-core >Affects Versions: 3.16.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 3.16.0 > > > SB2 schema generation fails for Resilience4jConfigurationDefinition because > the javaType is set to > [*io.github.resilience4j.circuitbreaker.CircuitBreaker*|https://github.com/apache/camel/blob/6da63c1f884faa0b7981f78c8de0c818f994804e/core/camel-core-model/src/main/java/org/apache/camel/model/Resilience4jConfigurationCommon.java#L31] > when > [generating|https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaGeneratorMojo.java#L395] > the schema while a String is expected. This also gives a > ClassNotFoundException as the type isn't present on the classpath in SB2 > starters. Removing the problematic javaTypes for now. Thanks ! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17743) camel-spring-boot - Schema generation fails for Resilience4jConfigurationCommon
[ https://issues.apache.org/jira/browse/CAMEL-17743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17743: Priority: Minor (was: Major) > camel-spring-boot - Schema generation fails for > Resilience4jConfigurationCommon > --- > > Key: CAMEL-17743 > URL: https://issues.apache.org/jira/browse/CAMEL-17743 > Project: Camel > Issue Type: Bug > Components: camel-core >Reporter: John Poth >Assignee: John Poth >Priority: Minor > > SB2 schema generation fails for Resilience4jConfigurationDefinition because > the javaType is set to > [*io.github.resilience4j.circuitbreaker.CircuitBreaker*|https://github.com/apache/camel/blob/6da63c1f884faa0b7981f78c8de0c818f994804e/core/camel-core-model/src/main/java/org/apache/camel/model/Resilience4jConfigurationCommon.java#L31] > when > [generating|https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaGeneratorMojo.java#L395] > the schema while a String is expected. This also gives a > ClassNotFoundException as the type isn't present on the classpath in SB2 > starters. Removing the problematic javaTypes for now. Thanks ! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17743) camel-spring-boot - Schema generation fails for Resilience4jConfigurationCommon
[ https://issues.apache.org/jira/browse/CAMEL-17743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17743: Affects Version/s: 3.16.0 > camel-spring-boot - Schema generation fails for > Resilience4jConfigurationCommon > --- > > Key: CAMEL-17743 > URL: https://issues.apache.org/jira/browse/CAMEL-17743 > Project: Camel > Issue Type: Task > Components: camel-core >Affects Versions: 3.16.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > > SB2 schema generation fails for Resilience4jConfigurationDefinition because > the javaType is set to > [*io.github.resilience4j.circuitbreaker.CircuitBreaker*|https://github.com/apache/camel/blob/6da63c1f884faa0b7981f78c8de0c818f994804e/core/camel-core-model/src/main/java/org/apache/camel/model/Resilience4jConfigurationCommon.java#L31] > when > [generating|https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaGeneratorMojo.java#L395] > the schema while a String is expected. This also gives a > ClassNotFoundException as the type isn't present on the classpath in SB2 > starters. Removing the problematic javaTypes for now. Thanks ! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17745) camel-spring-boot - AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17745: Summary: camel-spring-boot - AutoConfigurations models aren't updated (was: camel-core-starter AutoConfigurations models aren't updated) > camel-spring-boot - AutoConfigurations models aren't updated > > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: John Poth >Priority: Minor > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17743) camel-spring-boot - Schema generation fails for Resilience4jConfigurationCommon
[ https://issues.apache.org/jira/browse/CAMEL-17743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17743: Issue Type: Task (was: Bug) > camel-spring-boot - Schema generation fails for > Resilience4jConfigurationCommon > --- > > Key: CAMEL-17743 > URL: https://issues.apache.org/jira/browse/CAMEL-17743 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: John Poth >Assignee: John Poth >Priority: Minor > > SB2 schema generation fails for Resilience4jConfigurationDefinition because > the javaType is set to > [*io.github.resilience4j.circuitbreaker.CircuitBreaker*|https://github.com/apache/camel/blob/6da63c1f884faa0b7981f78c8de0c818f994804e/core/camel-core-model/src/main/java/org/apache/camel/model/Resilience4jConfigurationCommon.java#L31] > when > [generating|https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaGeneratorMojo.java#L395] > the schema while a String is expected. This also gives a > ClassNotFoundException as the type isn't present on the classpath in SB2 > starters. Removing the problematic javaTypes for now. Thanks ! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17743) camel-spring-boot - Schema generation fails for Resilience4jConfigurationCommon
[ https://issues.apache.org/jira/browse/CAMEL-17743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17743: Summary: camel-spring-boot - Schema generation fails for Resilience4jConfigurationCommon (was: SB2 Schema generation fails for Resilience4jConfigurationCommon) > camel-spring-boot - Schema generation fails for > Resilience4jConfigurationCommon > --- > > Key: CAMEL-17743 > URL: https://issues.apache.org/jira/browse/CAMEL-17743 > Project: Camel > Issue Type: Bug > Components: camel-core >Reporter: John Poth >Assignee: John Poth >Priority: Major > > SB2 schema generation fails for Resilience4jConfigurationDefinition because > the javaType is set to > [*io.github.resilience4j.circuitbreaker.CircuitBreaker*|https://github.com/apache/camel/blob/6da63c1f884faa0b7981f78c8de0c818f994804e/core/camel-core-model/src/main/java/org/apache/camel/model/Resilience4jConfigurationCommon.java#L31] > when > [generating|https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaGeneratorMojo.java#L395] > the schema while a String is expected. This also gives a > ClassNotFoundException as the type isn't present on the classpath in SB2 > starters. Removing the problematic javaTypes for now. Thanks ! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17745) camel-core-starter AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17745: Component/s: camel-spring-boot > camel-core-starter AutoConfigurations models aren't updated > --- > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: John Poth >Priority: Minor > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17745) camel-core-starter AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17745: Issue Type: Task (was: Bug) > camel-core-starter AutoConfigurations models aren't updated > --- > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Task >Reporter: John Poth >Priority: Major > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17742) Camel-quartz: fix and enable SpringQuartzPersistentStoreRestartAppChangeOptionsTest
[ https://issues.apache.org/jira/browse/CAMEL-17742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17742: Issue Type: Test (was: Bug) > Camel-quartz: fix and enable > SpringQuartzPersistentStoreRestartAppChangeOptionsTest > --- > > Key: CAMEL-17742 > URL: https://issues.apache.org/jira/browse/CAMEL-17742 > Project: Camel > Issue Type: Test > Components: camel-quartz >Affects Versions: 3.16.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Minor > > Test _SpringQuartzPersistentStoreRestartAppChangeOptionsTest was disabled > with update of spring 5.3.12 to 5.3.13. Test should be fixed and enabled -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17742) Camel-quartz: fix and enable SpringQuartzPersistentStoreRestartAppChangeOptionsTest
[ https://issues.apache.org/jira/browse/CAMEL-17742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17742: Priority: Minor (was: Major) > Camel-quartz: fix and enable > SpringQuartzPersistentStoreRestartAppChangeOptionsTest > --- > > Key: CAMEL-17742 > URL: https://issues.apache.org/jira/browse/CAMEL-17742 > Project: Camel > Issue Type: Bug > Components: camel-quartz >Affects Versions: 3.16.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Minor > > Test _SpringQuartzPersistentStoreRestartAppChangeOptionsTest was disabled > with update of spring 5.3.12 to 5.3.13. Test should be fixed and enabled -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17745) camel-core-starter AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17745: Priority: Minor (was: Major) > camel-core-starter AutoConfigurations models aren't updated > --- > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Task >Reporter: John Poth >Priority: Minor > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501300#comment-17501300
]
Claus Ibsen commented on CAMEL-17727:
-
TODO: camel-kafka health check repository that embeds the checks, then its only
1 hc from camel pov
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17745) camel-core-starter AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501287#comment-17501287 ] John Poth commented on CAMEL-17745: --- https://github.com/apache/camel-spring-boot/pull/454 > camel-core-starter AutoConfigurations models aren't updated > --- > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Bug >Reporter: John Poth >Priority: Major > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17743) SB2 Schema generation fails for Resilience4jConfigurationCommon
[ https://issues.apache.org/jira/browse/CAMEL-17743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501288#comment-17501288 ] John Poth commented on CAMEL-17743: --- https://github.com/apache/camel/pull/7107 > SB2 Schema generation fails for Resilience4jConfigurationCommon > --- > > Key: CAMEL-17743 > URL: https://issues.apache.org/jira/browse/CAMEL-17743 > Project: Camel > Issue Type: Bug > Components: camel-core >Reporter: John Poth >Assignee: John Poth >Priority: Major > > SB2 schema generation fails for Resilience4jConfigurationDefinition because > the javaType is set to > [*io.github.resilience4j.circuitbreaker.CircuitBreaker*|https://github.com/apache/camel/blob/6da63c1f884faa0b7981f78c8de0c818f994804e/core/camel-core-model/src/main/java/org/apache/camel/model/Resilience4jConfigurationCommon.java#L31] > when > [generating|https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaGeneratorMojo.java#L395] > the schema while a String is expected. This also gives a > ClassNotFoundException as the type isn't present on the classpath in SB2 > starters. Removing the problematic javaTypes for now. Thanks ! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17745) camel-core-starter AutoConfigurations models aren't updated
John Poth created CAMEL-17745: - Summary: camel-core-starter AutoConfigurations models aren't updated Key: CAMEL-17745 URL: https://issues.apache.org/jira/browse/CAMEL-17745 Project: Camel Issue Type: Bug Reporter: John Poth I think this relates to [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be worth creating a "real" camel-core-starter and a new camel-core-engine-starter. Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17741) camel-yaml-dsl - Improper way to get the default name of a field annotated with XmlElement
[
https://issues.apache.org/jira/browse/CAMEL-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Filotto resolved CAMEL-17741.
-
Resolution: Fixed
> camel-yaml-dsl - Improper way to get the default name of a field annotated
> with XmlElement
> ---
>
> Key: CAMEL-17741
> URL: https://issues.apache.org/jira/browse/CAMEL-17741
> Project: Camel
> Issue Type: Task
> Components: camel-yaml-dsl
>Reporter: Nicolas Filotto
>Assignee: Nicolas Filotto
>Priority: Minor
> Fix For: 3.16.0
>
>
> It appears that the plugin *camel-yaml-dsl-maven-plugin* doesn't retrieve the
> default name of a property as the JAXB specification states.
> Indeed, I have the next mapping:
> {code:java}
> @XmlElement
> @Metadata(label = "security")
> private List securityRequirements = new
> ArrayList<>();{code}
> According the JAXB specification, if a field is annotated with the annotation
> {_}XmlElement{_}, its name should be retrieved from the attribute "name" if
> set otherwise it should use the field name.
> With the current code, I end up with "{_}security{_}" corresponding to the
> value of the attribute "{_}name{_}" of the annotation _XmlRootElement_ on the
> class _SecurityDefinition_ as you can see below:
> {code:java}
> @Metadata(label = "rest,security,configuration", title = "Rest Security")
> @XmlRootElement(name = "security")
> @XmlAccessorType(XmlAccessType.FIELD)
> public class SecurityDefinition {{code}
> According to the specification, this behavior is actually only expected with
> a field annotated with {_}XmlElementRef{_}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17744) SB actuator-http-metrics example fails
[
https://issues.apache.org/jira/browse/CAMEL-17744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501282#comment-17501282
]
John Poth commented on CAMEL-17744:
---
Resolved with
https://github.com/apache/camel-spring-boot/commit/07b410a73855b4ecced4de2bb675466bd53ec5d2
> SB actuator-http-metrics example fails
> --
>
> Key: CAMEL-17744
> URL: https://issues.apache.org/jira/browse/CAMEL-17744
> Project: Camel
> Issue Type: Bug
> Components: examples
>Reporter: John Poth
>Assignee: John Poth
>Priority: Major
>
> Running the example from scratch gives:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Cannot configure option
> [apiContextListing] with value [false] as the bean class
> [org.apache.camel.spi.RestConfiguration] has no suitable setter method, or
> not possible to lookup a bean with the id [false] in Spring Boot registry
> at
> org.apache.camel.spring.boot.util.CamelPropertiesHelper.setCamelProperties(CamelPropertiesHelper.java:125)
> ~[camel-spring-boot-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
> at
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration.configureRestConfigurationDefinition(RestConfigurationDefinitionAutoConfiguration.java:72)
> ~[camel-core-starter-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[na:na]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:na]
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:na]
> at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
> at
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
> ~[spring-beans-5.3.16.jar:5.3.16]
> ... 37 common frames omitted
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (CAMEL-17744) SB actuator-http-metrics example fails
[
https://issues.apache.org/jira/browse/CAMEL-17744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Poth resolved CAMEL-17744.
---
Resolution: Fixed
> SB actuator-http-metrics example fails
> --
>
> Key: CAMEL-17744
> URL: https://issues.apache.org/jira/browse/CAMEL-17744
> Project: Camel
> Issue Type: Bug
> Components: examples
>Reporter: John Poth
>Assignee: John Poth
>Priority: Major
>
> Running the example from scratch gives:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Cannot configure option
> [apiContextListing] with value [false] as the bean class
> [org.apache.camel.spi.RestConfiguration] has no suitable setter method, or
> not possible to lookup a bean with the id [false] in Spring Boot registry
> at
> org.apache.camel.spring.boot.util.CamelPropertiesHelper.setCamelProperties(CamelPropertiesHelper.java:125)
> ~[camel-spring-boot-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
> at
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration.configureRestConfigurationDefinition(RestConfigurationDefinitionAutoConfiguration.java:72)
> ~[camel-core-starter-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[na:na]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:na]
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:na]
> at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
> at
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
> ~[spring-beans-5.3.16.jar:5.3.16]
> ... 37 common frames omitted
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17744) SB actuator-http-metrics example fails
John Poth created CAMEL-17744:
-
Summary: SB actuator-http-metrics example fails
Key: CAMEL-17744
URL: https://issues.apache.org/jira/browse/CAMEL-17744
Project: Camel
Issue Type: Bug
Components: examples
Reporter: John Poth
Assignee: John Poth
Running the example from scratch gives:
{code:java}
Caused by: java.lang.IllegalArgumentException: Cannot configure option
[apiContextListing] with value [false] as the bean class
[org.apache.camel.spi.RestConfiguration] has no suitable setter method, or not
possible to lookup a bean with the id [false] in Spring Boot registry
at
org.apache.camel.spring.boot.util.CamelPropertiesHelper.setCamelProperties(CamelPropertiesHelper.java:125)
~[camel-spring-boot-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
at
org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration.configureRestConfigurationDefinition(RestConfigurationDefinitionAutoConfiguration.java:72)
~[camel-core-starter-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[na:na]
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[na:na]
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[na:na]
at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
at
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
~[spring-beans-5.3.16.jar:5.3.16]
... 37 common frames omitted
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501277#comment-17501277
]
Claus Ibsen commented on CAMEL-17727:
-
TODO: should we have an option to turn off these? wonder if anyone want to have
camel health check and then not these when using camel-kafka?
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501231#comment-17501231
]
Claus Ibsen edited comment on CAMEL-17727 at 3/4/22, 11:19 AM:
---
TODO: consumer readiness check *DONE*
TODO: producer readiness check *DONE*
was (Author: davsclaus):
TODO: consumer readiness check *DONE*
TODO: producer readiness check
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500689#comment-17500689
]
Claus Ibsen edited comment on CAMEL-17727 at 3/4/22, 11:19 AM:
---
TODO: The client.id is null in DOWN detail *DONE*
TODO: failure counter should INC for every consequitive failures *DONE*
TODO: success counter should INC for every UP calls *DONE*
was (Author: davsclaus):
TODO: The client.id is null in DOWN detail *CANNOT* (kafka client hides this
information and its not possible to get it ... argh)
TODO: failure counter should INC for every consequitive failures *DONE*
TODO: success counter should INC for every UP calls *DONE*
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17743) SB2 Schema generation fails for Resilience4jConfigurationCommon
John Poth created CAMEL-17743: - Summary: SB2 Schema generation fails for Resilience4jConfigurationCommon Key: CAMEL-17743 URL: https://issues.apache.org/jira/browse/CAMEL-17743 Project: Camel Issue Type: Bug Components: camel-core Reporter: John Poth Assignee: John Poth SB2 schema generation fails for Resilience4jConfigurationDefinition because the javaType is set to [*io.github.resilience4j.circuitbreaker.CircuitBreaker*|https://github.com/apache/camel/blob/6da63c1f884faa0b7981f78c8de0c818f994804e/core/camel-core-model/src/main/java/org/apache/camel/model/Resilience4jConfigurationCommon.java#L31] when [generating|https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaGeneratorMojo.java#L395] the schema while a String is expected. This also gives a ClassNotFoundException as the type isn't present on the classpath in SB2 starters. Removing the problematic javaTypes for now. Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17742) Camel-quartz: fix and enable SpringQuartzPersistentStoreRestartAppChangeOptionsTest
Jiri Ondrusek created CAMEL-17742: - Summary: Camel-quartz: fix and enable SpringQuartzPersistentStoreRestartAppChangeOptionsTest Key: CAMEL-17742 URL: https://issues.apache.org/jira/browse/CAMEL-17742 Project: Camel Issue Type: Bug Components: camel-quartz Affects Versions: 3.16.0 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek Test _SpringQuartzPersistentStoreRestartAppChangeOptionsTest was disabled with update of spring 5.3.12 to 5.3.13. Test should be fixed and enabled -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501231#comment-17501231
]
Claus Ibsen commented on CAMEL-17727:
-
TODO: producer readiness check
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501231#comment-17501231
]
Claus Ibsen edited comment on CAMEL-17727 at 3/4/22, 9:28 AM:
--
TODO: consumer readiness check *DONE*
TODO: producer readiness check
was (Author: davsclaus):
TODO: producer readiness check
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500689#comment-17500689
]
Claus Ibsen edited comment on CAMEL-17727 at 3/4/22, 9:28 AM:
--
TODO: The client.id is null in DOWN detail *CANNOT* (kafka client hides this
information and its not possible to get it ... argh)
TODO: failure counter should INC for every consequitive failures *DONE*
TODO: success counter should INC for every UP calls *DONE*
was (Author: davsclaus):
TODO: The client.id is null in DOWN detail *CANNOT* (kafka client hides this
information and its not possible to get it ... argh)
TODO: failure counter should INC for every consequitive failures
TODO: success counter should INC for every UP calls
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500689#comment-17500689
]
Claus Ibsen edited comment on CAMEL-17727 at 3/4/22, 9:18 AM:
--
TODO: The client.id is null in DOWN detail *CANNOT* (kafka client hides this
information and its not possible to get it ... argh)
TODO: failure counter should INC for every consequitive failures
TODO: success counter should INC for every UP calls
was (Author: davsclaus):
TODO: The client.id is null in DOWN detail
TODO: failure counter should INC for every consequitive failures
TODO: success counter should INC for every UP calls
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17727) camel-kafka: add producer/consumer readiness checks
[
https://issues.apache.org/jira/browse/CAMEL-17727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17727:
Priority: Major (was: Minor)
> camel-kafka: add producer/consumer readiness checks
> ---
>
> Key: CAMEL-17727
> URL: https://issues.apache.org/jira/browse/CAMEL-17727
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> When a kafka broker is not reachable, the kafka client automatically tries to
> re-connect, as example:
> {code}
> 2022-02-24 18:12:32,880 WARN [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[test]) [Consumer
> clientId=consumer-c8b8rsv13hohlh07kbv0-1, groupId=c8b8rsv13hohlh07kbv0] Error
> connecting to node foo.bar:443 (id: 1 rack: us-east-1b):
> java.net.UnknownHostException: foo.bar:: Name or service not known
> {code}
> It would be nice if we have a consumer/producer readiness checks that can
> mark the application as not ready when the client is not connected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17741) camel-yaml-dsl - Improper way to get the default name of a field annotated with XmlElement
[
https://issues.apache.org/jira/browse/CAMEL-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17741:
Priority: Minor (was: Major)
> camel-yaml-dsl - Improper way to get the default name of a field annotated
> with XmlElement
> ---
>
> Key: CAMEL-17741
> URL: https://issues.apache.org/jira/browse/CAMEL-17741
> Project: Camel
> Issue Type: Task
> Components: camel-yaml-dsl
>Reporter: Nicolas Filotto
>Assignee: Nicolas Filotto
>Priority: Minor
> Fix For: 3.16.0
>
>
> It appears that the plugin *camel-yaml-dsl-maven-plugin* doesn't retrieve the
> default name of a property as the JAXB specification states.
> Indeed, I have the next mapping:
> {code:java}
> @XmlElement
> @Metadata(label = "security")
> private List securityRequirements = new
> ArrayList<>();{code}
> According the JAXB specification, if a field is annotated with the annotation
> {_}XmlElement{_}, its name should be retrieved from the attribute "name" if
> set otherwise it should use the field name.
> With the current code, I end up with "{_}security{_}" corresponding to the
> value of the attribute "{_}name{_}" of the annotation _XmlRootElement_ on the
> class _SecurityDefinition_ as you can see below:
> {code:java}
> @Metadata(label = "rest,security,configuration", title = "Rest Security")
> @XmlRootElement(name = "security")
> @XmlAccessorType(XmlAccessType.FIELD)
> public class SecurityDefinition {{code}
> According to the specification, this behavior is actually only expected with
> a field annotated with {_}XmlElementRef{_}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17741) camel-yaml-dsl - Improper way to get the default name of a field annotated with XmlElement
[
https://issues.apache.org/jira/browse/CAMEL-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17741:
Issue Type: Task (was: Bug)
> camel-yaml-dsl - Improper way to get the default name of a field annotated
> with XmlElement
> ---
>
> Key: CAMEL-17741
> URL: https://issues.apache.org/jira/browse/CAMEL-17741
> Project: Camel
> Issue Type: Task
> Components: camel-yaml-dsl
>Reporter: Nicolas Filotto
>Assignee: Nicolas Filotto
>Priority: Major
> Fix For: 3.16.0
>
>
> It appears that the plugin *camel-yaml-dsl-maven-plugin* doesn't retrieve the
> default name of a property as the JAXB specification states.
> Indeed, I have the next mapping:
> {code:java}
> @XmlElement
> @Metadata(label = "security")
> private List securityRequirements = new
> ArrayList<>();{code}
> According the JAXB specification, if a field is annotated with the annotation
> {_}XmlElement{_}, its name should be retrieved from the attribute "name" if
> set otherwise it should use the field name.
> With the current code, I end up with "{_}security{_}" corresponding to the
> value of the attribute "{_}name{_}" of the annotation _XmlRootElement_ on the
> class _SecurityDefinition_ as you can see below:
> {code:java}
> @Metadata(label = "rest,security,configuration", title = "Rest Security")
> @XmlRootElement(name = "security")
> @XmlAccessorType(XmlAccessType.FIELD)
> public class SecurityDefinition {{code}
> According to the specification, this behavior is actually only expected with
> a field annotated with {_}XmlElementRef{_}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17717) REST DSL securityRequirements cleanup
[
https://issues.apache.org/jira/browse/CAMEL-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501223#comment-17501223
]
Nicolas Filotto commented on CAMEL-17717:
-
The corresponding PR https://github.com/apache/camel/pull/7105
> REST DSL securityRequirements cleanup
> -
>
> Key: CAMEL-17717
> URL: https://issues.apache.org/jira/browse/CAMEL-17717
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Marat Gubaidullin
>Assignee: Nicolas Filotto
>Priority: Major
> Fix For: 3.16.0
>
>
> *RestDefinition* (rest.json) has *securityRequirements* property of type
> *SecurityRequirementsDefinition*
> {code:java}
> {
> "model": {
> "kind": "model",
> "name": "rest",
> "title": "Rest",
> "javaType": "org.apache.camel.model.rest.RestDefinition",
> ...
> },
> "properties": {
> ...
> "securityRequirements": { "kind": "element", "displayName": "Security
> Requirements", "label": "security", "required": false, "type": "object",
> "javaType": "org.apache.camel.model.rest.SecurityRequirementsDefinition",
> "deprecated": false, "autowired": false, "secret": false, "description":
> "Sets the security requirement(s) for all endpoints." },
> ...
> }
> {code}
> However *SecurityRequirementsDefinition* has only one property:
> *securityRequirements*
> {code:java}
> {
> "model": {
> "kind": "model",
> "name": "securityRequirements",
> "javaType": "org.apache.camel.model.rest.SecurityRequirementsDefinition",
> ...
> },
> "properties": {
> "securityRequirements": { "kind": "element", "displayName": "Security
> Requirements", "required": true, "type": "array", "javaType":
> "java.util.List", "oneOf": [
> "securityRequirement" ], "deprecated": false, "autowired": false, "secret":
> false, "description": "Security requirement configurations" }
> }
> }
> {code}
> Could we remove intermediate *SecurityRequirementsDefinition* and have
> *securityRequirements* property directly in *RestDefinition*?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17741) camel-yaml-dsl - Improper way to get the default name of a field annotated with XmlElement
[
https://issues.apache.org/jira/browse/CAMEL-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501218#comment-17501218
]
Nicolas Filotto commented on CAMEL-17741:
-
The corresponding PR https://github.com/apache/camel/pull/7104
> camel-yaml-dsl - Improper way to get the default name of a field annotated
> with XmlElement
> ---
>
> Key: CAMEL-17741
> URL: https://issues.apache.org/jira/browse/CAMEL-17741
> Project: Camel
> Issue Type: Bug
> Components: camel-yaml-dsl
>Reporter: Nicolas Filotto
>Assignee: Nicolas Filotto
>Priority: Major
> Fix For: 3.16.0
>
>
> It appears that the plugin *camel-yaml-dsl-maven-plugin* doesn't retrieve the
> default name of a property as the JAXB specification states.
> Indeed, I have the next mapping:
> {code:java}
> @XmlElement
> @Metadata(label = "security")
> private List securityRequirements = new
> ArrayList<>();{code}
> According the JAXB specification, if a field is annotated with the annotation
> {_}XmlElement{_}, its name should be retrieved from the attribute "name" if
> set otherwise it should use the field name.
> With the current code, I end up with "{_}security{_}" corresponding to the
> value of the attribute "{_}name{_}" of the annotation _XmlRootElement_ on the
> class _SecurityDefinition_ as you can see below:
> {code:java}
> @Metadata(label = "rest,security,configuration", title = "Rest Security")
> @XmlRootElement(name = "security")
> @XmlAccessorType(XmlAccessType.FIELD)
> public class SecurityDefinition {{code}
> According to the specification, this behavior is actually only expected with
> a field annotated with {_}XmlElementRef{_}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17609) camel-core - Problem with transacted routes
[
https://issues.apache.org/jira/browse/CAMEL-17609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Cassimon updated CAMEL-17609:
-
Fix Version/s: 3.16.0
> camel-core - Problem with transacted routes
> ---
>
> Key: CAMEL-17609
> URL: https://issues.apache.org/jira/browse/CAMEL-17609
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.14.1
>Reporter: Tom Cassimon
>Priority: Major
> Fix For: 3.14.2, 3.16.0
>
>
> I'm working on an update of the camel library version used to the latest LTS
> release (3.14.1), but it seems to have broken my tests that are using
> transacted.
> I have a simple test route which reads in a file, parses the content using
> bindy and sending the validated parts to a jms queue.
> {code:java}
> from("inputFile:///temp/testing/input2/")
> .autoStartup(true)
> .transacted()
> .unmarshal(format)
> .split(body())
> .to("bean-validator:x")
> .to("direct:sendMessage2")
> .end()
> .end();
> from("direct:sendMessage2")
> .convertBodyTo(String.class)
> .to("jms://be.test.output")
> .end(); {code}
> If one of the parts of the file doesn't pass the validation rules, the test
> expects to find no messages on the queue.
> This used to work in camel-3.7.x, but now in camel 3.14.1 messages do appear
> on the queue, even when parts of the file failed the validation.
> In the migration guide of 3.12 -> 3.13 is an entry about transactions, but it
> is not clear to me if this is related.
> Upon further investigation the split() seems to cause the issue with the
> transactionality, if i put 2 posts to jms inline in the route and throw an
> exception before the second post the result is no messages on the queue.
> Do i have to add something to the split to allow the transaction to propagate?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (CAMEL-17609) camel-core - Problem with transacted routes
[
https://issues.apache.org/jira/browse/CAMEL-17609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Cassimon resolved CAMEL-17609.
--
Fix Version/s: 3.14.2
Resolution: Fixed
> camel-core - Problem with transacted routes
> ---
>
> Key: CAMEL-17609
> URL: https://issues.apache.org/jira/browse/CAMEL-17609
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.14.1
>Reporter: Tom Cassimon
>Priority: Major
> Fix For: 3.14.2
>
>
> I'm working on an update of the camel library version used to the latest LTS
> release (3.14.1), but it seems to have broken my tests that are using
> transacted.
> I have a simple test route which reads in a file, parses the content using
> bindy and sending the validated parts to a jms queue.
> {code:java}
> from("inputFile:///temp/testing/input2/")
> .autoStartup(true)
> .transacted()
> .unmarshal(format)
> .split(body())
> .to("bean-validator:x")
> .to("direct:sendMessage2")
> .end()
> .end();
> from("direct:sendMessage2")
> .convertBodyTo(String.class)
> .to("jms://be.test.output")
> .end(); {code}
> If one of the parts of the file doesn't pass the validation rules, the test
> expects to find no messages on the queue.
> This used to work in camel-3.7.x, but now in camel 3.14.1 messages do appear
> on the queue, even when parts of the file failed the validation.
> In the migration guide of 3.12 -> 3.13 is an entry about transactions, but it
> is not clear to me if this is related.
> Upon further investigation the split() seems to cause the issue with the
> transactionality, if i put 2 posts to jms inline in the route and throw an
> exception before the second post the result is no messages on the queue.
> Do i have to add something to the split to allow the transaction to propagate?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17609) camel-core - Problem with transacted routes
[
https://issues.apache.org/jira/browse/CAMEL-17609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501217#comment-17501217
]
Tom Cassimon commented on CAMEL-17609:
--
Fixed with CAMEL-17474
> camel-core - Problem with transacted routes
> ---
>
> Key: CAMEL-17609
> URL: https://issues.apache.org/jira/browse/CAMEL-17609
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.14.1
>Reporter: Tom Cassimon
>Priority: Major
>
> I'm working on an update of the camel library version used to the latest LTS
> release (3.14.1), but it seems to have broken my tests that are using
> transacted.
> I have a simple test route which reads in a file, parses the content using
> bindy and sending the validated parts to a jms queue.
> {code:java}
> from("inputFile:///temp/testing/input2/")
> .autoStartup(true)
> .transacted()
> .unmarshal(format)
> .split(body())
> .to("bean-validator:x")
> .to("direct:sendMessage2")
> .end()
> .end();
> from("direct:sendMessage2")
> .convertBodyTo(String.class)
> .to("jms://be.test.output")
> .end(); {code}
> If one of the parts of the file doesn't pass the validation rules, the test
> expects to find no messages on the queue.
> This used to work in camel-3.7.x, but now in camel 3.14.1 messages do appear
> on the queue, even when parts of the file failed the validation.
> In the migration guide of 3.12 -> 3.13 is an entry about transactions, but it
> is not clear to me if this is related.
> Upon further investigation the split() seems to cause the issue with the
> transactionality, if i put 2 posts to jms inline in the route and throw an
> exception before the second post the result is no messages on the queue.
> Do i have to add something to the split to allow the transaction to propagate?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17741) camel-yaml-dsl - Improper way to get the default name of a field annotated with XmlElement
[
https://issues.apache.org/jira/browse/CAMEL-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Filotto updated CAMEL-17741:
Summary: camel-yaml-dsl - Improper way to get the default name of a field
annotated with XmlElement (was: camel-yaml-dsl - Improper way to get the
default name of a field annotated XmlElement with )
> camel-yaml-dsl - Improper way to get the default name of a field annotated
> with XmlElement
> ---
>
> Key: CAMEL-17741
> URL: https://issues.apache.org/jira/browse/CAMEL-17741
> Project: Camel
> Issue Type: Bug
> Components: camel-yaml-dsl
>Reporter: Nicolas Filotto
>Assignee: Nicolas Filotto
>Priority: Major
> Fix For: 3.16.0
>
>
> It appears that the plugin *camel-yaml-dsl-maven-plugin* doesn't retrieve the
> default name of a property as the JAXB specification states.
> Indeed, I have the next mapping:
> {code:java}
> @XmlElement
> @Metadata(label = "security")
> private List securityRequirements = new
> ArrayList<>();{code}
> According the JAXB specification, if a field is annotated with the annotation
> {_}XmlElement{_}, its name should be retrieved from the attribute "name" if
> set otherwise it should use the field name.
> With the current code, I end up with "{_}security{_}" corresponding to the
> value of the attribute "{_}name{_}" of the annotation _XmlRootElement_ on the
> class _SecurityDefinition_ as you can see below:
> {code:java}
> @Metadata(label = "rest,security,configuration", title = "Rest Security")
> @XmlRootElement(name = "security")
> @XmlAccessorType(XmlAccessType.FIELD)
> public class SecurityDefinition {{code}
> According to the specification, this behavior is actually only expected with
> a field annotated with {_}XmlElementRef{_}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (CAMEL-17741) camel-yaml-dsl - Improper way to get the default name of a field annotated XmlElement with
[
https://issues.apache.org/jira/browse/CAMEL-17741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Filotto reassigned CAMEL-17741:
---
Assignee: Nicolas Filotto
> camel-yaml-dsl - Improper way to get the default name of a field annotated
> XmlElement with
> ---
>
> Key: CAMEL-17741
> URL: https://issues.apache.org/jira/browse/CAMEL-17741
> Project: Camel
> Issue Type: Bug
> Components: camel-yaml-dsl
>Reporter: Nicolas Filotto
>Assignee: Nicolas Filotto
>Priority: Major
> Fix For: 3.16.0
>
>
> It appears that the plugin *camel-yaml-dsl-maven-plugin* doesn't retrieve the
> default name of a property as the JAXB specification states.
> Indeed, I have the next mapping:
> {code:java}
> @XmlElement
> @Metadata(label = "security")
> private List securityRequirements = new
> ArrayList<>();{code}
> According the JAXB specification, if a field is annotated with the annotation
> {_}XmlElement{_}, its name should be retrieved from the attribute "name" if
> set otherwise it should use the field name.
> With the current code, I end up with "{_}security{_}" corresponding to the
> value of the attribute "{_}name{_}" of the annotation _XmlRootElement_ on the
> class _SecurityDefinition_ as you can see below:
> {code:java}
> @Metadata(label = "rest,security,configuration", title = "Rest Security")
> @XmlRootElement(name = "security")
> @XmlAccessorType(XmlAccessType.FIELD)
> public class SecurityDefinition {{code}
> According to the specification, this behavior is actually only expected with
> a field annotated with {_}XmlElementRef{_}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17741) camel-yaml-dsl - Improper way to get the default name of a field annotated XmlElement with
Nicolas Filotto created CAMEL-17741:
---
Summary: camel-yaml-dsl - Improper way to get the default name of
a field annotated XmlElement with
Key: CAMEL-17741
URL: https://issues.apache.org/jira/browse/CAMEL-17741
Project: Camel
Issue Type: Bug
Components: camel-yaml-dsl
Reporter: Nicolas Filotto
Fix For: 3.16.0
It appears that the plugin *camel-yaml-dsl-maven-plugin* doesn't retrieve the
default name of a property as the JAXB specification states.
Indeed, I have the next mapping:
{code:java}
@XmlElement
@Metadata(label = "security")
private List securityRequirements = new ArrayList<>();{code}
According the JAXB specification, if a field is annotated with the annotation
{_}XmlElement{_}, its name should be retrieved from the attribute "name" if set
otherwise it should use the field name.
With the current code, I end up with "{_}security{_}" corresponding to the
value of the attribute "{_}name{_}" of the annotation _XmlRootElement_ on the
class _SecurityDefinition_ as you can see below:
{code:java}
@Metadata(label = "rest,security,configuration", title = "Rest Security")
@XmlRootElement(name = "security")
@XmlAccessorType(XmlAccessType.FIELD)
public class SecurityDefinition {{code}
According to the specification, this behavior is actually only expected with a
field annotated with {_}XmlElementRef{_}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
