[jira] [Commented] (CAMEL-15288) Camel OSGi: Allow for defining the Bean resolution order
[ https://issues.apache.org/jira/browse/CAMEL-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541283#comment-17541283 ] Jean-Baptiste Onofré commented on CAMEL-15288: -- Yes, I think it's OK now. I close this Jira for now, let's reopen it if we need some updates. > Camel OSGi: Allow for defining the Bean resolution order > > > Key: CAMEL-15288 > URL: https://issues.apache.org/jira/browse/CAMEL-15288 > Project: Camel > Issue Type: Improvement > Components: camel-osgi >Affects Versions: 2.24.3 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Currently OsgiDefaultCamelContext updates the registry and inserts > OsgiServiceRegistry as the _first_ registry into the list. > This can lead to undesirable behaviour, so an option to define the resolution > order will be helpful. > For example, it can be more appropriate to lookup local beans first, only go > to lookup an OSGi service if no local bean is found. Or it could be desired > to not lookup OSGi services at all. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-15288) Camel OSGi: Allow for defining the Bean resolution order
[ https://issues.apache.org/jira/browse/CAMEL-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved CAMEL-15288. -- Resolution: Invalid > Camel OSGi: Allow for defining the Bean resolution order > > > Key: CAMEL-15288 > URL: https://issues.apache.org/jira/browse/CAMEL-15288 > Project: Camel > Issue Type: Improvement > Components: camel-osgi >Affects Versions: 2.24.3 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Currently OsgiDefaultCamelContext updates the registry and inserts > OsgiServiceRegistry as the _first_ registry into the list. > This can lead to undesirable behaviour, so an option to define the resolution > order will be helpful. > For example, it can be more appropriate to lookup local beans first, only go > to lookup an OSGi service if no local bean is found. Or it could be desired > to not lookup OSGi services at all. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-15288) Camel OSGi: Allow for defining the Bean resolution order
[ https://issues.apache.org/jira/browse/CAMEL-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541278#comment-17541278 ] Martin Lichtin commented on CAMEL-15288: The behavior in 3.14 has changed and this may no longer be relevant.. > Camel OSGi: Allow for defining the Bean resolution order > > > Key: CAMEL-15288 > URL: https://issues.apache.org/jira/browse/CAMEL-15288 > Project: Camel > Issue Type: Improvement > Components: camel-osgi >Affects Versions: 2.24.3 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Currently OsgiDefaultCamelContext updates the registry and inserts > OsgiServiceRegistry as the _first_ registry into the list. > This can lead to undesirable behaviour, so an option to define the resolution > order will be helpful. > For example, it can be more appropriate to lookup local beans first, only go > to lookup an OSGi service if no local bean is found. Or it could be desired > to not lookup OSGi services at all. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18139) camel-jbang - Run from clipboard does not work for java
[
https://issues.apache.org/jira/browse/CAMEL-18139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18139.
-
Assignee: Claus Ibsen
Resolution: Fixed
> camel-jbang - Run from clipboard does not work for java
> ---
>
> Key: CAMEL-18139
> URL: https://issues.apache.org/jira/browse/CAMEL-18139
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.17.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.0
>
>
> 2022-05-23 20:21:39.543 INFO 29065 --- [ main]
> org.apache.camel.main.DownloaderHelper : Downloaded:
> org.apache.camel:camel-java-joor-dsl:3.18.0-SNAPSHOT (took: 1s414ms)
> org.joor.ReflectException: Compilation error: /generated-clipboard.java:4:
> error: class Hey is public, should be declared in a file named Hey.java
> public class Hey extends org.apache.camel.builder.RouteBuilder {
>^
> 1 error
> at
> org.apache.camel.dsl.java.joor.MultiCompile.compileUnit(MultiCompile.java:130)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (CAMEL-14880) Create a camel-couchdb3 component
[
https://issues.apache.org/jira/browse/CAMEL-14880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541148#comment-17541148
]
Arcadius Ahouansou edited comment on CAMEL-14880 at 5/23/22 8:29 PM:
-
Just to mention that there is a drop-in replacement for lightcouch
[https://github.com/IndabaConsultores/LightCouch]
I used it with camel 2.25.4 and
couchdb v. 2.3.0 and v. 3.2.2
and it seems to be working for me
{code:java}
implementation("org.apache.camel:camel-couchdb:${camelVersion}") {
exclude group: 'org.lightcouch', module: 'lightcouch'
}
implementation("com.github.IndabaConsultores:lightCouch:0.3.0"){code}
was (Author: arcadius):
Just to mention that there is a drop-in replacement for lightcouch
[https://github.com/IndabaConsultores/LightCouch]
I used it with camel 2.25.4 and couchdb 3 and it seems to be working for me
{code:java}
implementation("org.apache.camel:camel-couchdb:${camelVersion}") {
exclude group: 'org.lightcouch', module: 'lightcouch'
}
implementation("com.github.IndabaConsultores:lightCouch:0.3.0"){code}
> Create a camel-couchdb3 component
> -
>
> Key: CAMEL-14880
> URL: https://issues.apache.org/jira/browse/CAMEL-14880
> Project: Camel
> Issue Type: New Feature
>Affects Versions: 3.2.0
>Reporter: Alex Dettinger
>Priority: Minor
> Fix For: 3.x
>
>
> As per the context of
> [CAMEL-14822|https://issues.apache.org/jira/browse/CAMEL-14822], the
> camel-couchdb component is exposed to the de-facto end of life of the
> underlying couchdb library. As such, camel currently offers no support to
> couchdb 3.x.
> A way of dealing with such situation would be to create a camel-couchdb3
> component on top of [java-cloudant|https://github.com/cloudant/java-cloudant].
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CAMEL-14880) Create a camel-couchdb3 component
[
https://issues.apache.org/jira/browse/CAMEL-14880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541148#comment-17541148
]
Arcadius Ahouansou commented on CAMEL-14880:
Just to mention that there is a drop-in replacement for lightcouch
[https://github.com/IndabaConsultores/LightCouch]
I used it with camel 2.25.4 and couchdb 3 and it seems to be working for me
{code:java}
implementation("org.apache.camel:camel-couchdb:${camelVersion}") {
exclude group: 'org.lightcouch', module: 'lightcouch'
}
implementation("com.github.IndabaConsultores:lightCouch:0.3.0"){code}
> Create a camel-couchdb3 component
> -
>
> Key: CAMEL-14880
> URL: https://issues.apache.org/jira/browse/CAMEL-14880
> Project: Camel
> Issue Type: New Feature
>Affects Versions: 3.2.0
>Reporter: Alex Dettinger
>Priority: Minor
> Fix For: 3.x
>
>
> As per the context of
> [CAMEL-14822|https://issues.apache.org/jira/browse/CAMEL-14822], the
> camel-couchdb component is exposed to the de-facto end of life of the
> underlying couchdb library. As such, camel currently offers no support to
> couchdb 3.x.
> A way of dealing with such situation would be to create a camel-couchdb3
> component on top of [java-cloudant|https://github.com/cloudant/java-cloudant].
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CAMEL-18139) camel-jbang - Run from clipboard does not work for java
[
https://issues.apache.org/jira/browse/CAMEL-18139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541084#comment-17541084
]
Claus Ibsen commented on CAMEL-18139:
-
This is because the compiler expects the content to be in a file with the class
name
> camel-jbang - Run from clipboard does not work for java
> ---
>
> Key: CAMEL-18139
> URL: https://issues.apache.org/jira/browse/CAMEL-18139
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.17.0
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.0
>
>
> 2022-05-23 20:21:39.543 INFO 29065 --- [ main]
> org.apache.camel.main.DownloaderHelper : Downloaded:
> org.apache.camel:camel-java-joor-dsl:3.18.0-SNAPSHOT (took: 1s414ms)
> org.joor.ReflectException: Compilation error: /generated-clipboard.java:4:
> error: class Hey is public, should be declared in a file named Hey.java
> public class Hey extends org.apache.camel.builder.RouteBuilder {
>^
> 1 error
> at
> org.apache.camel.dsl.java.joor.MultiCompile.compileUnit(MultiCompile.java:130)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18139) camel-jbang - Run from clipboard does not work for java
[
https://issues.apache.org/jira/browse/CAMEL-18139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18139:
Issue Type: Bug (was: Task)
> camel-jbang - Run from clipboard does not work for java
> ---
>
> Key: CAMEL-18139
> URL: https://issues.apache.org/jira/browse/CAMEL-18139
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.17.0
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 3.18.0
>
>
> 2022-05-23 20:21:39.543 INFO 29065 --- [ main]
> org.apache.camel.main.DownloaderHelper : Downloaded:
> org.apache.camel:camel-java-joor-dsl:3.18.0-SNAPSHOT (took: 1s414ms)
> org.joor.ReflectException: Compilation error: /generated-clipboard.java:4:
> error: class Hey is public, should be declared in a file named Hey.java
> public class Hey extends org.apache.camel.builder.RouteBuilder {
>^
> 1 error
> at
> org.apache.camel.dsl.java.joor.MultiCompile.compileUnit(MultiCompile.java:130)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (CAMEL-18139) camel-jbang - Run from clipboard and compiling to java
Claus Ibsen created CAMEL-18139:
---
Summary: camel-jbang - Run from clipboard and compiling to java
Key: CAMEL-18139
URL: https://issues.apache.org/jira/browse/CAMEL-18139
Project: Camel
Issue Type: Task
Components: camel-jbang
Affects Versions: 3.17.0
Reporter: Claus Ibsen
Fix For: 3.18.0
2022-05-23 20:21:39.543 INFO 29065 --- [ main]
org.apache.camel.main.DownloaderHelper : Downloaded:
org.apache.camel:camel-java-joor-dsl:3.18.0-SNAPSHOT (took: 1s414ms)
org.joor.ReflectException: Compilation error: /generated-clipboard.java:4:
error: class Hey is public, should be declared in a file named Hey.java
public class Hey extends org.apache.camel.builder.RouteBuilder {
^
1 error
at
org.apache.camel.dsl.java.joor.MultiCompile.compileUnit(MultiCompile.java:130)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18139) camel-jbang - Run from clipboard does not work for java
[
https://issues.apache.org/jira/browse/CAMEL-18139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18139:
Summary: camel-jbang - Run from clipboard does not work for java (was:
camel-jbang - Run from clipboard and compiling to java)
> camel-jbang - Run from clipboard does not work for java
> ---
>
> Key: CAMEL-18139
> URL: https://issues.apache.org/jira/browse/CAMEL-18139
> Project: Camel
> Issue Type: Task
> Components: camel-jbang
>Affects Versions: 3.17.0
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 3.18.0
>
>
> 2022-05-23 20:21:39.543 INFO 29065 --- [ main]
> org.apache.camel.main.DownloaderHelper : Downloaded:
> org.apache.camel:camel-java-joor-dsl:3.18.0-SNAPSHOT (took: 1s414ms)
> org.joor.ReflectException: Compilation error: /generated-clipboard.java:4:
> error: class Hey is public, should be declared in a file named Hey.java
> public class Hey extends org.apache.camel.builder.RouteBuilder {
>^
> 1 error
> at
> org.apache.camel.dsl.java.joor.MultiCompile.compileUnit(MultiCompile.java:130)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18139) camel-jbang - Run from clipboard does not work for java
[
https://issues.apache.org/jira/browse/CAMEL-18139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18139:
Priority: Minor (was: Major)
> camel-jbang - Run from clipboard does not work for java
> ---
>
> Key: CAMEL-18139
> URL: https://issues.apache.org/jira/browse/CAMEL-18139
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.17.0
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.0
>
>
> 2022-05-23 20:21:39.543 INFO 29065 --- [ main]
> org.apache.camel.main.DownloaderHelper : Downloaded:
> org.apache.camel:camel-java-joor-dsl:3.18.0-SNAPSHOT (took: 1s414ms)
> org.joor.ReflectException: Compilation error: /generated-clipboard.java:4:
> error: class Hey is public, should be declared in a file named Hey.java
> public class Hey extends org.apache.camel.builder.RouteBuilder {
>^
> 1 error
> at
> org.apache.camel.dsl.java.joor.MultiCompile.compileUnit(MultiCompile.java:130)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (CAMEL-18070) camel-core - Simple - Make it easy to check if property placeholder exists or not
[
https://issues.apache.org/jira/browse/CAMEL-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18070.
-
Resolution: Fixed
> camel-core - Simple - Make it easy to check if property placeholder exists or
> not
> -
>
> Key: CAMEL-18070
> URL: https://issues.apache.org/jira/browse/CAMEL-18070
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.18.0
>
>
> To make it easy to check that keyName exists or not.
> Well its easy to check if it exists but not the opposite
> {{?keyName}}
> We need a not argument for this
> {{?keyName}} == null
> Or something ala
> {{!keyName}}
> ${properties:!keyName}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CAMEL-18070) camel-core - Simple - Make it easy to check if property placeholder exists or not
[
https://issues.apache.org/jira/browse/CAMEL-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540998#comment-17540998
]
Claus Ibsen commented on CAMEL-18070:
-
There is a new propertiesExist function
${propertiesExist:keyName}
And to check for NOT exists you prefix with !
${propertiesExist:!keyName}
> camel-core - Simple - Make it easy to check if property placeholder exists or
> not
> -
>
> Key: CAMEL-18070
> URL: https://issues.apache.org/jira/browse/CAMEL-18070
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.18.0
>
>
> To make it easy to check that keyName exists or not.
> Well its easy to check if it exists but not the opposite
> {{?keyName}}
> We need a not argument for this
> {{?keyName}} == null
> Or something ala
> {{!keyName}}
> ${properties:!keyName}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (CAMEL-18070) camel-core - Simple - Make it easy to check if property placeholder exists or not
[
https://issues.apache.org/jira/browse/CAMEL-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-18070:
---
Assignee: Claus Ibsen
> camel-core - Simple - Make it easy to check if property placeholder exists or
> not
> -
>
> Key: CAMEL-18070
> URL: https://issues.apache.org/jira/browse/CAMEL-18070
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.18.0
>
>
> To make it easy to check that keyName exists or not.
> Well its easy to check if it exists but not the opposite
> {{?keyName}}
> We need a not argument for this
> {{?keyName}} == null
> Or something ala
> {{!keyName}}
> ${properties:!keyName}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CAMEL-14631) Support custom type converters for Enums
[ https://issues.apache.org/jira/browse/CAMEL-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540988#comment-17540988 ] Steven Wyatt commented on CAMEL-14631: -- This used to work all the way up to 2.19.5. We are trying to upgrade to 2.20.4 and our enum type converter is no longer called. > Support custom type converters for Enums > > > Key: CAMEL-14631 > URL: https://issues.apache.org/jira/browse/CAMEL-14631 > Project: Camel > Issue Type: Improvement > Components: came-core >Reporter: Ralf Claussnitzer >Priority: Minor > > It should be possible to provide a custom TypeConverter for converting > strings into an Enum instances. > The conversion of `String` to `Enum` is hard coded to fail with an Exception > if `EnumTypeConverter` cannot instantiate an `Enum` constant by name. > However, Java allows to override the string representation for enums. > Converting such strings back to enums is only possible through a special > converting function. > Currently `org.apache.camel.impl.converter.EnumTypeConverter` tries to find > the Enum instance by name. If that fails it falls back to calling the > built-in valueOf(String) method which will end the program with a > RuntimeException. The type conversion process stops there instead of further > looking for custom type converters. The line with `return null;` in > `EnumTypeConverter` is never reached. Would `EnumTypeConverter` indeed return > null, the process would continue and a custom converter would finally be > called. > * > https://mail-archives.apache.org/mod_mbox/camel-dev/202002.mbox/%3Cc87cef78-9709-5b92-efee-9bf0e2c2370d%40slub-dresden.de%3E -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18070) camel-core - Simple - Make it easy to check if property placeholder exists or not
[
https://issues.apache.org/jira/browse/CAMEL-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18070:
Fix Version/s: 3.18.0
(was: 3.x)
> camel-core - Simple - Make it easy to check if property placeholder exists or
> not
> -
>
> Key: CAMEL-18070
> URL: https://issues.apache.org/jira/browse/CAMEL-18070
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 3.18.0
>
>
> To make it easy to check that keyName exists or not.
> Well its easy to check if it exists but not the opposite
> {{?keyName}}
> We need a not argument for this
> {{?keyName}} == null
> Or something ala
> {{!keyName}}
> ${properties:!keyName}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (CAMEL-18073) camel-jbang - Add openapi modeline
[ https://issues.apache.org/jira/browse/CAMEL-18073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18073. - Resolution: Won't Fix > camel-jbang - Add openapi modeline > -- > > Key: CAMEL-18073 > URL: https://issues.apache.org/jira/browse/CAMEL-18073 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > We have support for --open-api now, but we can also add this to > camel-dsl-modeline > https://camel.apache.org/camel-k/1.9.x/cli/modeline.html -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-18073) camel-jbang - Add openapi modeline
[ https://issues.apache.org/jira/browse/CAMEL-18073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540984#comment-17540984 ] Claus Ibsen commented on CAMEL-18073: - This is more difficult to do as the openapi currently is executed before camel main starts. > camel-jbang - Add openapi modeline > -- > > Key: CAMEL-18073 > URL: https://issues.apache.org/jira/browse/CAMEL-18073 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > We have support for --open-api now, but we can also add this to > camel-dsl-modeline > https://camel.apache.org/camel-k/1.9.x/cli/modeline.html -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18031) camel-karaf - Upgrade to 4.4.0
[ https://issues.apache.org/jira/browse/CAMEL-18031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18031: Description: Karaf 4.4.0 is released. (was: Karaf 2.4.0 is released.) > camel-karaf - Upgrade to 4.4.0 > -- > > Key: CAMEL-18031 > URL: https://issues.apache.org/jira/browse/CAMEL-18031 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-karaf >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.18.0 > > > Karaf 4.4.0 is released. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18031) camel-karaf - Upgrade to 4.4.0
[ https://issues.apache.org/jira/browse/CAMEL-18031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18031: Summary: camel-karaf - Upgrade to 4.4.0 (was: camel-karaf - Upgrade to 2.4.0) > camel-karaf - Upgrade to 4.4.0 > -- > > Key: CAMEL-18031 > URL: https://issues.apache.org/jira/browse/CAMEL-18031 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-karaf >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.18.0 > > > Karaf 2.4.0 is released. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (CAMEL-18092) Support reload with Camel JBang with files specified with a specific path
[
https://issues.apache.org/jira/browse/CAMEL-18092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-18092:
---
Assignee: Claus Ibsen
> Support reload with Camel JBang with files specified with a specific path
> -
>
> Key: CAMEL-18092
> URL: https://issues.apache.org/jira/browse/CAMEL-18092
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 3.16.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
>
> Given this route in subfolder src/main/java/org/acme/timer/log :
> {noformat}
> package org.acme.timer.log;
> import org.apache.camel.builder.RouteBuilder;
> public class TimerRoute extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:foo?period=1000")
> .log("Hello World a first time")
> .log("Helloss World a second time - modified ");
> }
> }
> {noformat}
> when calling:
> {noformat}
> jbang -Dcamel.jbang.version=3.17.0-SNAPSHOT camel@apache/camel run
> src/main/java/org/acme/timer/log/TimerRoute.java --logging-level=info
> --reload --dep=org.apache.camel:camel-debug{noformat}
> when modifying the route and saving it, the route is not restarted.
> Given that the file path has been provided, the reload shoudl be able to
> watch for it even if it is in a subfolder
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18092) Support reload with Camel JBang with files specified with a specific path
[
https://issues.apache.org/jira/browse/CAMEL-18092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18092:
Fix Version/s: 3.18.0
> Support reload with Camel JBang with files specified with a specific path
> -
>
> Key: CAMEL-18092
> URL: https://issues.apache.org/jira/browse/CAMEL-18092
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 3.16.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.0
>
>
> Given this route in subfolder src/main/java/org/acme/timer/log :
> {noformat}
> package org.acme.timer.log;
> import org.apache.camel.builder.RouteBuilder;
> public class TimerRoute extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:foo?period=1000")
> .log("Hello World a first time")
> .log("Helloss World a second time - modified ");
> }
> }
> {noformat}
> when calling:
> {noformat}
> jbang -Dcamel.jbang.version=3.17.0-SNAPSHOT camel@apache/camel run
> src/main/java/org/acme/timer/log/TimerRoute.java --logging-level=info
> --reload --dep=org.apache.camel:camel-debug{noformat}
> when modifying the route and saving it, the route is not restarted.
> Given that the file path has been provided, the reload shoudl be able to
> watch for it even if it is in a subfolder
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18096) camel-kafka - Introduce TX options for kafka transaction
[ https://issues.apache.org/jira/browse/CAMEL-18096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18096: Fix Version/s: 3.18.0 > camel-kafka - Introduce TX options for kafka transaction > > > Key: CAMEL-18096 > URL: https://issues.apache.org/jira/browse/CAMEL-18096 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Reporter: Zheng Feng >Assignee: Zheng Feng >Priority: Major > Fix For: 3.18.0 > > > Currently it needs to use *addtional-properties* to enable kafka transaction. > It would be good if we could make configuring the TX options as new endpoint > options so its easier and more tooling friendly. Additional properties is > only intended for special and rare use-cases. > > * transactionalId -> addtional-properties[transactional.id] > * idempotence -> additional-properties[enable.idempotence] > * retries -> additional-properties[retries] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18112) Support trace breakpoint
[ https://issues.apache.org/jira/browse/CAMEL-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18112: Component/s: tooling > Support trace breakpoint > > > Key: CAMEL-18112 > URL: https://issues.apache.org/jira/browse/CAMEL-18112 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Aurélien Pupier >Priority: Minor > > it would be nice to support trace breakpoints. > Most IDEs are providing this kind of feature. It allows to provide traces > during a debug session without modifying the source code. > see: > - > https://microsoft.github.io/debug-adapter-protocol/specification#Types_SourceBreakpoint > logMessage > - In IntelliJ, using non-suspended in combination with logging options > https://www.jetbrains.com/help/idea/using-breakpoints.html#suspend_policy > - In Eclipse, Tracepoint > https://www.eclipse.org/community/eclipse_newsletter/2017/june/article1.php > - In VS Code, Logpoint > https://code.visualstudio.com/docs/editor/debugging#_logpoints -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18116) camel-spring-boot-examples - twitter-salesforce - not working
[
https://issues.apache.org/jira/browse/CAMEL-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18116.
-
Fix Version/s: 3.18.0
Resolution: Fixed
Thanks for the PR - keep them coming
> camel-spring-boot-examples - twitter-salesforce - not working
> -
>
> Key: CAMEL-18116
> URL: https://issues.apache.org/jira/browse/CAMEL-18116
> Project: Camel
> Issue Type: Task
> Components: examples
>Reporter: Federico Mariani
>Assignee: Federico Mariani
>Priority: Minor
> Fix For: 3.18.0
>
>
> The example is not working because the annotations {_}@{_}_JsonProperty_ are
> not picked up from the property, but getter and setter with _@JsonProperty_
> should be added
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (CAMEL-18116) camel-spring-boot-examples - twitter-salesforce - not working
[
https://issues.apache.org/jira/browse/CAMEL-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-18116:
---
Assignee: Federico Mariani
> camel-spring-boot-examples - twitter-salesforce - not working
> -
>
> Key: CAMEL-18116
> URL: https://issues.apache.org/jira/browse/CAMEL-18116
> Project: Camel
> Issue Type: Task
> Components: examples
>Reporter: Federico Mariani
>Assignee: Federico Mariani
>Priority: Minor
>
> The example is not working because the annotations {_}@{_}_JsonProperty_ are
> not picked up from the property, but getter and setter with _@JsonProperty_
> should be added
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (CAMEL-18117) camel-jbang - Package uber-jar should include application.properties if present
[ https://issues.apache.org/jira/browse/CAMEL-18117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540862#comment-17540862 ] Claus Ibsen edited comment on CAMEL-18117 at 5/23/22 1:47 PM: -- TODO: documentation about profile *DONE* was (Author: davsclaus): TODO: documentation about profile > camel-jbang - Package uber-jar should include application.properties if > present > --- > > Key: CAMEL-18117 > URL: https://issues.apache.org/jira/browse/CAMEL-18117 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 3.17.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > So you can automatic include application.properties when doing a package > uber-jar -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18117) camel-jbang - Package uber-jar should include application.properties if present
[ https://issues.apache.org/jira/browse/CAMEL-18117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18117. - Resolution: Fixed > camel-jbang - Package uber-jar should include application.properties if > present > --- > > Key: CAMEL-18117 > URL: https://issues.apache.org/jira/browse/CAMEL-18117 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 3.17.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > So you can automatic include application.properties when doing a package > uber-jar -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18138) camel-spring - XSD schema not updated in right path on website
[ https://issues.apache.org/jira/browse/CAMEL-18138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18138. - Resolution: Fixed https://github.com/apache/camel-website/commit/262e64e660678a99377fb19b4bfb41d885060d70 > camel-spring - XSD schema not updated in right path on website > -- > > Key: CAMEL-18138 > URL: https://issues.apache.org/jira/browse/CAMEL-18138 > Project: Camel > Issue Type: Task > Components: camel-spring >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.17.0 > > > Reported on chat > https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Latest.20camel-spring.2Exsd.20versions -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18138) camel-spring - XSD schema not updated in right path on website
Claus Ibsen created CAMEL-18138: --- Summary: camel-spring - XSD schema not updated in right path on website Key: CAMEL-18138 URL: https://issues.apache.org/jira/browse/CAMEL-18138 Project: Camel Issue Type: Task Components: camel-spring Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.17.0 Reported on chat https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Latest.20camel-spring.2Exsd.20versions -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-18117) camel-jbang - Package uber-jar should include application.properties if present
[ https://issues.apache.org/jira/browse/CAMEL-18117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540862#comment-17540862 ] Claus Ibsen commented on CAMEL-18117: - TODO: documentation about profile > camel-jbang - Package uber-jar should include application.properties if > present > --- > > Key: CAMEL-18117 > URL: https://issues.apache.org/jira/browse/CAMEL-18117 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 3.17.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > So you can automatic include application.properties when doing a package > uber-jar -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-18117) camel-jbang - Package uber-jar should include application.properties if present
[ https://issues.apache.org/jira/browse/CAMEL-18117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540819#comment-17540819 ] Claus Ibsen commented on CAMEL-18117: - Yes we should use profiles > camel-jbang - Package uber-jar should include application.properties if > present > --- > > Key: CAMEL-18117 > URL: https://issues.apache.org/jira/browse/CAMEL-18117 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 3.17.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > So you can automatic include application.properties when doing a package > uber-jar -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18137) camel-mongodb - Cannot upsert in sharded collection
[
https://issues.apache.org/jira/browse/CAMEL-18137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18137:
Affects Version/s: 3.17.0
> camel-mongodb - Cannot upsert in sharded collection
> ---
>
> Key: CAMEL-18137
> URL: https://issues.apache.org/jira/browse/CAMEL-18137
> Project: Camel
> Issue Type: Bug
> Components: camel-mongodb
>Affects Versions: 3.17.0
>Reporter: Kanstantsin Ihnatsenka
>Priority: Major
> Fix For: 3.18.0
>
>
> According to official mongodb documentation sharded key should be specified
> while upserting:
> https://www.mongodb.com/docs/manual/reference/method/db.collection.updateOne/
> {code:java}
> If you specify upsert: true on a sharded collection, you must include the
> full shard key in the filter. For additional db.collection.updateOne()
> behavior on a sharded collection, see Sharded Collections.{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18137) camel-mongodb - Cannot upsert in sharded collection
[
https://issues.apache.org/jira/browse/CAMEL-18137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18137:
Fix Version/s: 3.18.0
> camel-mongodb - Cannot upsert in sharded collection
> ---
>
> Key: CAMEL-18137
> URL: https://issues.apache.org/jira/browse/CAMEL-18137
> Project: Camel
> Issue Type: Bug
> Components: camel-mongodb
>Reporter: Kanstantsin Ihnatsenka
>Priority: Major
> Fix For: 3.18.0
>
>
> According to official mongodb documentation sharded key should be specified
> while upserting:
> https://www.mongodb.com/docs/manual/reference/method/db.collection.updateOne/
> {code:java}
> If you specify upsert: true on a sharded collection, you must include the
> full shard key in the filter. For additional db.collection.updateOne()
> behavior on a sharded collection, see Sharded Collections.{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18137) camel-mongodb - Cannot upsert in sharded collection
[
https://issues.apache.org/jira/browse/CAMEL-18137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18137:
Summary: camel-mongodb - Cannot upsert in sharded collection (was: Cannot
upsert in sharded collection)
> camel-mongodb - Cannot upsert in sharded collection
> ---
>
> Key: CAMEL-18137
> URL: https://issues.apache.org/jira/browse/CAMEL-18137
> Project: Camel
> Issue Type: Bug
> Components: camel-mongodb
>Reporter: Kanstantsin Ihnatsenka
>Priority: Major
>
> According to official mongodb documentation sharded key should be specified
> while upserting:
> https://www.mongodb.com/docs/manual/reference/method/db.collection.updateOne/
> {code:java}
> If you specify upsert: true on a sharded collection, you must include the
> full shard key in the filter. For additional db.collection.updateOne()
> behavior on a sharded collection, see Sharded Collections.{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CAMEL-18116) camel-spring-boot-examples - twitter-salesforce - not working
[
https://issues.apache.org/jira/browse/CAMEL-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540804#comment-17540804
]
Federico Mariani commented on CAMEL-18116:
--
https://github.com/apache/camel-spring-boot-examples/pull/60
> camel-spring-boot-examples - twitter-salesforce - not working
> -
>
> Key: CAMEL-18116
> URL: https://issues.apache.org/jira/browse/CAMEL-18116
> Project: Camel
> Issue Type: Task
> Components: examples
>Reporter: Federico Mariani
>Priority: Minor
>
> The example is not working because the annotations {_}@{_}_JsonProperty_ are
> not picked up from the property, but getter and setter with _@JsonProperty_
> should be added
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
