[jira] [Created] (CAMEL-16788) Local parameters get overridden by environment variable
Nicola Ferraro created CAMEL-16788: -- Summary: Local parameters get overridden by environment variable Key: CAMEL-16788 URL: https://issues.apache.org/jira/browse/CAMEL-16788 Project: Camel Issue Type: Bug Components: camel-kamelet Reporter: Nicola Ferraro Fix For: 3.12.0 When a Kamelet declares a parameter like "namespace" or "port", then the value assigned to that parameter via properties is ignored if there's a "NAMESPACE" or "PORT" environment variable set on the host. That strategy may work well for global parameters, but scoped parameters should prioritize the local configuration if present. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16615) Create Jackson based dataformats for Avro and Protobuf
Nicola Ferraro created CAMEL-16615: -- Summary: Create Jackson based dataformats for Avro and Protobuf Key: CAMEL-16615 URL: https://issues.apache.org/jira/browse/CAMEL-16615 Project: Camel Issue Type: New Feature Reporter: Nicola Ferraro Assignee: Nicola Ferraro Fix For: 3.10.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16604) camel-kamelet - YAML DSL: Specify an option as optional results in a mandatory option
[
https://issues.apache.org/jira/browse/CAMEL-16604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342587#comment-17342587
]
Nicola Ferraro commented on CAMEL-16604:
I think all parameters are optional unless they're present in the "required"
list, at least, that's the semantic...
There may be something in the operator/runtime that breaks with empty values.
Did you check if the issue happens on KameletBinding or also in standard routes
(i.e. using kamelets as from("kamelet:xx")).
> camel-kamelet - YAML DSL: Specify an option as optional results in a
> mandatory option
> -
>
> Key: CAMEL-16604
> URL: https://issues.apache.org/jira/browse/CAMEL-16604
> Project: Camel
> Issue Type: Bug
> Components: camel-kamelet
>Reporter: Andrea Cosentino
>Priority: Major
> Fix For: 3.10.0
>
>
> If you have something like:
> {code:java}
> apiVersion: camel.apache.org/v1alpha1
> kind: Kamelet
> metadata:
> name: kafka-not-secured-source
> annotations:
> camel.apache.org/kamelet.icon:
> "data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MDAgNTAwOyIgeG1sOnNwYWNlPSJwcmVzZXJ2ZSI+DQo8ZyBpZD0iWE1MSURfMV8iPg0KCTxwYXRoIGlkPSJYTUxJRF85XyIgZD0iTTMxNC44LDI2OS43Yy0xNC4yLDAtMjcsNi4zLTM1LjcsMTYuMkwyNTYuOCwyNzBjMi40LTYuNSwzLjctMTMuNiwzLjctMjAuOWMwLTcuMi0xLjMtMTQuMS0zLjYtMjAuNg0KCQlsMjIuMy0xNS43YzguNyw5LjksMjEuNCwxNi4xLDM1LjYsMTYuMWMyNi4yLDAsNDcuNi0yMS4zLDQ3LjYtNDcuNnMtMjEuMy00Ny42LTQ3LjYtNDcuNnMtNDcuNiwyMS4zLTQ3LjYsNDcuNg0KCQljMCw0LjcsMC43LDkuMiwyLDEzLjVsLTIyLjMsMTUuN2MtOS4zLTExLjYtMjIuOC0xOS42LTM4LjEtMjIuMXYtMjYuOWMyMS42LTQuNSwzNy44LTIzLjcsMzcuOC00Ni42YzAtMjYuMi0yMS4zLTQ3LjYtNDcuNi00Ny42DQoJCWMtMjYuMiwwLTQ3LjYsMjEuMy00Ny42LDQ3LjZjMCwyMi42LDE1LjgsNDEuNSwzNi45LDQ2LjN2MjcuM2MtMjguOCw1LjEtNTAuOCwzMC4yLTUwLjgsNjAuNWMwLDMwLjQsMjIuMiw1NS43LDUxLjIsNjAuNXYyOC44DQoJCWMtMjEuMyw0LjctMzcuNCwyMy43LTM3LjQsNDYuNGMwLDI2LjIsMjEuMyw0Ny42LDQ3LjYsNDcuNmMyNi4yLDAsNDcuNi0yMS4zLDQ3LjYtNDcuNmMwLTIyLjctMTYtNDEuOC0zNy40LTQ2LjR2LTI4LjgNCgkJYzE1LTIuNSwyOC4yLTEwLjQsMzcuNC0yMS44bDIyLjUsMTUuOWMtMS4yLDQuMy0xLjksOC43LTEuOSwxMy40YzAsMjYuMiwyMS4zLDQ3LjYsNDcuNiw0Ny42czQ3LjYtMjEuMyw0Ny42LTQ3LjYNCgkJQzM2Mi40LDI5MSwzNDEuMSwyNjkuNywzMTQuOCwyNjkuN3ogTTMxNC44LDE1OC40YzEyLjcsMCwyMy4xLDEwLjQsMjMuMSwyMy4xYzAsMTIuNy0xMC4zLDIzLjEtMjMuMSwyMy4xcy0yMy4xLTEwLjQtMjMuMS0yMy4xDQoJCUMyOTEuOCwxNjguOCwzMDIuMSwxNTguNCwzMTQuOCwxNTguNHogTTE3NiwxMTUuMWMwLTEyLjcsMTAuMy0yMy4xLDIzLjEtMjMuMWMxMi43LDAsMjMuMSwxMC40LDIzLjEsMjMuMQ0KCQljMCwxMi43LTEwLjMsMjMuMS0yMy4xLDIzLjFDMTg2LjMsMTM4LjIsMTc2LDEyNy44LDE3NiwxMTUuMXogTTIyMi4xLDM4NC45YzAsMTIuNy0xMC4zLDIzLjEtMjMuMSwyMy4xDQoJCWMtMTIuNywwLTIzLjEtMTAuNC0yMy4xLTIzLjFjMC0xMi43LDEwLjMtMjMuMSwyMy4xLTIzLjFDMjExLjgsMzYxLjgsMjIyLjEsMzcyLjIsMjIyLjEsMzg0Ljl6IE0xOTkuMSwyODEuMw0KCQljLTE3LjcsMC0zMi4yLTE0LjQtMzIuMi0zMi4yYzAtMTcuNywxNC40LTMyLjIsMzIuMi0zMi4yYzE3LjcsMCwzMi4yLDE0LjQsMzIuMiwzMi4yQzIzMS4yLDI2Ni45LDIxNi44LDI4MS4zLDE5OS4xLDI4MS4zeg0KCQkgTTMxNC44LDM0MC4zYy0xMi43LDAtMjMuMS0xMC40LTIzLjEtMjMuMWMwLTEyLjcsMTAuMy0yMy4xLDIzLjEtMjMuMXMyMy4xLDEwLjQsMjMuMSwyMy4xQzMzNy45LDMzMCwzMjcuNSwzNDAuMywzMTQuOCwzNDAuM3oiLz4NCjwvZz4NCjwvc3ZnPg0K"
> camel.apache.org/provider: "Apache Software Foundation"
> camel.apache.org/kamelet.group: "Kafka"
> labels:
> camel.apache.org/kamelet.type: "source"
> spec:
> definition:
> title: "Kafka Not Secured Source"
> description: |-
> Receive data from Kafka topics on an insecure broker.
> required:
> - topic
> - brokers
> type: object
> properties:
> topic:
> title: Topic Names
> description: Comma separated list of Kafka topic names
> type: string
> brokers:
> title: Brokers
> description: Comma separated list of Kafka Broker URLs
> type: string
> autoCommitEnable:
> title: Auto Commit Enable
> description: If true, periodically commit to ZooKeeper the offset of
> messages already fetched by the consumer
> type: boolean
> default: true
> x-descriptors:
> - 'urn:alm:descriptor:com.tectonic.ui:checkbox'
> allowManualCommit:
> title: Allow Manual Commit
> description: Whether to allow doing manual commits
> type: boolean
> default: false
> x-descriptors:
> - 'urn:alm:descriptor:com.tectonic.ui:checkbox'
> pollOnError:
> title: Poll On Error Behavior
> description: What to do if kafka threw an exception while polling for new
> messages. There are 5 enums and the value can be one of DISCARD,
> ERROR_HANDLER, RECONNECT, RETRY, STOP
> type: string
>
[jira] [Updated] (CAMEL-16490) YAML DSL tod is no longer recognized (requires to-d)
[
https://issues.apache.org/jira/browse/CAMEL-16490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro updated CAMEL-16490:
---
Description:
It was "tod" prior to 3.9, while not it's only recognized as "to-d". We may set
an alias.
Was working:
{code:java}
# camel-k: language=yaml dependency=camel-log
- from:
uri: "timer:yaml"
parameters:
period: "1000"
steps:
- tod: "log:info"
{code}
was:It was "tod" prior to 3.9, while not it's only recognized as "to-d". We
may set an alias.
> YAML DSL tod is no longer recognized (requires to-d)
>
>
> Key: CAMEL-16490
> URL: https://issues.apache.org/jira/browse/CAMEL-16490
> Project: Camel
> Issue Type: Bug
> Components: camel-yaml-dsl
>Affects Versions: 3.9.0
>Reporter: Nicola Ferraro
>Priority: Major
>
> It was "tod" prior to 3.9, while not it's only recognized as "to-d". We may
> set an alias.
>
> Was working:
> {code:java}
> # camel-k: language=yaml dependency=camel-log
> - from:
> uri: "timer:yaml"
> parameters:
> period: "1000"
> steps:
> - tod: "log:info"
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16490) YAML DSL tod is no longer recognized (requires to-d)
Nicola Ferraro created CAMEL-16490: -- Summary: YAML DSL tod is no longer recognized (requires to-d) Key: CAMEL-16490 URL: https://issues.apache.org/jira/browse/CAMEL-16490 Project: Camel Issue Type: Bug Components: camel-yaml-dsl Affects Versions: 3.9.0 Reporter: Nicola Ferraro It was "tod" prior to 3.9, while not it's only recognized as "to-d". We may set an alias. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16489) YAML DSL is sensitive to key ordering
[
https://issues.apache.org/jira/browse/CAMEL-16489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro updated CAMEL-16489:
---
Description:
Related to [https://github.com/apache/camel-k/issues/2203]
This does not seem to work in YAML DSL:
{code:java}
- from:
steps:
- to:
parameters:
showHeaders: "true"
uri: "log:info"
uri: "timer:tick"
{code}
Error:
{code:java}
[1] Caused by: java.lang.IllegalStateException: url must be set before setting
properties
[1] at
org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ToDefinitionDeserializer.setProperty(ModelDeserializers.java:14189)
[1] at
org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ToDefinitionDeserializer.setProperty(ModelDeserializers.java:14141)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.setProperties(YamlDeserializerBase.java:103)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:51)
[1] at
org.apache.camel.k.loader.yaml.YamlSourceLoaderDeserializerResolver$ToDeserializer.construct(YamlSourceLoaderDeserializerResolver.java:65)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializationContext$2.construct(YamlDeserializationContext.java:194)
[1] at
org.apache.camel.dsl.yaml.deserializers.ProcessorDefinitionDeserializer.construct(ProcessorDefinitionDeserializer.java:36)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializationContext$1.construct(YamlDeserializationContext.java:152)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asType(YamlDeserializerSupport.java:290)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asCollection(YamlDeserializerSupport.java:268)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asFlatCollection(YamlDeserializerSupport.java:249)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asFlatList(YamlDeserializerSupport.java:223)
[1] at
org.apache.camel.dsl.yaml.deserializers.RouteFromDefinitionDeserializer.setProperties(RouteFromDefinitionDeserializer.java:76)
[1] at
org.apache.camel.dsl.yaml.deserializers.RouteFromDefinitionDeserializer.setProperties(RouteFromDefinitionDeserializer.java:36)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:51)
[1] at
org.apache.camel.k.loader.yaml.YamlSourceLoaderDeserializerResolver$RouteFromDeserializer.construct(YamlSourceLoaderDeserializerResolver.java:57)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializationContext$2.construct(YamlDeserializationContext.java:194)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObjectNoCheck(BaseConstructor.java:140)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObject(BaseConstructor.java:128)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructSequenceStep2(BaseConstructor.java:206)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructSequence(BaseConstructor.java:199)
[1] at
org.snakeyaml.engine.v2.constructor.StandardConstructor$ConstructYamlSeq.construct(StandardConstructor.java:340)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObjectNoCheck(BaseConstructor.java:140)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObject(BaseConstructor.java:128)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.construct(BaseConstructor.java:87)
[1] ... 32 more {code}
Changing the order to this, fixes:
{code:java}
- from:
uri: "timer:tick"
steps:
- to:
uri: "log:info"
parameters:
showHeaders: "true" {code}
was:
Related to [https://github.com/apache/camel-k/issues/2203]
This does not seem to work in YAML DSL:
{code:java}
- from:
steps:
- to:
uri: "log:info"
parameters:
showHeaders: "true"
uri: "timer:tick"
{code}
Error:
{code:java}
[1] Caused by: java.lang.IllegalStateException: url must be set before setting
properties
[1] at
org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ToDefinitionDeserializer.setProperty(ModelDeserializers.java:14189)
[1] at
org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ToDefinitionDeserializer.setProperty(ModelDeserializers.java:14141)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.setProperties(YamlDeserializerBase.java:103)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:51)
[1] at
org.apache.camel.k.loader.yaml.YamlSourceLoaderDeserializerResolver$ToDeserializer.construct(YamlSourceLoaderDeserializerResolver.java:65)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializationContext$2.construct(YamlDeserializationContext.java:194)
[1] at
[jira] [Updated] (CAMEL-16489) YAML DSL is sensitive to key ordering
[
https://issues.apache.org/jira/browse/CAMEL-16489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro updated CAMEL-16489:
---
Description:
Related to [https://github.com/apache/camel-k/issues/2203]
This does not seem to work in YAML DSL:
{code:java}
- from:
steps:
- to:
uri: "log:info"
parameters:
showHeaders: "true"
uri: "timer:tick"
{code}
Error:
{code:java}
[1] Caused by: java.lang.IllegalStateException: url must be set before setting
properties
[1] at
org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ToDefinitionDeserializer.setProperty(ModelDeserializers.java:14189)
[1] at
org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ToDefinitionDeserializer.setProperty(ModelDeserializers.java:14141)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.setProperties(YamlDeserializerBase.java:103)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:51)
[1] at
org.apache.camel.k.loader.yaml.YamlSourceLoaderDeserializerResolver$ToDeserializer.construct(YamlSourceLoaderDeserializerResolver.java:65)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializationContext$2.construct(YamlDeserializationContext.java:194)
[1] at
org.apache.camel.dsl.yaml.deserializers.ProcessorDefinitionDeserializer.construct(ProcessorDefinitionDeserializer.java:36)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializationContext$1.construct(YamlDeserializationContext.java:152)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asType(YamlDeserializerSupport.java:290)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asCollection(YamlDeserializerSupport.java:268)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asFlatCollection(YamlDeserializerSupport.java:249)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asFlatList(YamlDeserializerSupport.java:223)
[1] at
org.apache.camel.dsl.yaml.deserializers.RouteFromDefinitionDeserializer.setProperties(RouteFromDefinitionDeserializer.java:76)
[1] at
org.apache.camel.dsl.yaml.deserializers.RouteFromDefinitionDeserializer.setProperties(RouteFromDefinitionDeserializer.java:36)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:51)
[1] at
org.apache.camel.k.loader.yaml.YamlSourceLoaderDeserializerResolver$RouteFromDeserializer.construct(YamlSourceLoaderDeserializerResolver.java:57)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializationContext$2.construct(YamlDeserializationContext.java:194)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObjectNoCheck(BaseConstructor.java:140)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObject(BaseConstructor.java:128)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructSequenceStep2(BaseConstructor.java:206)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructSequence(BaseConstructor.java:199)
[1] at
org.snakeyaml.engine.v2.constructor.StandardConstructor$ConstructYamlSeq.construct(StandardConstructor.java:340)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObjectNoCheck(BaseConstructor.java:140)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObject(BaseConstructor.java:128)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.construct(BaseConstructor.java:87)
[1] ... 32 more {code}
Changing the order to this, fixes:
{code:java}
- from:
uri: "timer:tick"
steps:
- to:
uri: "log:info"
parameters:
showHeaders: "true" {code}
was:
Related to [https://github.com/apache/camel-k/issues/2203]
This does not seem to work in YAML DSL:
{code:java}
- from:
uri: "timer:tick"
steps:
- to:
uri: "log:info"
parameters:
showHeaders: "true"{code}
Error:
{code:java}
[1] Caused by: java.lang.IllegalStateException: url must be set before setting
properties
[1] at
org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ToDefinitionDeserializer.setProperty(ModelDeserializers.java:14189)
[1] at
org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ToDefinitionDeserializer.setProperty(ModelDeserializers.java:14141)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.setProperties(YamlDeserializerBase.java:103)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:51)
[1] at
org.apache.camel.k.loader.yaml.YamlSourceLoaderDeserializerResolver$ToDeserializer.construct(YamlSourceLoaderDeserializerResolver.java:65)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializationContext$2.construct(YamlDeserializationContext.java:194)
[1] at
[jira] [Created] (CAMEL-16489) YAML DSL is sensitive to key ordering
Nicola Ferraro created CAMEL-16489:
--
Summary: YAML DSL is sensitive to key ordering
Key: CAMEL-16489
URL: https://issues.apache.org/jira/browse/CAMEL-16489
Project: Camel
Issue Type: Bug
Components: camel-yaml-dsl
Affects Versions: 3.9.0
Reporter: Nicola Ferraro
Related to [https://github.com/apache/camel-k/issues/2203]
This does not seem to work in YAML DSL:
{code:java}
- from:
uri: "timer:tick"
steps:
- to:
uri: "log:info"
parameters:
showHeaders: "true"{code}
Error:
{code:java}
[1] Caused by: java.lang.IllegalStateException: url must be set before setting
properties
[1] at
org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ToDefinitionDeserializer.setProperty(ModelDeserializers.java:14189)
[1] at
org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ToDefinitionDeserializer.setProperty(ModelDeserializers.java:14141)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.setProperties(YamlDeserializerBase.java:103)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:51)
[1] at
org.apache.camel.k.loader.yaml.YamlSourceLoaderDeserializerResolver$ToDeserializer.construct(YamlSourceLoaderDeserializerResolver.java:65)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializationContext$2.construct(YamlDeserializationContext.java:194)
[1] at
org.apache.camel.dsl.yaml.deserializers.ProcessorDefinitionDeserializer.construct(ProcessorDefinitionDeserializer.java:36)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializationContext$1.construct(YamlDeserializationContext.java:152)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asType(YamlDeserializerSupport.java:290)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asCollection(YamlDeserializerSupport.java:268)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asFlatCollection(YamlDeserializerSupport.java:249)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asFlatList(YamlDeserializerSupport.java:223)
[1] at
org.apache.camel.dsl.yaml.deserializers.RouteFromDefinitionDeserializer.setProperties(RouteFromDefinitionDeserializer.java:76)
[1] at
org.apache.camel.dsl.yaml.deserializers.RouteFromDefinitionDeserializer.setProperties(RouteFromDefinitionDeserializer.java:36)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:51)
[1] at
org.apache.camel.k.loader.yaml.YamlSourceLoaderDeserializerResolver$RouteFromDeserializer.construct(YamlSourceLoaderDeserializerResolver.java:57)
[1] at
org.apache.camel.dsl.yaml.common.YamlDeserializationContext$2.construct(YamlDeserializationContext.java:194)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObjectNoCheck(BaseConstructor.java:140)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObject(BaseConstructor.java:128)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructSequenceStep2(BaseConstructor.java:206)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructSequence(BaseConstructor.java:199)
[1] at
org.snakeyaml.engine.v2.constructor.StandardConstructor$ConstructYamlSeq.construct(StandardConstructor.java:340)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObjectNoCheck(BaseConstructor.java:140)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.constructObject(BaseConstructor.java:128)
[1] at
org.snakeyaml.engine.v2.constructor.BaseConstructor.construct(BaseConstructor.java:87)
[1] ... 32 more {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16320) Netty-http should support redirects
Nicola Ferraro created CAMEL-16320:
--
Summary: Netty-http should support redirects
Key: CAMEL-16320
URL: https://issues.apache.org/jira/browse/CAMEL-16320
Project: Camel
Issue Type: Improvement
Components: camel-netty-http
Reporter: Nicola Ferraro
I'm running the following integration:
{code:java}
- from:
uri: "timer:yaml"
parameters:
period: "1"
steps:
- to:
"netty-http:https://github.com/apache/camel/raw/7204aa132662ab6cb8e3c5afea8b9b0859eff0e8/docs/img/logo.png;
- to: "log:info"
{code}
With `kamel local run netty.yaml`.
It hits a redirect on Github, but there's no way to "follow redirects" in the
component documentation, like for the "http" component.
Error:
{code:java}
2021-03-09 14:58:45,031 WARN [org.apa.cam.com.tim.TimerConsumer] (Camel Thread
#1 - NettyClientTCPWorker) Error processing exchange.
Exchange[1AC7E2A0D31F4A0-]. Caused by:
[org.apache.camel.component.netty.http.NettyHttpOperationFailedException -
Netty HTTP operation failed invoking null with statusCode: 302,
redirectLocation:
https://raw.githubusercontent.com/apache/camel/7204aa132662ab6cb8e3c5afea8b9b0859eff0e8/docs/img/logo.png]:
org.apache.camel.component.netty.http.NettyHttpOperationFailedException: Netty
HTTP operation failed invoking null with statusCode: 302, redirectLocation:
https://raw.githubusercontent.com/apache/camel/7204aa132662ab6cb8e3c5afea8b9b0859eff0e8/docs/img/logo.png
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-16138) Allow KafkaClientFactory to be used without explicit broker URLs
[ https://issues.apache.org/jira/browse/CAMEL-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro reassigned CAMEL-16138: -- Assignee: John Poth > Allow KafkaClientFactory to be used without explicit broker URLs > > > Key: CAMEL-16138 > URL: https://issues.apache.org/jira/browse/CAMEL-16138 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Reporter: Nicola Ferraro >Assignee: John Poth >Priority: Major > Fix For: 3.8.0 > > > CAMEL-16071 has added support for KafkaClientFactory (thanks to > [~javierholguera]). It allows plugging a different implementation of the > Kafka Producer/Consumer, but the component still requires setting the > "brokers" configuration property in the component/endpoint, otherwise an > IllegalArgumentException is thrown. > > This prevents users and platforms to plug implementations of the Kafka > Producers/Consumers with fully externalized configuration (e.g. in > Camel-Quarkus we may be able in the near future to plug configuration > injected into files via Kubernetes service-binding). > > I think the check on the presence of the "brokers" property should be moved > into the default factory. > > cc: [~jpoth] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16138) Allow KafkaClientFactory to be used without explicit broker URLs
[ https://issues.apache.org/jira/browse/CAMEL-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17278013#comment-17278013 ] Nicola Ferraro commented on CAMEL-16138: Yeah, I think that option is available in both components > Allow KafkaClientFactory to be used without explicit broker URLs > > > Key: CAMEL-16138 > URL: https://issues.apache.org/jira/browse/CAMEL-16138 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Reporter: Nicola Ferraro >Priority: Major > Fix For: 3.8.0 > > > CAMEL-16071 has added support for KafkaClientFactory (thanks to > [~javierholguera]). It allows plugging a different implementation of the > Kafka Producer/Consumer, but the component still requires setting the > "brokers" configuration property in the component/endpoint, otherwise an > IllegalArgumentException is thrown. > > This prevents users and platforms to plug implementations of the Kafka > Producers/Consumers with fully externalized configuration (e.g. in > Camel-Quarkus we may be able in the near future to plug configuration > injected into files via Kubernetes service-binding). > > I think the check on the presence of the "brokers" property should be moved > into the default factory. > > cc: [~jpoth] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16138) Allow KafkaClientFactory to be used without explicit broker URLs
Nicola Ferraro created CAMEL-16138: -- Summary: Allow KafkaClientFactory to be used without explicit broker URLs Key: CAMEL-16138 URL: https://issues.apache.org/jira/browse/CAMEL-16138 Project: Camel Issue Type: Task Components: camel-kafka Reporter: Nicola Ferraro Fix For: 3.8.0 CAMEL-16071 has added support for KafkaClientFactory (thanks to [~javierholguera]). It allows plugging a different implementation of the Kafka Producer/Consumer, but the component still requires setting the "brokers" configuration property in the component/endpoint, otherwise an IllegalArgumentException is thrown. This prevents users and platforms to plug implementations of the Kafka Producers/Consumers with fully externalized configuration (e.g. in Camel-Quarkus we may be able in the near future to plug configuration injected into files via Kubernetes service-binding). I think the check on the presence of the "brokers" property should be moved into the default factory. cc: [~jpoth] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15911) Remove POM from distribution of Camel K runtime
[ https://issues.apache.org/jira/browse/CAMEL-15911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-15911. Resolution: Fixed Updated released files and instructions for next releases > Remove POM from distribution of Camel K runtime > --- > > Key: CAMEL-15911 > URL: https://issues.apache.org/jira/browse/CAMEL-15911 > Project: Camel > Issue Type: Task > Components: distribution >Reporter: Zoran Regvart >Assignee: Nicola Ferraro >Priority: Major > > There is no need to distribute the Camel K runtime POM, it is already > included in the source zip package and folk will be downloading it from Maven > central repository, it is of no use to anyone in the distribution. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15881) Add a rebalancing cluster service
[ https://issues.apache.org/jira/browse/CAMEL-15881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-15881. Resolution: Fixed > Add a rebalancing cluster service > - > > Key: CAMEL-15881 > URL: https://issues.apache.org/jira/browse/CAMEL-15881 > Project: Camel > Issue Type: New Feature > Components: camel-core, camel-kubernetes >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Major > Fix For: 3.7.0 > > > I've been working on a re-balancing cluster service implementation that can > be used to assign to application instances an equal number of cluster-service > locks, when multiple ones are used in the same application. > > This can be used to re-balance partitions in a cluster of service instances, > if locks are 1:1 partition keys. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15881) Add a rebalancing cluster service
Nicola Ferraro created CAMEL-15881: -- Summary: Add a rebalancing cluster service Key: CAMEL-15881 URL: https://issues.apache.org/jira/browse/CAMEL-15881 Project: Camel Issue Type: New Feature Components: camel-core, camel-kubernetes Reporter: Nicola Ferraro Assignee: Nicola Ferraro Fix For: 3.7.0 I've been working on a re-balancing cluster service implementation that can be used to assign to application instances an equal number of cluster-service locks, when multiple ones are used in the same application. This can be used to re-balance partitions in a cluster of service instances, if locks are 1:1 partition keys. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15287) Non-uniform way to handle nulls in http clients
Nicola Ferraro created CAMEL-15287:
--
Summary: Non-uniform way to handle nulls in http clients
Key: CAMEL-15287
URL: https://issues.apache.org/jira/browse/CAMEL-15287
Project: Camel
Issue Type: Bug
Reporter: Nicola Ferraro
Suppose you have an external Quarkus service that replies always with null.
When calling it from a camel route via:
{code:java}
.to("http://quarkus-service/null-api;) {code}
Then the body of the exchange is null.
But if we use:
{code:java}
.to("netty-http:http://quarkus-service/null-api;){code}
Then the body becomes an empty InputStream, which is not null.
I don't know what's the correct way to handle such cases, but we should try to
uniform them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14922) Cannot enable cors on platform-http
[
https://issues.apache.org/jira/browse/CAMEL-14922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro updated CAMEL-14922:
---
Issue Type: Bug (was: Improvement)
> Cannot enable cors on platform-http
> ---
>
> Key: CAMEL-14922
> URL: https://issues.apache.org/jira/browse/CAMEL-14922
> Project: Camel
> Issue Type: Bug
> Components: camel-platform-http
>Affects Versions: 3.2.0
>Reporter: Nicola Ferraro
>Priority: Critical
>
> I've tried to enable cors via properties using
> `camel.context.rest-configuration.enable-cors=true` (but it should also
> happen via DSL configuration), but the platform-http component adds a
> parameter to the URI that is not recognized downstream: `optionsEnabled=true`.
> I've tested it with both the vertx and the quarkus implementation, both fail
> with the following exception:
> {code}
> [2] Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint:
> platform-http:///timeline?httpMethodRestrict=GET%2COPTIONS=true
> due to: There are 1 parameters that couldn't be set on the endpoint. Check
> the uri if the parameters are spelt correctly and that they are properties of
> the endpoint. Unknown parameters=[{optionsEnabled=true}]
> [2] at
> org.apache.camel.support.DefaultComponent.validateParameters(DefaultComponent.java:358)
> [2] at
> org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:261)
> [2] at
> org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:780)
> [2] ... 26 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14922) Cannot enable cors on platform-http
Nicola Ferraro created CAMEL-14922:
--
Summary: Cannot enable cors on platform-http
Key: CAMEL-14922
URL: https://issues.apache.org/jira/browse/CAMEL-14922
Project: Camel
Issue Type: Improvement
Components: camel-platform-http
Affects Versions: 3.2.0
Reporter: Nicola Ferraro
I've tried to enable cors via properties using
`camel.context.rest-configuration.enable-cors=true` (but it should also happen
via DSL configuration), but the platform-http component adds a parameter to the
URI that is not recognized downstream: `optionsEnabled=true`.
I've tested it with both the vertx and the quarkus implementation, both fail
with the following exception:
{code}
[2] Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
resolve endpoint:
platform-http:///timeline?httpMethodRestrict=GET%2COPTIONS=true
due to: There are 1 parameters that couldn't be set on the endpoint. Check the
uri if the parameters are spelt correctly and that they are properties of the
endpoint. Unknown parameters=[{optionsEnabled=true}]
[2] at
org.apache.camel.support.DefaultComponent.validateParameters(DefaultComponent.java:358)
[2] at
org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:261)
[2] at
org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:780)
[2] ... 26 more
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14658) Provide a simpler way to connect to a local s3 instance
[ https://issues.apache.org/jira/browse/CAMEL-14658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051411#comment-17051411 ] Nicola Ferraro commented on CAMEL-14658: So, the use case is this briefly. I've a camel k integration that talks to S3. I want to configure a CI that checks that everything is right and uses a Minio backend, and a staging environment that uses the real S3 environment. Ideally I could set the specific environment properties in a property file: - s3.properties (https://github.com/openshift-integration/camel-k-example-api/blob/master/s3.properties) for staging - ci.properties for the CI job, but without the endpoint option I need to code an external class that is injected only in CI (https://github.com/openshift-integration/camel-k-example-api/blob/master/test/MinioConfigurer.java) It would be much nicer if we supported setting the endpoint directly in properties, considering that it seems a property like many others and also considering that the tooling (e.g. VSCode plugin) currently does not assist users when dealing with non-core components (https://github.com/camel-tooling/vscode-camelk/issues/337). > Provide a simpler way to connect to a local s3 instance > --- > > Key: CAMEL-14658 > URL: https://issues.apache.org/jira/browse/CAMEL-14658 > Project: Camel > Issue Type: Improvement > Components: camel-aws-s3 >Reporter: Nicola Ferraro >Priority: Major > > I've done this to workaround: > https://github.com/openshift-integration/camel-k-example-api/blob/master/test/MinioConfigurer.java > But it's technically enough to add a endpoint property to the component > options and other flags to have it configured via properties. > I don't know if this applies also to other aws endpoints, but it seems easy > for S3, cc: [~acosentino]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14658) Provide a simpler way to connect to a local s3 instance
[ https://issues.apache.org/jira/browse/CAMEL-14658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro updated CAMEL-14658: --- Description: I've done this to workaround: https://github.com/openshift-integration/camel-k-example-api/blob/master/test/MinioConfigurer.java But it's technically enough to add a endpoint property to the component options and other flags to have it configured via properties. I don't know if this applies also to other aws endpoints, but it seems easy for S3, cc: [~acosentino]. was: I've done this to workaround: https://github.com/openshift-integration/camel-k-example-api/blob/master/test/MinioConfigurer.java But it's technically enough to add a endpoint property to the component options and other flags to have it configured via properties. I don't know if this applies also to other aws endpoints, but it seems easy for S3. > Provide a simpler way to connect to a local s3 instance > --- > > Key: CAMEL-14658 > URL: https://issues.apache.org/jira/browse/CAMEL-14658 > Project: Camel > Issue Type: Improvement > Components: camel-aws-s3 >Reporter: Nicola Ferraro >Priority: Major > > I've done this to workaround: > https://github.com/openshift-integration/camel-k-example-api/blob/master/test/MinioConfigurer.java > But it's technically enough to add a endpoint property to the component > options and other flags to have it configured via properties. > I don't know if this applies also to other aws endpoints, but it seems easy > for S3, cc: [~acosentino]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14658) Provide a simpler way to connect to a local s3 instance
Nicola Ferraro created CAMEL-14658: -- Summary: Provide a simpler way to connect to a local s3 instance Key: CAMEL-14658 URL: https://issues.apache.org/jira/browse/CAMEL-14658 Project: Camel Issue Type: Improvement Components: camel-aws-s3 Reporter: Nicola Ferraro I've done this to workaround: https://github.com/openshift-integration/camel-k-example-api/blob/master/test/MinioConfigurer.java But it's technically enough to add a endpoint property to the component options and other flags to have it configured via properties. I don't know if this applies also to other aws endpoints, but it seems easy for S3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14645) Wrong rest mapping on camel-undertow
Nicola Ferraro created CAMEL-14645:
--
Summary: Wrong rest mapping on camel-undertow
Key: CAMEL-14645
URL: https://issues.apache.org/jira/browse/CAMEL-14645
Project: Camel
Issue Type: Bug
Components: camel-undertow
Reporter: Nicola Ferraro
The order in which routes are declared changes the behavior of the integration.
E.g.
{code:java}
rest()
.get("/{pippo}")
.route()
.setBody().simple("Route with name: ${header.pippo}")
.setHeader("Content-Type", constant("text/plain"));
rest()
.get("/")
.route()
.setBody().constant("Route without name")
.setHeader("Content-Type", constant("text/plain"));
{code}
When calling it with:
{code}
curl http://service:8080/
{code}
The first route replies ("Route with name: ..."), but the second was supposed
to.
This same example works with jetty and netty-http.
As workaround for undertow, if the order of the two routes is reversed, it
works correctly.
But when you create a route from a given openapi.json file, the order is given
and you're not supposed to change it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14381) create a camel-mutiny component
[
https://issues.apache.org/jira/browse/CAMEL-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro updated CAMEL-14381:
---
Fix Version/s: (was: 3.1.0)
3.2.0
> create a camel-mutiny component
> ---
>
> Key: CAMEL-14381
> URL: https://issues.apache.org/jira/browse/CAMEL-14381
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Assignee: Nicola Ferraro
>Priority: Major
> Fix For: 3.2.0
>
>
> We should create a mutiny component, similar to camel-reactive-streams
> https://github.com/smallrye/smallrye-mutiny
> {code:java}
> CamelMutiny.on(context)
> .toMulti(servicenow().table("incident").max(100))
> .then(m -> doSomething(m))
> .await().indefinitely();
> {code}
> In Quarkus, we can nicely integrate camel into reactive messaging, like:
> {code:java}
> @Inject
> CamelMutiny mutiny;
> @Outgoing
> Multi fromEndpoint() {
> return mutiny.toMulti(servicenow().table("incident").max(100));
> }
> @Outgoing
> Multi fromEndpointURI() {
> return mutiny.toMulti("servicenow?table=incident");
> }
> @Incoming
> void toEndpoint(Multi items) {
> return mutiny.subscribeTo(items)
> .with(servicenow().table("incident").max(100).async());
> }
> @Incoming
> void toEndpointURI(Multi items) {
> return mutiny.subscribeTo(items)
> .with(s"servicenow?table=incident");
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14385) Camel-cron component
[ https://issues.apache.org/jira/browse/CAMEL-14385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-14385. Resolution: Fixed > Camel-cron component > > > Key: CAMEL-14385 > URL: https://issues.apache.org/jira/browse/CAMEL-14385 > Project: Camel > Issue Type: New Feature >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Major > Fix For: 3.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This comes from a discussion on Camel K: > https://github.com/apache/camel-k-runtime/pull/223#issuecomment-572515581 > > It would be a wrapper component, currently around Quartz only. Camel K would > be able to override it with the Kubernetes scheduler if needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14381) create a camel-mutiny component
[
https://issues.apache.org/jira/browse/CAMEL-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro reassigned CAMEL-14381:
--
Assignee: Nicola Ferraro
> create a camel-mutiny component
> ---
>
> Key: CAMEL-14381
> URL: https://issues.apache.org/jira/browse/CAMEL-14381
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Assignee: Nicola Ferraro
>Priority: Major
> Fix For: 3.1.0
>
>
> We should create a mutiny component, similar to camel-reactive-streams
> https://github.com/smallrye/smallrye-mutiny
> {code:java}
> CamelMutiny.on(context)
> .toMulti(servicenow().table("incident").max(100))
> .then(m -> doSomething(m))
> .await().indefinitely();
> {code}
> In Quarkus, we can nicely integrate camel into reactive messaging, like:
> {code:java}
> @Inject
> CamelMutiny mutiny;
> @Outgoing
> Multi fromEndpoint() {
> return mutiny.toMulti(servicenow().table("incident").max(100));
> }
> @Outgoing
> Multi fromEndpointURI() {
> return mutiny.toMulti("servicenow?table=incident");
> }
> @Incoming
> void toEndpoint(Multi items) {
> return mutiny.subscribeTo(items)
> .with(servicenow().table("incident").max(100).async());
> }
> @Incoming
> void toEndpointURI(Multi items) {
> return mutiny.subscribeTo(items)
> .with(s"servicenow?table=incident");
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14385) Camel-cron component
Nicola Ferraro created CAMEL-14385: -- Summary: Camel-cron component Key: CAMEL-14385 URL: https://issues.apache.org/jira/browse/CAMEL-14385 Project: Camel Issue Type: New Feature Reporter: Nicola Ferraro Assignee: Nicola Ferraro Fix For: 3.1.0, 3.x This comes from a discussion on Camel K: https://github.com/apache/camel-k-runtime/pull/223#issuecomment-572515581 It would be a wrapper component, currently around Quartz only. Camel K would be able to override it with the Kubernetes scheduler if needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14300) Java 8 Supplier overloadings break all DSLs
Nicola Ferraro created CAMEL-14300: -- Summary: Java 8 Supplier overloadings break all DSLs Key: CAMEL-14300 URL: https://issues.apache.org/jira/browse/CAMEL-14300 Project: Camel Issue Type: Bug Affects Versions: 3.0.0 Reporter: Nicola Ferraro There are a number of issues opened in Camel K since most DSLs are no longer working. The cause is probably the addition of these overloadings of the `.process()` method that work in Java but fail in Groovy and JS: [https://github.com/apache/camel/commit/e38f2a0751445478a2a71620407a723ffab9ab04] Camel K issues: - [https://github.com/apache/camel-k/issues/1143] - [https://github.com/apache/camel-k/issues/1144] Are they really important for Camel users? Can we deprecate them and then remove in next minor? cc: [~davsclaus], [~lb] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14219) ReactiveStreams subscriber does not enforce type conversion
Nicola Ferraro created CAMEL-14219: -- Summary: ReactiveStreams subscriber does not enforce type conversion Key: CAMEL-14219 URL: https://issues.apache.org/jira/browse/CAMEL-14219 Project: Camel Issue Type: Bug Components: camel-reactive-streams Affects Versions: 3.0.0 Reporter: Nicola Ferraro Assignee: Nicola Ferraro See: [https://stackoverflow.com/questions/59004326/my-camel-route-app-detects-other-apps-published-ampq-message-but-fails-to/59041466#59041466] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-13401) Create a webhook meta-component
[
https://issues.apache.org/jira/browse/CAMEL-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro resolved CAMEL-13401.
Resolution: Fixed
> Create a webhook meta-component
> ---
>
> Key: CAMEL-13401
> URL: https://issues.apache.org/jira/browse/CAMEL-13401
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Nicola Ferraro
>Assignee: Nicola Ferraro
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The intention is to create a meta-component that allows other components to
> define how they can configure themselves to create push-based consumers by
> remotely configuring a webhook.
> The way it's used is similar to the master component.
>
> E.g.
> The following route starts from a Telegram polling consumer:
> {code:java}
> from("telegram:bots/token")
> .to("log:info"){code}
>
> By prepending the _webhook_ uri prefix, we literally _prepend a webhook
> listener_ to it:
> {code:java}
> from("webhook:telegram:bots/token")
> .to("log:info"){code}
>
> The role of the webhook meta-component is of:
> * Exposing one or more endpoints using the rest consumer factory
> * Running the delegate endpoint in webhook mode (each component defines the
> specific rules)
> * Registering the webhook at the webhook provider site (specific per
> component, external URL configurable)
> * Unregistering the webhook at the webhook provider site when it's no more
> necessary (specific per component)
> So, the meta-component sets up the infrastructure and orchestrates the
> workflow.
>
> Registration/deregistration should be configurable:
> * In standalone mode, the registration is done at route startup, the
> deregistration is done at route shutdown
> * In Camel K mode, automatic registration is disabled by default, because
> the deployment can be scale up/down (especially in Knative mode, where this
> happens automatically):
> ** Camel K will setup a webhook subscription resource that takes care of
> externally registering/deregistering the webhook when the integration is
> created/edited/deleted (will use the webhook component API for this)
>
> With this meta-component, in Camel K + Knative mode, we can create
> integrations from telegram, slack, github, twitter, dropbox, that can
> scale down to 0 when not used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13401) Create a webhook meta-component
[
https://issues.apache.org/jira/browse/CAMEL-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16817667#comment-16817667
]
Nicola Ferraro commented on CAMEL-13401:
So in PR [https://github.com/apache/camel/pull/2867], metadata and other info
about the webhook is present at endpoint level. When constructing the route,
the endpoint + component configuration define how the webhook should be
created, as it happen for standard endpoint configuration. There's not a
clearly defined set of metadata info for the webhook that we can inspect for
changes.
In standalone mode it's not an issue, since webhook is registered at startup
and deregistered at shutdown. In Camel K mode, I think it's not a too bad thing
to unregister+register the webhook at each code change, even if not always
needed. But we can think to figure out a more optimized strategy...
I'm closing this issue for the moment, as the base is implemented..
> Create a webhook meta-component
> ---
>
> Key: CAMEL-13401
> URL: https://issues.apache.org/jira/browse/CAMEL-13401
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Nicola Ferraro
>Assignee: Nicola Ferraro
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The intention is to create a meta-component that allows other components to
> define how they can configure themselves to create push-based consumers by
> remotely configuring a webhook.
> The way it's used is similar to the master component.
>
> E.g.
> The following route starts from a Telegram polling consumer:
> {code:java}
> from("telegram:bots/token")
> .to("log:info"){code}
>
> By prepending the _webhook_ uri prefix, we literally _prepend a webhook
> listener_ to it:
> {code:java}
> from("webhook:telegram:bots/token")
> .to("log:info"){code}
>
> The role of the webhook meta-component is of:
> * Exposing one or more endpoints using the rest consumer factory
> * Running the delegate endpoint in webhook mode (each component defines the
> specific rules)
> * Registering the webhook at the webhook provider site (specific per
> component, external URL configurable)
> * Unregistering the webhook at the webhook provider site when it's no more
> necessary (specific per component)
> So, the meta-component sets up the infrastructure and orchestrates the
> workflow.
>
> Registration/deregistration should be configurable:
> * In standalone mode, the registration is done at route startup, the
> deregistration is done at route shutdown
> * In Camel K mode, automatic registration is disabled by default, because
> the deployment can be scale up/down (especially in Knative mode, where this
> happens automatically):
> ** Camel K will setup a webhook subscription resource that takes care of
> externally registering/deregistering the webhook when the integration is
> created/edited/deleted (will use the webhook component API for this)
>
> With this meta-component, in Camel K + Knative mode, we can create
> integrations from telegram, slack, github, twitter, dropbox, that can
> scale down to 0 when not used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13401) Create a webhook meta-component
[
https://issues.apache.org/jira/browse/CAMEL-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro updated CAMEL-13401:
---
Description:
The intention is to create a meta-component that allows other components to
define how they can configure themselves to create push-based consumers by
remotely configuring a webhook.
The way it's used is similar to the master component.
E.g.
The following route starts from a Telegram polling consumer:
{code:java}
from("telegram:bots/token")
.to("log:info"){code}
By prepending the _webhook_ uri prefix, we literally _prepend a webhook
listener_ to it:
{code:java}
from("webhook:telegram:bots/token")
.to("log:info"){code}
The role of the webhook meta-component is of:
* Exposing one or more endpoints using the rest consumer factory
* Running the delegate endpoint in webhook mode (each component defines the
specific rules)
* Registering the webhook at the webhook provider site (specific per
component, external URL configurable)
* Unregistering the webhook at the webhook provider site when it's no more
necessary (specific per component)
So, the meta-component sets up the infrastructure and orchestrates the workflow.
Registration/deregistration should be configurable:
* In standalone mode, the registration is done at route startup, the
deregistration is done at route shutdown
* In Camel K mode, automatic registration is disabled by default, because the
deployment can be scale up/down (especially in Knative mode, where this happens
automatically):
** Camel K will setup a webhook subscription resource that takes care of
externally registering/deregistering the webhook when the integration is
created/edited/deleted (will use the webhook component API for this)
With this meta-component, in Camel K + Knative mode, we can create integrations
from telegram, slack, github, twitter, dropbox, that can scale down to 0
when not used.
> Create a webhook meta-component
> ---
>
> Key: CAMEL-13401
> URL: https://issues.apache.org/jira/browse/CAMEL-13401
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Nicola Ferraro
>Assignee: Nicola Ferraro
>Priority: Major
> Fix For: 3.0.0
>
>
> The intention is to create a meta-component that allows other components to
> define how they can configure themselves to create push-based consumers by
> remotely configuring a webhook.
> The way it's used is similar to the master component.
>
> E.g.
> The following route starts from a Telegram polling consumer:
> {code:java}
> from("telegram:bots/token")
> .to("log:info"){code}
>
> By prepending the _webhook_ uri prefix, we literally _prepend a webhook
> listener_ to it:
> {code:java}
> from("webhook:telegram:bots/token")
> .to("log:info"){code}
>
> The role of the webhook meta-component is of:
> * Exposing one or more endpoints using the rest consumer factory
> * Running the delegate endpoint in webhook mode (each component defines the
> specific rules)
> * Registering the webhook at the webhook provider site (specific per
> component, external URL configurable)
> * Unregistering the webhook at the webhook provider site when it's no more
> necessary (specific per component)
> So, the meta-component sets up the infrastructure and orchestrates the
> workflow.
>
> Registration/deregistration should be configurable:
> * In standalone mode, the registration is done at route startup, the
> deregistration is done at route shutdown
> * In Camel K mode, automatic registration is disabled by default, because
> the deployment can be scale up/down (especially in Knative mode, where this
> happens automatically):
> ** Camel K will setup a webhook subscription resource that takes care of
> externally registering/deregistering the webhook when the integration is
> created/edited/deleted (will use the webhook component API for this)
>
> With this meta-component, in Camel K + Knative mode, we can create
> integrations from telegram, slack, github, twitter, dropbox, that can
> scale down to 0 when not used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13401) Create a webhook meta-component
Nicola Ferraro created CAMEL-13401: -- Summary: Create a webhook meta-component Key: CAMEL-13401 URL: https://issues.apache.org/jira/browse/CAMEL-13401 Project: Camel Issue Type: New Feature Components: camel-core Reporter: Nicola Ferraro Assignee: Nicola Ferraro Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12981) camel-catalog: provide information about active/passive endpoints
Nicola Ferraro created CAMEL-12981: -- Summary: camel-catalog: provide information about active/passive endpoints Key: CAMEL-12981 URL: https://issues.apache.org/jira/browse/CAMEL-12981 Project: Camel Issue Type: Task Components: camel-core Reporter: Nicola Ferraro Fix For: 3.0.0 In Camel K we need to distinguish active from passive endpoints in order to determine when a integration can be scaled down to 0. E.g. * a "timer" (start) endpoint is *active*, because it needs to have a JVM always running and do something at each interval * a "jms" (start) endpoint is *active* because it needs to establish a connection to the broker and keep it alive * a "direct" or "seda" endpoint is *passive*, because they do something when they receive an exchange from another route * a "undertow" (start) endpoint is *passive*, because it does nothing until somebody calls it from an +external+ service (http based endpoints can all be considered passive in Knative+CamelK) We should add this information to the catalog. Now I've embedded it in Camel K. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12966) camel-netty-http: use relative path by default
Nicola Ferraro created CAMEL-12966: -- Summary: camel-netty-http: use relative path by default Key: CAMEL-12966 URL: https://issues.apache.org/jira/browse/CAMEL-12966 Project: Camel Issue Type: Task Reporter: Nicola Ferraro Fix For: 2.24.0 Netty-http 4 has a non-standard way of dealing with path, using the full url on the first line of the HTTP request. E.g. GET [http://thehost/thepath] instead of: GET /thepath This is controlled by the useRelativePath, that should be defaulted to "true" to be compatible with other components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12140) camel-saga-eip: add asynchronous compensation and related callbacks
[ https://issues.apache.org/jira/browse/CAMEL-12140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689261#comment-16689261 ] Nicola Ferraro commented on CAMEL-12140: There are some changes in progress in the microprofile LRA spec, it's better to defer until there's a stable release of LRA so we can map the EIP on the new features. > camel-saga-eip: add asynchronous compensation and related callbacks > --- > > Key: CAMEL-12140 > URL: https://issues.apache.org/jira/browse/CAMEL-12140 > Project: Camel > Issue Type: Improvement > Components: eip >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Major > Fix For: 3.0.0, 2.24.0 > > > Compensating actions may not be able to complete synchronously. We should add > some mechanism to do async (long) compensations. The same for completion > callbacks. > The LRA framework handle this using the "status" callback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12788) Camel K: initial effort
[ https://issues.apache.org/jira/browse/CAMEL-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12788. Resolution: Invalid Moved everything to: https://github.com/apache/camel-k/issues > Camel K: initial effort > --- > > Key: CAMEL-12788 > URL: https://issues.apache.org/jira/browse/CAMEL-12788 > Project: Camel > Issue Type: Task > Components: camel-k >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Major > > Let's start writing down some tasks for the Camel k project here. Is that ok > [~ancosen]? We should also add a "camel-k" component to Jira. > We have a new repo on github (apache/camel-k) and on docker hub > (apache/camel-k). > I've done a end-to-end test and I'm able to run a integration on Openshift, > but the installation procedure is fairly complex. > Some subtasks created. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12803) Camel K: add uninstall command
[ https://issues.apache.org/jira/browse/CAMEL-12803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12803. Resolution: Invalid Moved to: https://github.com/apache/camel-k/issues/38 > Camel K: add uninstall command > -- > > Key: CAMEL-12803 > URL: https://issues.apache.org/jira/browse/CAMEL-12803 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Dmitry Volodin >Priority: Minor > > It's would be nice to have an uninstall command which will remove all camel-k > artifacts (cluster-wide and project related). This will be useful for > development and update procedures. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12800) Camel K: add user guide
[ https://issues.apache.org/jira/browse/CAMEL-12800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12800. Resolution: Invalid Moved to: https://github.com/apache/camel-k/issues/37 > Camel K: add user guide > --- > > Key: CAMEL-12800 > URL: https://issues.apache.org/jira/browse/CAMEL-12800 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > We should document what a user needs to do in order to use Camel K (from > "kamel run Source.java" on) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12799) Camel K: document architecture
[ https://issues.apache.org/jira/browse/CAMEL-12799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12799. Resolution: Invalid Moved to: https://github.com/apache/camel-k/issues/36 > Camel K: document architecture > -- > > Key: CAMEL-12799 > URL: https://issues.apache.org/jira/browse/CAMEL-12799 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > We should document the architecture: > * Operator and client, how they interact > * Build modes > * Publishing modes > * The deployment flow -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12797) Camel K: add roadmap information
[ https://issues.apache.org/jira/browse/CAMEL-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12797. Resolution: Invalid Moved to: https://github.com/apache/camel-k/issues/35 > Camel K: add roadmap information > > > Key: CAMEL-12797 > URL: https://issues.apache.org/jira/browse/CAMEL-12797 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > We should add to the documentation a high level roadmap of the project (see > nicolaferraro/integration-operator). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12796) Camel K: add dev mode
[ https://issues.apache.org/jira/browse/CAMEL-12796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12796. Resolution: Invalid Moved to: https://github.com/apache/camel-k/issues/34 > Camel K: add dev mode > - > > Key: CAMEL-12796 > URL: https://issues.apache.org/jira/browse/CAMEL-12796 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Minor > > It would be nice to mix CAMEL-12794 and CAMEL-12795 to create a "kamel run > --dev Source.java" that: > * Deploys the integration with a sidecar strategy > * Waits for the deployment to be running > * Displays the logs in the console > * Listen for changes in the source file and triggers a redeploy, so that > changes are immediately visible > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12795) Camel K: add wait and log watch options
[
https://issues.apache.org/jira/browse/CAMEL-12795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro resolved CAMEL-12795.
Resolution: Invalid
Moved to https://github.com/apache/camel-k/issues/33
> Camel K: add wait and log watch options
> ---
>
> Key: CAMEL-12795
> URL: https://issues.apache.org/jira/browse/CAMEL-12795
> Project: Camel
> Issue Type: Sub-task
> Components: camel-k
>Reporter: Nicola Ferraro
>Priority: Minor
>
> We should add a flag to "kamel run" to wait for the deployment to be
> completed before returning ("–wait").
>
> We should add a "kamel logs" command to display a integration logs. It's a
> shorthand for "kubectl logs" and "kubectl logs -f" but Camel K will direct
> those commands to the right pod/container using the integration name.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12794) Camel K: add sidecar builder strategy
[ https://issues.apache.org/jira/browse/CAMEL-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12794. Resolution: Won't Fix Managed contexts are a better strategy. > Camel K: add sidecar builder strategy > - > > Key: CAMEL-12794 > URL: https://issues.apache.org/jira/browse/CAMEL-12794 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > In contexts like plain Kubernetes there's not a default docker registry where > images can be pushed. Until we figure-out a strategy to deploy a docker > registry, we can fallback on a sidecar builder container. > We create a deployment with two containers: > * The main container waits for a trigger and start the application > * The builder container does a maven build and signal the trigger, then > terminates > This will be useful also for "--dev" mode (more later). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12793) Camel K: allow buildless direct deploy
[ https://issues.apache.org/jira/browse/CAMEL-12793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12793. Resolution: Invalid https://github.com/apache/camel-k/issues/31 > Camel K: allow buildless direct deploy > -- > > Key: CAMEL-12793 > URL: https://issues.apache.org/jira/browse/CAMEL-12793 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > The general way of doing builds expects a build phase where a docker image is > generated. > In some cases, when there are no additional dependencies to load respect to > "camel-core" (or respect to a "prebuilt context" we will add in the future), > there's no need to build a docker image and we can run the integration > directly. > We can mount the source file as configmap and load it directly in the runtime. > File mounting will also be the preferred strategy when dealing with ".js" > files (independently of the build phase). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12791) Camel K: manage dependencies
[
https://issues.apache.org/jira/browse/CAMEL-12791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro resolved CAMEL-12791.
Resolution: Invalid
Moved to https://github.com/apache/camel-k/issues/30
> Camel K: manage dependencies
>
>
> Key: CAMEL-12791
> URL: https://issues.apache.org/jira/browse/CAMEL-12791
> Project: Camel
> Issue Type: Sub-task
> Components: camel-k
>Reporter: Nicola Ferraro
>Priority: Major
>
> When the user executes "kamel run Source.java", he might be using some
> components not available in camel-core.
> In this case, the "kamel" script should create the resource as usual (do not
> put too much logic into the client), while the operator in the "Initialize"
> action should scan the source file to find declaration of external maven
> dependencies.
>
> We can use a simplified way to declare dependencies, such as declaring them
> in a comment, e.g.
>
> {code:java}
> // k-include: camel-mail
> {code}
> This way we let the user specify everything in a single file. We can switch
> to something better later (best if recognized by the tooling).
>
>
> The initializer will add "org.apache.camel:camel-mail" to the list of
> dependencies in the CR (custom resource).
>
> We should enable the following ways to include dependencies:
> * Comment in the source file
> * kamel run --dependency camel-mail Source.java
> * Putting it direcly in spec->dependency->items by editing the custom
> resource
> We should also allow to disable the auto-discovery via a flag in
> "spec->dependency->autoDiscovery", controlled by a "kamel
> --dependency-auto-discovery false" client flag.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12790) Camel K: add contributing guide
[ https://issues.apache.org/jira/browse/CAMEL-12790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12790. Resolution: Done > Camel K: add contributing guide > --- > > Key: CAMEL-12790 > URL: https://issues.apache.org/jira/browse/CAMEL-12790 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > We should document how the repository is organized, how to build the project > and how to contribute, including: > * Requirements (e.g. go version - 1.10 - dep and operator sdk tools) > * How to setup the environment (e.g. gopath) > * How to build (e.g. various make options) > * How to test built artifacts (e.g. how to run the operator locally) > * General contribution guide -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12788) Camel K: initial effort
[ https://issues.apache.org/jira/browse/CAMEL-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610587#comment-16610587 ] Nicola Ferraro commented on CAMEL-12788: I've asked INFRA to enable github issues for Camel K. I find it a lot more practical at this stage to develop it directly on Github. I'll move the remaining subtasks there. > Camel K: initial effort > --- > > Key: CAMEL-12788 > URL: https://issues.apache.org/jira/browse/CAMEL-12788 > Project: Camel > Issue Type: Task > Components: camel-k >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Major > > Let's start writing down some tasks for the Camel k project here. Is that ok > [~ancosen]? We should also add a "camel-k" component to Jira. > We have a new repo on github (apache/camel-k) and on docker hub > (apache/camel-k). > I've done a end-to-end test and I'm able to run a integration on Openshift, > but the installation procedure is fairly complex. > Some subtasks created. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12789) Camel K: add install command
[ https://issues.apache.org/jira/browse/CAMEL-12789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12789. Resolution: Done > Camel K: add install command > > > Key: CAMEL-12789 > URL: https://issues.apache.org/jira/browse/CAMEL-12789 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Major > > We need to add a "kamel install" command that will setup Camel K on a > connected cluster. > The installation should: > * Setup the CRD and permissions at cluster level > * Install the operator into the current namespace > Setting up the CRD requires cluster-wide permissions, but it is a one-time > operation and the script can detect authorization issues and help the user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12798) Camel K: document installation
[ https://issues.apache.org/jira/browse/CAMEL-12798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12798. Resolution: Done Assignee: Nicola Ferraro > Camel K: document installation > -- > > Key: CAMEL-12798 > URL: https://issues.apache.org/jira/browse/CAMEL-12798 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Major > > After installation procedure is completed (CAMEL-12789) we should document > how to install and caveats (cluster admin rights, etc.) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12789) Camel K: add install command
[ https://issues.apache.org/jira/browse/CAMEL-12789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610300#comment-16610300 ] Nicola Ferraro commented on CAMEL-12789: Initial command created. I should add a ""--cluster-setup" flag to allow executing cluster-wide actions only (for first time installation). > Camel K: add install command > > > Key: CAMEL-12789 > URL: https://issues.apache.org/jira/browse/CAMEL-12789 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Major > > We need to add a "kamel install" command that will setup Camel K on a > connected cluster. > The installation should: > * Setup the CRD and permissions at cluster level > * Install the operator into the current namespace > Setting up the CRD requires cluster-wide permissions, but it is a one-time > operation and the script can detect authorization issues and help the user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12800) Camel K: add user guide
[ https://issues.apache.org/jira/browse/CAMEL-12800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro updated CAMEL-12800: --- Component/s: camel-k > Camel K: add user guide > --- > > Key: CAMEL-12800 > URL: https://issues.apache.org/jira/browse/CAMEL-12800 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > We should document what a user needs to do in order to use Camel K (from > "kamel run Source.java" on) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12793) Camel K: allow buildless direct deploy
[ https://issues.apache.org/jira/browse/CAMEL-12793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro updated CAMEL-12793: --- Component/s: camel-k > Camel K: allow buildless direct deploy > -- > > Key: CAMEL-12793 > URL: https://issues.apache.org/jira/browse/CAMEL-12793 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > The general way of doing builds expects a build phase where a docker image is > generated. > In some cases, when there are no additional dependencies to load respect to > "camel-core" (or respect to a "prebuilt context" we will add in the future), > there's no need to build a docker image and we can run the integration > directly. > We can mount the source file as configmap and load it directly in the runtime. > File mounting will also be the preferred strategy when dealing with ".js" > files (independently of the build phase). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12798) Camel K: document installation
[ https://issues.apache.org/jira/browse/CAMEL-12798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro updated CAMEL-12798: --- Component/s: camel-k > Camel K: document installation > -- > > Key: CAMEL-12798 > URL: https://issues.apache.org/jira/browse/CAMEL-12798 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > After installation procedure is completed (CAMEL-12789) we should document > how to install and caveats (cluster admin rights, etc.) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12794) Camel K: add sidecar builder strategy
[ https://issues.apache.org/jira/browse/CAMEL-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro updated CAMEL-12794: --- Component/s: camel-k > Camel K: add sidecar builder strategy > - > > Key: CAMEL-12794 > URL: https://issues.apache.org/jira/browse/CAMEL-12794 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > In contexts like plain Kubernetes there's not a default docker registry where > images can be pushed. Until we figure-out a strategy to deploy a docker > registry, we can fallback on a sidecar builder container. > We create a deployment with two containers: > * The main container waits for a trigger and start the application > * The builder container does a maven build and signal the trigger, then > terminates > This will be useful also for "--dev" mode (more later). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12797) Camel K: add roadmap information
[ https://issues.apache.org/jira/browse/CAMEL-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro updated CAMEL-12797: --- Component/s: camel-k > Camel K: add roadmap information > > > Key: CAMEL-12797 > URL: https://issues.apache.org/jira/browse/CAMEL-12797 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > We should add to the documentation a high level roadmap of the project (see > nicolaferraro/integration-operator). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12799) Camel K: document architecture
[ https://issues.apache.org/jira/browse/CAMEL-12799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro updated CAMEL-12799: --- Component/s: camel-k > Camel K: document architecture > -- > > Key: CAMEL-12799 > URL: https://issues.apache.org/jira/browse/CAMEL-12799 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > We should document the architecture: > * Operator and client, how they interact > * Build modes > * Publishing modes > * The deployment flow -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12791) Camel K: manage dependencies
[
https://issues.apache.org/jira/browse/CAMEL-12791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro updated CAMEL-12791:
---
Component/s: camel-k
> Camel K: manage dependencies
>
>
> Key: CAMEL-12791
> URL: https://issues.apache.org/jira/browse/CAMEL-12791
> Project: Camel
> Issue Type: Sub-task
> Components: camel-k
>Reporter: Nicola Ferraro
>Priority: Major
>
> When the user executes "kamel run Source.java", he might be using some
> components not available in camel-core.
> In this case, the "kamel" script should create the resource as usual (do not
> put too much logic into the client), while the operator in the "Initialize"
> action should scan the source file to find declaration of external maven
> dependencies.
>
> We can use a simplified way to declare dependencies, such as declaring them
> in a comment, e.g.
>
> {code:java}
> // k-include: camel-mail
> {code}
> This way we let the user specify everything in a single file. We can switch
> to something better later (best if recognized by the tooling).
>
>
> The initializer will add "org.apache.camel:camel-mail" to the list of
> dependencies in the CR (custom resource).
>
> We should enable the following ways to include dependencies:
> * Comment in the source file
> * kamel run --dependency camel-mail Source.java
> * Putting it direcly in spec->dependency->items by editing the custom
> resource
> We should also allow to disable the auto-discovery via a flag in
> "spec->dependency->autoDiscovery", controlled by a "kamel
> --dependency-auto-discovery false" client flag.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12795) Camel K: add wait and log watch options
[
https://issues.apache.org/jira/browse/CAMEL-12795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro updated CAMEL-12795:
---
Component/s: camel-k
> Camel K: add wait and log watch options
> ---
>
> Key: CAMEL-12795
> URL: https://issues.apache.org/jira/browse/CAMEL-12795
> Project: Camel
> Issue Type: Sub-task
> Components: camel-k
>Reporter: Nicola Ferraro
>Priority: Minor
>
> We should add a flag to "kamel run" to wait for the deployment to be
> completed before returning ("–wait").
>
> We should add a "kamel logs" command to display a integration logs. It's a
> shorthand for "kubectl logs" and "kubectl logs -f" but Camel K will direct
> those commands to the right pod/container using the integration name.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12796) Camel K: add dev mode
[ https://issues.apache.org/jira/browse/CAMEL-12796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro updated CAMEL-12796: --- Component/s: camel-k > Camel K: add dev mode > - > > Key: CAMEL-12796 > URL: https://issues.apache.org/jira/browse/CAMEL-12796 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Minor > > It would be nice to mix CAMEL-12794 and CAMEL-12795 to create a "kamel run > --dev Source.java" that: > * Deploys the integration with a sidecar strategy > * Waits for the deployment to be running > * Displays the logs in the console > * Listen for changes in the source file and triggers a redeploy, so that > changes are immediately visible > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12790) Camel K: add contributing guide
[ https://issues.apache.org/jira/browse/CAMEL-12790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro updated CAMEL-12790: --- Component/s: camel-k > Camel K: add contributing guide > --- > > Key: CAMEL-12790 > URL: https://issues.apache.org/jira/browse/CAMEL-12790 > Project: Camel > Issue Type: Sub-task > Components: camel-k >Reporter: Nicola Ferraro >Priority: Major > > We should document how the repository is organized, how to build the project > and how to contribute, including: > * Requirements (e.g. go version - 1.10 - dep and operator sdk tools) > * How to setup the environment (e.g. gopath) > * How to build (e.g. various make options) > * How to test built artifacts (e.g. how to run the operator locally) > * General contribution guide -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12788) Camel K: initial effort
[ https://issues.apache.org/jira/browse/CAMEL-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro updated CAMEL-12788: --- Summary: Camel K: initial effort (was: Allow Camel K to be installed easily and document) > Camel K: initial effort > --- > > Key: CAMEL-12788 > URL: https://issues.apache.org/jira/browse/CAMEL-12788 > Project: Camel > Issue Type: Task > Components: camel-k >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Major > > Let's start writing down some tasks for the Camel k project here. Is that ok > [~ancosen]? We should also add a "camel-k" component to Jira. > We have a new repo on github (apache/camel-k) and on docker hub > (apache/camel-k). > I've done a end-to-end test and I'm able to run a integration on Openshift, > but the installation procedure is fairly complex. > Some subtasks created. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12788) Allow Camel K to be installed easily and document
[ https://issues.apache.org/jira/browse/CAMEL-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro updated CAMEL-12788: --- Description: Let's start writing down some tasks for the Camel k project here. Is that ok [~ancosen]? We should also add a "camel-k" component to Jira. We have a new repo on github (apache/camel-k) and on docker hub (apache/camel-k). I've done a end-to-end test and I'm able to run a integration on Openshift, but the installation procedure is fairly complex. Some subtasks created. was: Let's start writing down some tasks for the Camel k project here. Is that ok [~ancosen]? We should also add a "camel-k" component to Jira. We have a new repo on github (apache/camel-k) and on docker hub (apache/camel-k). I've done a end-to-end test and I'm able to run a integration on Openshift, but the installation procedure is fairly complex. We should make sure that installing the Camel-K operator on a namespace is as simple as running "kamel install" with the client tool. Later we can also make the installation optional, as the operator can be installed when the first integration is launched. Documentation is also needed. > Allow Camel K to be installed easily and document > - > > Key: CAMEL-12788 > URL: https://issues.apache.org/jira/browse/CAMEL-12788 > Project: Camel > Issue Type: Task > Components: camel-k >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Major > > Let's start writing down some tasks for the Camel k project here. Is that ok > [~ancosen]? We should also add a "camel-k" component to Jira. > We have a new repo on github (apache/camel-k) and on docker hub > (apache/camel-k). > I've done a end-to-end test and I'm able to run a integration on Openshift, > but the installation procedure is fairly complex. > Some subtasks created. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12800) Camel K: add user guide
Nicola Ferraro created CAMEL-12800: -- Summary: Camel K: add user guide Key: CAMEL-12800 URL: https://issues.apache.org/jira/browse/CAMEL-12800 Project: Camel Issue Type: Sub-task Reporter: Nicola Ferraro We should document what a user needs to do in order to use Camel K (from "kamel run Source.java" on) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12799) Camel K: document architecture
Nicola Ferraro created CAMEL-12799: -- Summary: Camel K: document architecture Key: CAMEL-12799 URL: https://issues.apache.org/jira/browse/CAMEL-12799 Project: Camel Issue Type: Sub-task Reporter: Nicola Ferraro We should document the architecture: * Operator and client, how they interact * Build modes * Publishing modes * The deployment flow -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12798) Camel K: document installation
Nicola Ferraro created CAMEL-12798: -- Summary: Camel K: document installation Key: CAMEL-12798 URL: https://issues.apache.org/jira/browse/CAMEL-12798 Project: Camel Issue Type: Sub-task Reporter: Nicola Ferraro After installation procedure is completed (CAMEL-12789) we should document how to install and caveats (cluster admin rights, etc.) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12797) Camel K: add roadmap information
Nicola Ferraro created CAMEL-12797: -- Summary: Camel K: add roadmap information Key: CAMEL-12797 URL: https://issues.apache.org/jira/browse/CAMEL-12797 Project: Camel Issue Type: Sub-task Reporter: Nicola Ferraro We should add to the documentation a high level roadmap of the project (see nicolaferraro/integration-operator). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12796) Camel K: add dev mode
Nicola Ferraro created CAMEL-12796: -- Summary: Camel K: add dev mode Key: CAMEL-12796 URL: https://issues.apache.org/jira/browse/CAMEL-12796 Project: Camel Issue Type: Sub-task Reporter: Nicola Ferraro It would be nice to mix CAMEL-12794 and CAMEL-12795 to create a "kamel run --dev Source.java" that: * Deploys the integration with a sidecar strategy * Waits for the deployment to be running * Displays the logs in the console * Listen for changes in the source file and triggers a redeploy, so that changes are immediately visible -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12795) Camel K: add wait and log watch options
Nicola Ferraro created CAMEL-12795:
--
Summary: Camel K: add wait and log watch options
Key: CAMEL-12795
URL: https://issues.apache.org/jira/browse/CAMEL-12795
Project: Camel
Issue Type: Sub-task
Reporter: Nicola Ferraro
We should add a flag to "kamel run" to wait for the deployment to be completed
before returning ("–wait").
We should add a "kamel logs" command to display a integration logs. It's a
shorthand for "kubectl logs" and "kubectl logs -f" but Camel K will direct
those commands to the right pod/container using the integration name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12794) Camel K: add sidecar builder strategy
Nicola Ferraro created CAMEL-12794: -- Summary: Camel K: add sidecar builder strategy Key: CAMEL-12794 URL: https://issues.apache.org/jira/browse/CAMEL-12794 Project: Camel Issue Type: Sub-task Reporter: Nicola Ferraro In contexts like plain Kubernetes there's not a default docker registry where images can be pushed. Until we figure-out a strategy to deploy a docker registry, we can fallback on a sidecar builder container. We create a deployment with two containers: * The main container waits for a trigger and start the application * The builder container does a maven build and signal the trigger, then terminates This will be useful also for "--dev" mode (more later). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12793) Camel K: allow buildless direct deploy
Nicola Ferraro created CAMEL-12793: -- Summary: Camel K: allow buildless direct deploy Key: CAMEL-12793 URL: https://issues.apache.org/jira/browse/CAMEL-12793 Project: Camel Issue Type: Sub-task Reporter: Nicola Ferraro The general way of doing builds expects a build phase where a docker image is generated. In some cases, when there are no additional dependencies to load respect to "camel-core" (or respect to a "prebuilt context" we will add in the future), there's no need to build a docker image and we can run the integration directly. We can mount the source file as configmap and load it directly in the runtime. File mounting will also be the preferred strategy when dealing with ".js" files (independently of the build phase). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12791) Camel K: manage dependencies
Nicola Ferraro created CAMEL-12791:
--
Summary: Camel K: manage dependencies
Key: CAMEL-12791
URL: https://issues.apache.org/jira/browse/CAMEL-12791
Project: Camel
Issue Type: Sub-task
Reporter: Nicola Ferraro
When the user executes "kamel run Source.java", he might be using some
components not available in camel-core.
In this case, the "kamel" script should create the resource as usual (do not
put too much logic into the client), while the operator in the "Initialize"
action should scan the source file to find declaration of external maven
dependencies.
We can use a simplified way to declare dependencies, such as declaring them in
a comment, e.g.
{code:java}
// k-include: camel-mail
{code}
This way we let the user specify everything in a single file. We can switch to
something better later (best if recognized by the tooling).
The initializer will add "org.apache.camel:camel-mail" to the list of
dependencies in the CR (custom resource).
We should enable the following ways to include dependencies:
* Comment in the source file
* kamel run --dependency camel-mail Source.java
* Putting it direcly in spec->dependency->items by editing the custom resource
We should also allow to disable the auto-discovery via a flag in
"spec->dependency->autoDiscovery", controlled by a "kamel
--dependency-auto-discovery false" client flag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12790) Camel K: add contributing guide
Nicola Ferraro created CAMEL-12790: -- Summary: Camel K: add contributing guide Key: CAMEL-12790 URL: https://issues.apache.org/jira/browse/CAMEL-12790 Project: Camel Issue Type: Sub-task Reporter: Nicola Ferraro We should document how the repository is organized, how to build the project and how to contribute, including: * Requirements (e.g. go version - 1.10 - dep and operator sdk tools) * How to setup the environment (e.g. gopath) * How to build (e.g. various make options) * How to test built artifacts (e.g. how to run the operator locally) * General contribution guide -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12789) Camel K: add install command
Nicola Ferraro created CAMEL-12789: -- Summary: Camel K: add install command Key: CAMEL-12789 URL: https://issues.apache.org/jira/browse/CAMEL-12789 Project: Camel Issue Type: Sub-task Components: camel-k Reporter: Nicola Ferraro Assignee: Nicola Ferraro We need to add a "kamel install" command that will setup Camel K on a connected cluster. The installation should: * Setup the CRD and permissions at cluster level * Install the operator into the current namespace Setting up the CRD requires cluster-wide permissions, but it is a one-time operation and the script can detect authorization issues and help the user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12788) Allow Camel K to be installed easily and document
Nicola Ferraro created CAMEL-12788: -- Summary: Allow Camel K to be installed easily and document Key: CAMEL-12788 URL: https://issues.apache.org/jira/browse/CAMEL-12788 Project: Camel Issue Type: Task Reporter: Nicola Ferraro Assignee: Nicola Ferraro Let's start writing down some tasks for the Camel k project here. Is that ok [~ancosen]? We should also add a "camel-k" component to Jira. We have a new repo on github (apache/camel-k) and on docker hub (apache/camel-k). I've done a end-to-end test and I'm able to run a integration on Openshift, but the installation procedure is fairly complex. We should make sure that installing the Camel-K operator on a namespace is as simple as running "kamel install" with the client tool. Later we can also make the installation optional, as the operator can be installed when the first integration is launched. Documentation is also needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12522) camel-rxjava2: remove dependency on rx extensions
[ https://issues.apache.org/jira/browse/CAMEL-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12522. Resolution: Fixed Fixed by [~lb]. > camel-rxjava2: remove dependency on rx extensions > - > > Key: CAMEL-12522 > URL: https://issues.apache.org/jira/browse/CAMEL-12522 > Project: Camel > Issue Type: Task >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Minor > Fix For: 2.22.0 > > > RxJava2 MulticastProcessor from extensions has been moved to the main repo: > [https://github.com/ReactiveX/RxJava/pull/6002] > > Once released, we don't need to depend on the extension project anymore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12562) camel-dns: starter ignores serviceCall EIP configuration
[
https://issues.apache.org/jira/browse/CAMEL-12562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506674#comment-16506674
]
Nicola Ferraro commented on CAMEL-12562:
Yes, it may have been a issue with my IDE. This can be closed.
For the last point about Kubernetes, I'm not able to use it in OpenShift.
Setting domain=svc.cluster.local and proto=workshop (namespace), I get the
"inventory" service resolved to "5ea5d395.inventory.workshop.svc.cluster.local"
(CNAME), but port is 0, while it should have been 8080.
There is another schema reported here
[https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#supported-dns-schema|https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#supported-dns-schema.]
(_my-port-name._my-port-protocol.my-svc.my-namespace.svc.cluster.local) but it
seems not usable by camel-dns.
If you "dig", you see that only "_tcp.inventory.workshop.svc.cluster.local" and
"_http._tcp.inventory.workshop.svc.cluster.local" return the correct port
(8080), while the simple address (inventory.workshop.svc.cluster.local) returns
0 as port.
In summary, looking at
[https://github.com/apache/camel/blob/2bbbf36c395eadbbdfcd3c1b7f86bd6dfd35816d/components/camel-dns/src/main/java/org/apache/camel/component/dns/cloud/DnsServiceDiscovery.java#L76],
the pattern used in camel-dns is .., while Kubernetes
uses ...
I wonder if we can make the pattern customizable.
Reference:
{code:java}
/ $ dig inventory.workshop.svc.cluster.local SRV
; <<>> DiG 9.9.5-P1 <<>> inventory.workshop.svc.cluster.local SRV
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32772
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; QUESTION SECTION:
;inventory.workshop.svc.cluster.local. IN SRV
;; ANSWER SECTION:
inventory.workshop.svc.cluster.local. 30 IN SRV 10 100 0
5ea5d395.inventory.workshop.svc.cluster.local.
;; ADDITIONAL SECTION:
5ea5d395.inventory.workshop.svc.cluster.local. 30 IN A 172.30.206.247
;; Query time: 2 msec
;; SERVER: 172.30.0.1#53(172.30.0.1)
;; WHEN: Fri Jun 08 22:54:11 UTC 2018
;; MSG SIZE rcvd: 99
/ $
/ $
/ $
/ $ dig _http._tcp.inventory.workshop.svc.cluster.local SRV
; <<>> DiG 9.9.5-P1 <<>> _http._tcp.inventory.workshop.svc.cluster.local SRV
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10390
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; QUESTION SECTION:
;_http._tcp.inventory.workshop.svc.cluster.local. IN SRV
;; ANSWER SECTION:
_http._tcp.inventory.workshop.svc.cluster.local. 30 IN SRV 10 100 8080
5ea5d395.inventory.workshop.svc.cluster.local.
;; ADDITIONAL SECTION:
5ea5d395.inventory.workshop.svc.cluster.local. 30 IN A 172.30.206.247
;; Query time: 1 msec
;; SERVER: 172.30.0.1#53(172.30.0.1)
;; WHEN: Fri Jun 08 22:54:22 UTC 2018
;; MSG SIZE rcvd: 110
/ $
/ $
/ $
/ $ dig _tcp.inventory.workshop.svc.cluster.local SRV
; <<>> DiG 9.9.5-P1 <<>> _tcp.inventory.workshop.svc.cluster.local SRV
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18193
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; QUESTION SECTION:
;_tcp.inventory.workshop.svc.cluster.local. IN SRV
;; ANSWER SECTION:
_tcp.inventory.workshop.svc.cluster.local. 30 IN SRV 10 100 8080
5ea5d395.inventory.workshop.svc.cluster.local.
;; ADDITIONAL SECTION:
5ea5d395.inventory.workshop.svc.cluster.local. 30 IN A 172.30.206.247
;; Query time: 1 msec
;; SERVER: 172.30.0.1#53(172.30.0.1)
;; WHEN: Fri Jun 08 22:56:35 UTC 2018
;; MSG SIZE rcvd: 104{code}
> camel-dns: starter ignores serviceCall EIP configuration
>
>
> Key: CAMEL-12562
> URL: https://issues.apache.org/jira/browse/CAMEL-12562
> Project: Camel
> Issue Type: Bug
> Components: camel-dns
>Reporter: Nicola Ferraro
>Assignee: Luca Burgazzoli
>Priority: Major
> Fix For: 2.21.2, 2.22.0
>
> Attachments: report.log
>
>
> When setting:
> {code:java}
> camel.cloud.dns.service-discovery.enabled=true
> camel.cloud.dns.service-discovery.domain=svc.cluster.local
> camel.cloud.dns.service-discovery.proto=workshop{code}
> The lookup is not executed with the dns provider.
>
> Instead, if I set it in the route:
> {code:java}
> .serviceCall().name("inventory/api/purchases").dnsServiceDiscovery().domain("svc.cluster.local").proto("workshop");{code}
>
> It at least tries to do the lookup with the DNS provider (although it fails
> to find the service on Kubernetes).
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12562) camel-dns: starter ignores serviceCall EIP configuration
[
https://issues.apache.org/jira/browse/CAMEL-12562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro updated CAMEL-12562:
---
Attachment: report.log
> camel-dns: starter ignores serviceCall EIP configuration
>
>
> Key: CAMEL-12562
> URL: https://issues.apache.org/jira/browse/CAMEL-12562
> Project: Camel
> Issue Type: Bug
> Components: camel-dns
>Reporter: Nicola Ferraro
>Assignee: Luca Burgazzoli
>Priority: Major
> Fix For: 2.21.2, 2.22.0
>
> Attachments: report.log
>
>
> When setting:
> {code:java}
> camel.cloud.dns.service-discovery.enabled=true
> camel.cloud.dns.service-discovery.domain=svc.cluster.local
> camel.cloud.dns.service-discovery.proto=workshop{code}
> The lookup is not executed with the dns provider.
>
> Instead, if I set it in the route:
> {code:java}
> .serviceCall().name("inventory/api/purchases").dnsServiceDiscovery().domain("svc.cluster.local").proto("workshop");{code}
>
> It at least tries to do the lookup with the DNS provider (although it fails
> to find the service on Kubernetes).
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12562) camel-dns: starter ignores serviceCall EIP configuration
[
https://issues.apache.org/jira/browse/CAMEL-12562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506429#comment-16506429
]
Nicola Ferraro commented on CAMEL-12562:
I've put a debug point in DnsServiceDiscovery#getServices. It gets activated
only when I specify the serviceCall parameters in the DSL.
Going to attach the spring-boot report.
> camel-dns: starter ignores serviceCall EIP configuration
>
>
> Key: CAMEL-12562
> URL: https://issues.apache.org/jira/browse/CAMEL-12562
> Project: Camel
> Issue Type: Bug
> Components: camel-dns
>Reporter: Nicola Ferraro
>Assignee: Luca Burgazzoli
>Priority: Major
> Fix For: 2.21.2, 2.22.0
>
>
> When setting:
> {code:java}
> camel.cloud.dns.service-discovery.enabled=true
> camel.cloud.dns.service-discovery.domain=svc.cluster.local
> camel.cloud.dns.service-discovery.proto=workshop{code}
> The lookup is not executed with the dns provider.
>
> Instead, if I set it in the route:
> {code:java}
> .serviceCall().name("inventory/api/purchases").dnsServiceDiscovery().domain("svc.cluster.local").proto("workshop");{code}
>
> It at least tries to do the lookup with the DNS provider (although it fails
> to find the service on Kubernetes).
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12562) camel-dns: starter ignores serviceCall EIP configuration
Nicola Ferraro created CAMEL-12562:
--
Summary: camel-dns: starter ignores serviceCall EIP configuration
Key: CAMEL-12562
URL: https://issues.apache.org/jira/browse/CAMEL-12562
Project: Camel
Issue Type: Bug
Components: camel-dns
Reporter: Nicola Ferraro
Assignee: Luca Burgazzoli
When setting:
{code:java}
camel.cloud.dns.service-discovery.enabled=true
camel.cloud.dns.service-discovery.domain=svc.cluster.local
camel.cloud.dns.service-discovery.proto=workshop{code}
The lookup is not executed with the dns provider.
Instead, if I set it in the route:
{code:java}
.serviceCall().name("inventory/api/purchases").dnsServiceDiscovery().domain("svc.cluster.local").proto("workshop");{code}
It at least tries to do the lookup with the DNS provider (although it fails to
find the service on Kubernetes).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12561) camel-kubernetes: serviceCall EIP throws NullPointerException
Nicola Ferraro created CAMEL-12561:
--
Summary: camel-kubernetes: serviceCall EIP throws
NullPointerException
Key: CAMEL-12561
URL: https://issues.apache.org/jira/browse/CAMEL-12561
Project: Camel
Issue Type: Bug
Components: camel-kubernetes
Affects Versions: 2.21.1
Reporter: Nicola Ferraro
Assignee: Luca Burgazzoli
I've written the following route:
{code:java}
rest().get("/purchases")
.route()
.serviceCall().name("inventory/api/purchases")
.kubernetesServiceDiscovery();{code}
But when I run the service inside Openshift I get:
{code:java}
org.apache.camel.RuntimeCamelException: java.lang.NullPointerException
at
org.apache.camel.component.kubernetes.cloud.KubernetesEnvServiceDiscovery.getServices(KubernetesEnvServiceDiscovery.java:44)
at
org.apache.camel.impl.cloud.DefaultServiceLoadBalancer.process(DefaultServiceLoadBalancer.java:132)
at
org.apache.camel.impl.cloud.DefaultServiceCallProcessor.process(DefaultServiceCallProcessor.java:185)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
at
org.apache.camel.http.common.CamelServlet.doService(CamelServlet.java:208)
at
org.apache.camel.http.common.CamelServlet.service(CamelServlet.java:78)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at
io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
at
org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
at
io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
at
org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:109)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
at
io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
at
org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:81)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
at
io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
at
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:197)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
at
io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
at
io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
at
io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
at
io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:64)
at
io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
at
io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132)
at
io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at
io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
at
io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
at
io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
at
io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
at
[jira] [Created] (CAMEL-12560) camel-kubernetes: serviceCall EIP configuration is not read from application.properties
Nicola Ferraro created CAMEL-12560:
--
Summary: camel-kubernetes: serviceCall EIP configuration is not
read from application.properties
Key: CAMEL-12560
URL: https://issues.apache.org/jira/browse/CAMEL-12560
Project: Camel
Issue Type: Bug
Reporter: Nicola Ferraro
Assignee: Luca Burgazzoli
Configuration of servicecall eip is not read by any starter in camel-kubernetes.
I've put configuration under:
{code:java}
camel.cloud.kubernetes.service-discovery...{code}
But service-call eip ignores it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12555) saga-eip: do not hang if option cannot be computed
[
https://issues.apache.org/jira/browse/CAMEL-12555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro resolved CAMEL-12555.
Resolution: Fixed
> saga-eip: do not hang if option cannot be computed
> --
>
> Key: CAMEL-12555
> URL: https://issues.apache.org/jira/browse/CAMEL-12555
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.21.0, 2.21.1
>Reporter: Nicola Ferraro
>Assignee: Nicola Ferraro
>Priority: Major
> Fix For: 2.22.0
>
>
> Saga-enabled exchanges hang if the expression associated with a option fails.
> We should throw a error and conclude the saga with failure instead.
> {code:java}
> from("timer:tick")
> .saga().option("data", simple("${something / fails}"))
> .log("exchange and saga hang..."){code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12555) saga-eip: do not hang if option cannot be computed
Nicola Ferraro created CAMEL-12555:
--
Summary: saga-eip: do not hang if option cannot be computed
Key: CAMEL-12555
URL: https://issues.apache.org/jira/browse/CAMEL-12555
Project: Camel
Issue Type: Bug
Affects Versions: 2.21.1, 2.21.0
Reporter: Nicola Ferraro
Assignee: Nicola Ferraro
Fix For: 2.22.0
Saga-enabled exchanges hang if the expression associated with a option fails.
We should throw a error and conclude the saga with failure instead.
{code:java}
from("timer:tick")
.saga().option("data", simple("${something / fails}"))
.log("exchange and saga hang..."){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12539) camel-caffeine: improve documentation
Nicola Ferraro created CAMEL-12539:
--
Summary: camel-caffeine: improve documentation
Key: CAMEL-12539
URL: https://issues.apache.org/jira/browse/CAMEL-12539
Project: Camel
Issue Type: Task
Components: camel-caffeine
Affects Versions: 2.21.1
Reporter: Nicola Ferraro
Assignee: Andrea Cosentino
The doc does not state how to check if a result has been found in the cache
("CamelCaffeineActionHasResult").
Some basic examples are also needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12538) camel-caffeine: do not use different caches with slightly different URIs
Nicola Ferraro created CAMEL-12538:
--
Summary: camel-caffeine: do not use different caches with slightly
different URIs
Key: CAMEL-12538
URL: https://issues.apache.org/jira/browse/CAMEL-12538
Project: Camel
Issue Type: Bug
Components: camel-caffeine
Affects Versions: 2.21.1
Reporter: Nicola Ferraro
Assignee: Andrea Cosentino
I've found a problem with caffeine-cache. When I use the following:
{code:java}
// route 1
.to("caffeine-cache:global?key=x=PUT")
// route 2
.to("caffeine-cache:global?key=x=GET"{code}
I expect that what I save in route 1 can be retrieved in route 2, but this is
not the case, since the two URIs differ (GET/PUT) and I get two different
caches.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12522) camel-rxjava2: remove dependency on rx extensions
Nicola Ferraro created CAMEL-12522: -- Summary: camel-rxjava2: remove dependency on rx extensions Key: CAMEL-12522 URL: https://issues.apache.org/jira/browse/CAMEL-12522 Project: Camel Issue Type: Task Reporter: Nicola Ferraro Assignee: Nicola Ferraro Fix For: 2.22.0 RxJava2 MulticastProcessor from extensions has been moved to the main repo: [https://github.com/ReactiveX/RxJava/pull/6002] Once released, we don't need to depend on the extension project anymore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-11114) Create cache DSL
[
https://issues.apache.org/jira/browse/CAMEL-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro reassigned CAMEL-4:
--
Assignee: Nicola Ferraro
> Create cache DSL
>
>
> Key: CAMEL-4
> URL: https://issues.apache.org/jira/browse/CAMEL-4
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, eip
>Reporter: Nicola Ferraro
>Assignee: Nicola Ferraro
>Priority: Major
> Fix For: 2.22.0
>
>
> We should evaluate adding a new "cache" dsl that can be used with all cache
> components in Camel. A default implementation may use also caffeine, included
> in camel-core.
> A possible usage example may be:
> {code}
> from("xxx")
> .cache().on("${header.yyy}").ttl(60) // caches the body
>
> .to("http4://a-service-that-makes-me-pay-for-each-request.com/api/expensive-endpoint")
> .transform().zzz()
>
> .to("http4://or-a-service-that-i-can-call-few-times-a-day.com/api/limited-endpoint")
> .unmarshal()
> .endCache()
> {code}
> It should be also useful to protect internal services when using Camel e.g.
> as a api-gateway (almost what hystrix does in case of failure of the target
> host).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12423) Spring Boot 2 - Upgrade to Spring Boot 2.0.1
Nicola Ferraro created CAMEL-12423: -- Summary: Spring Boot 2 - Upgrade to Spring Boot 2.0.1 Key: CAMEL-12423 URL: https://issues.apache.org/jira/browse/CAMEL-12423 Project: Camel Issue Type: Sub-task Reporter: Nicola Ferraro Fix For: 2.22.0 A new version of spring boot with several fixed has been released. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12387) Spring Boot 2 - Update readme's and documentation
[ https://issues.apache.org/jira/browse/CAMEL-12387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12387. Resolution: Fixed > Spring Boot 2 - Update readme's and documentation > - > > Key: CAMEL-12387 > URL: https://issues.apache.org/jira/browse/CAMEL-12387 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Claus Ibsen >Assignee: Nicola Ferraro >Priority: Major > Fix For: 2.22.0 > > > In the src/main/docs folder of camel-spring-boot we should update that for > SB2. > Also there may be a slight chance that the readme files for the SB examples > that need a bit of update. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12387) Spring Boot 2 - Update readme's and documentation
[ https://issues.apache.org/jira/browse/CAMEL-12387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro reassigned CAMEL-12387: -- Assignee: Nicola Ferraro > Spring Boot 2 - Update readme's and documentation > - > > Key: CAMEL-12387 > URL: https://issues.apache.org/jira/browse/CAMEL-12387 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Claus Ibsen >Assignee: Nicola Ferraro >Priority: Major > Fix For: 2.22.0 > > > In the src/main/docs folder of camel-spring-boot we should update that for > SB2. > Also there may be a slight chance that the readme files for the SB examples > that need a bit of update. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12393) Add karaf feature for camel-lra
[ https://issues.apache.org/jira/browse/CAMEL-12393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12393. Resolution: Fixed > Add karaf feature for camel-lra > --- > > Key: CAMEL-12393 > URL: https://issues.apache.org/jira/browse/CAMEL-12393 > Project: Camel > Issue Type: Improvement >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Major > Fix For: 2.21.1 > > > The lra component can work with both spring-boot and Karaf, but a feature is > missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12377) Spring Boot 2 - Fix the camel-example-spring-boot-rest-jpa
[ https://issues.apache.org/jira/browse/CAMEL-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12377. Resolution: Fixed Fixed as per description because the bug is not related to Camel. > Spring Boot 2 - Fix the camel-example-spring-boot-rest-jpa > -- > > Key: CAMEL-12377 > URL: https://issues.apache.org/jira/browse/CAMEL-12377 > Project: Camel > Issue Type: Sub-task >Reporter: Claus Ibsen >Assignee: Nicola Ferraro >Priority: Major > Fix For: 2.22.0 > > > This example fails with testing as the insertered sample data does not use > the auto-generated key from the JPA entity class, in the data.sql file. If > you add the ID column and use values 1 and 2, then it works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12377) Spring Boot 2 - Fix the camel-example-spring-boot-rest-jpa
[ https://issues.apache.org/jira/browse/CAMEL-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro reassigned CAMEL-12377: -- Assignee: Nicola Ferraro > Spring Boot 2 - Fix the camel-example-spring-boot-rest-jpa > -- > > Key: CAMEL-12377 > URL: https://issues.apache.org/jira/browse/CAMEL-12377 > Project: Camel > Issue Type: Sub-task >Reporter: Claus Ibsen >Assignee: Nicola Ferraro >Priority: Major > Fix For: 2.22.0 > > > This example fails with testing as the insertered sample data does not use > the auto-generated key from the JPA entity class, in the data.sql file. If > you add the ID column and use values 1 and 2, then it works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12393) Add karaf feature for camel-lra
Nicola Ferraro created CAMEL-12393: -- Summary: Add karaf feature for camel-lra Key: CAMEL-12393 URL: https://issues.apache.org/jira/browse/CAMEL-12393 Project: Camel Issue Type: Improvement Reporter: Nicola Ferraro Assignee: Nicola Ferraro Fix For: 2.21.1 The lra component can work with both spring-boot and Karaf, but a feature is missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12380) Spring Boot 2 - Remove dependency on code ported from 1.5.x
[ https://issues.apache.org/jira/browse/CAMEL-12380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12380. Resolution: Fixed Spring-boot 2 has a different way to bind properties, old 1.5.x was "too relaxed". I've removed the relaxed property resolver and replaced it with the new "Binder". > Spring Boot 2 - Remove dependency on code ported from 1.5.x > --- > > Key: CAMEL-12380 > URL: https://issues.apache.org/jira/browse/CAMEL-12380 > Project: Camel > Issue Type: Sub-task >Reporter: Nicola Ferraro >Assignee: Nicola Ferraro >Priority: Minor > > Looks like some code ported from 1.5.x was necessary to support compatibility > of both spring-boot 1 and spring-boot 2, but we can rely on v2-only code now. > > E.g. RelaxedPropertyResolver is not necessary if using [canonical > properties|https://github.com/spring-projects/spring-boot/wiki/Canonical-properties#spring-boot-20-canonical-properties]. > > Others classes currently forward-ported: > - PropertySourceUtils > - RelaxedNames -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12372) Spring Boot 2 - Fix the tests/camel-itest-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-12372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406148#comment-16406148 ] Nicola Ferraro commented on CAMEL-12372: Ok, @Ignored and added reactor test back. > Spring Boot 2 - Fix the tests/camel-itest-spring-boot > - > > Key: CAMEL-12372 > URL: https://issues.apache.org/jira/browse/CAMEL-12372 > Project: Camel > Issue Type: Sub-task >Reporter: Claus Ibsen >Assignee: Nicola Ferraro >Priority: Major > Fix For: 2.22.0 > > > These tests fails when running from maven command line. But you can run and > have the test working if you run from IDEA as unit test, eg right click > CamelBeanioTest etc and run it as unit test from within the editor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12372) Spring Boot 2 - Fix the tests/camel-itest-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-12372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406074#comment-16406074 ] Nicola Ferraro commented on CAMEL-12372: Yes, I left them without changes because I've seen they're using milestone versions. Maybe I better fix them by adding the milestone repo to the list as spring-boot 2 is using a unreleased version for some spring-cloud artifacts... > Spring Boot 2 - Fix the tests/camel-itest-spring-boot > - > > Key: CAMEL-12372 > URL: https://issues.apache.org/jira/browse/CAMEL-12372 > Project: Camel > Issue Type: Sub-task >Reporter: Claus Ibsen >Assignee: Nicola Ferraro >Priority: Major > Fix For: 2.22.0 > > > These tests fails when running from maven command line. But you can run and > have the test working if you run from IDEA as unit test, eg right click > CamelBeanioTest etc and run it as unit test from within the editor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12372) Spring Boot 2 - Fix the tests/camel-itest-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-12372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro resolved CAMEL-12372. Resolution: Fixed Fixed and run all tests. Added the following dependencies to starters (they are needed by main artifacts, not by tests): * org.hibernate.validator:hibernate-validator to camel-kubernetes-starter and camel-swagger-java-starter * io.undertow:undertow-servlet to camel-undertow-starter > Spring Boot 2 - Fix the tests/camel-itest-spring-boot > - > > Key: CAMEL-12372 > URL: https://issues.apache.org/jira/browse/CAMEL-12372 > Project: Camel > Issue Type: Sub-task >Reporter: Claus Ibsen >Assignee: Nicola Ferraro >Priority: Major > Fix For: 2.22.0 > > > These tests fails when running from maven command line. But you can run and > have the test working if you run from IDEA as unit test, eg right click > CamelBeanioTest etc and run it as unit test from within the editor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12380) Spring Boot 2 - Remove dependency on code ported from 1.5.x
Nicola Ferraro created CAMEL-12380: -- Summary: Spring Boot 2 - Remove dependency on code ported from 1.5.x Key: CAMEL-12380 URL: https://issues.apache.org/jira/browse/CAMEL-12380 Project: Camel Issue Type: Improvement Reporter: Nicola Ferraro Assignee: Nicola Ferraro Looks like some code ported from 1.5.x was necessary to support compatibility of both spring-boot 1 and spring-boot 2, but we can rely on v2-only code now. E.g. RelaxedPropertyResolver is not necessary if using [canonical properties|https://github.com/spring-projects/spring-boot/wiki/Canonical-properties#spring-boot-20-canonical-properties]. Others classes currently forward-ported: - PropertySourceUtils - RelaxedNames -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12372) Spring Boot 2 - Fix the tests/camel-itest-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-12372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Ferraro reassigned CAMEL-12372: -- Assignee: Nicola Ferraro > Spring Boot 2 - Fix the tests/camel-itest-spring-boot > - > > Key: CAMEL-12372 > URL: https://issues.apache.org/jira/browse/CAMEL-12372 > Project: Camel > Issue Type: Sub-task >Reporter: Claus Ibsen >Assignee: Nicola Ferraro >Priority: Major > Fix For: 2.22.0 > > > These tests fails when running from maven command line. But you can run and > have the test working if you run from IDEA as unit test, eg right click > CamelBeanioTest etc and run it as unit test from within the editor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
