[jira] [Commented] (CAMEL-15233) camel-salesforce - CometDReplayExtension does not keep replayId for each message/channel
[
https://issues.apache.org/jira/browse/CAMEL-15233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149873#comment-17149873
]
Claus Ibsen commented on CAMEL-15233:
-
Hi Edgar
Yes this looks great. And since this is an internal change only and
fixes/improves this then I can see us backport this to 2.25.x.
The source from salesforce is BSD-3 which we can accept
For the unit test can you find another way with the reflection to avoid using
log4j util, as logging library.
And when ready can you create a PR.
> camel-salesforce - CometDReplayExtension does not keep replayId for each
> message/channel
>
>
> Key: CAMEL-15233
> URL: https://issues.apache.org/jira/browse/CAMEL-15233
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Reporter: Edgar Chernick
>Priority: Major
>
> CometDReplayExtension class try to read the replayId from the message by
> doing
> {code}
> final Object value = message.get(EXTENSION_NAME);
> {code}
> However, the replayId (based on this
> [https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/using_streaming_api_durability.htm])
> is actually within data -> event -> replayId.
> By doing the following (the same thing the salesforce consumer does
> https://github.com/apache/camel/blob/master/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/SalesforceConsumer.java#L250)
> {code}
> final Map data = (Map) message.get("data");
> final Map event = (Map) data.get("event");
> final Object value = event.get("replayId");
> {code}
> I was able to properly fetch the replayId from the message.
> Since the current version does not do this properly, If the component loses
> the connection and has to subscribe again it will use the replayid value from
> the endpoint which it will be outdated if any message was read before the
> connection failure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-15233) camel-salesforce - CometDReplayExtension does not keep replayId for each message/channel
[
https://issues.apache.org/jira/browse/CAMEL-15233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-15233:
Fix Version/s: 3.5.0
2.25.2
> camel-salesforce - CometDReplayExtension does not keep replayId for each
> message/channel
>
>
> Key: CAMEL-15233
> URL: https://issues.apache.org/jira/browse/CAMEL-15233
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Reporter: Edgar Chernick
>Priority: Major
> Fix For: 2.25.2, 3.5.0
>
>
> CometDReplayExtension class try to read the replayId from the message by
> doing
> {code}
> final Object value = message.get(EXTENSION_NAME);
> {code}
> However, the replayId (based on this
> [https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/using_streaming_api_durability.htm])
> is actually within data -> event -> replayId.
> By doing the following (the same thing the salesforce consumer does
> https://github.com/apache/camel/blob/master/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/SalesforceConsumer.java#L250)
> {code}
> final Map data = (Map) message.get("data");
> final Map event = (Map) data.get("event");
> final Object value = event.get("replayId");
> {code}
> I was able to properly fetch the replayId from the message.
> Since the current version does not do this properly, If the component loses
> the connection and has to subscribe again it will use the replayid value from
> the endpoint which it will be outdated if any message was read before the
> connection failure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14963) camel-core - Parameterized RouteBuilder
[ https://issues.apache.org/jira/browse/CAMEL-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148410#comment-17148410 ] Claus Ibsen edited comment on CAMEL-14963 at 7/2/20, 5:00 AM: -- RouteTemplate TODO: Model *DONE* TODO: Validation that template parameters are provided *DONE* TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template *DONE* TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value *DONE* TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL TODO: spring boot routes collector TODO: camel-karaf XML DSL TODO: fluent builder for creating route via template was (Author: davsclaus): RouteTemplate TODO: Model *DONE* TODO: Validation that template parameters are provided *DONE* TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template *DONE* TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value *DONE* TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL TODO: spring boot routes collector TODO: camel-karaf XML DSL > camel-core - Parameterized RouteBuilder > --- > > Key: CAMEL-14963 > URL: https://issues.apache.org/jira/browse/CAMEL-14963 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.5.0 > > > Had some talk with Luca about parameterized route builder/routes so you could > specify per route what parameters they has (required and optional) by > parameter name. > Then this information can be used by tooling, camel component etc to be able > to instantiate a route and specify the parameters it requires. > Some more details to follow. Just wanted to create a JIRA before forgetting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14963) camel-core - Parameterized RouteBuilder
[ https://issues.apache.org/jira/browse/CAMEL-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148410#comment-17148410 ] Claus Ibsen edited comment on CAMEL-14963 at 7/2/20, 4:59 AM: -- RouteTemplate TODO: Model *DONE* TODO: Validation that template parameters are provided *DONE* TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template *DONE* TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value *DONE* TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL TODO: spring boot routes collector TODO: camel-karaf XML DSL was (Author: davsclaus): RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template *DONE* TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value *DONE* TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL TODO: spring boot routes collector TODO: camel-karaf XML DSL > camel-core - Parameterized RouteBuilder > --- > > Key: CAMEL-14963 > URL: https://issues.apache.org/jira/browse/CAMEL-14963 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.5.0 > > > Had some talk with Luca about parameterized route builder/routes so you could > specify per route what parameters they has (required and optional) by > parameter name. > Then this information can be used by tooling, camel component etc to be able > to instantiate a route and specify the parameters it requires. > Some more details to follow. Just wanted to create a JIRA before forgetting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14918) camel-cdi - Avoid @Resource injection
[ https://issues.apache.org/jira/browse/CAMEL-14918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Feng reassigned CAMEL-14918: -- Assignee: Zheng Feng > camel-cdi - Avoid @Resource injection > - > > Key: CAMEL-14918 > URL: https://issues.apache.org/jira/browse/CAMEL-14918 > Project: Camel > Issue Type: Task > Components: camel-cdi >Reporter: Claus Ibsen >Assignee: Zheng Feng >Priority: Major > Fix For: 3.x > > > In org.apache.camel.cdi.transaction.JtaTransactionPolicy the JNDI transaction > manager is injected. > But we should do this via Java code so we dont have a *** dependency on > javax.annotation.Resource that are not available in standard JARs and you > have to hunt down the universe to find such things. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14918) camel-cdi - Avoid @Resource injection
[ https://issues.apache.org/jira/browse/CAMEL-14918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149767#comment-17149767 ] Zheng Feng commented on CAMEL-14918: Since we have moved the JtaTransactionPolicy to the camel-jta, the javax.annontation.Resource is on the TransactionalJtaTransactionPolicy now. > camel-cdi - Avoid @Resource injection > - > > Key: CAMEL-14918 > URL: https://issues.apache.org/jira/browse/CAMEL-14918 > Project: Camel > Issue Type: Task > Components: camel-cdi >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > In org.apache.camel.cdi.transaction.JtaTransactionPolicy the JNDI transaction > manager is injected. > But we should do this via Java code so we dont have a *** dependency on > javax.annotation.Resource that are not available in standard JARs and you > have to hunt down the universe to find such things. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-15233) camel-salesforce - CometDReplayExtension does not keep replayId for each message/channel
[
https://issues.apache.org/jira/browse/CAMEL-15233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149742#comment-17149742
]
Edgar Chernick edited comment on CAMEL-15233 at 7/1/20, 11:34 PM:
--
Hi guys, I've tried fixing the issue myself here
https://github.com/apache/camel/compare/master...edgarc-ciandt:master. Would
you guys mind taking a look and code reviewing it ?
I have deleted the CometDReplayExtension class and used another implementation
of it from
https://github.com/forcedotcom/EMP-Connector/blob/master/src/main/java/com/salesforce/emp/connector/ReplayExtension.java
I have also created some unit tests to cover it.
Another question. I would need to have this fixed on 2.25, do you guys think
it's possible or the fix will probably be applied to the latest version only ?
was (Author: edgarc):
Hi guys, I've tried fixing the issue myself here
https://github.com/apache/camel/compare/master...edgarc-ciandt:master. Would
you guys mind taking a look and code reviewing it ?
I have deleted the CometDReplayExtension class and used another implementation
of it from
https://github.com/forcedotcom/EMP-Connector/blob/master/src/main/java/com/salesforce/emp/connector/ReplayExtension.java
I have also created some unit tests to cover it.
Another question. I would need to have this fixed on 2.25, do you guys think
it's possible or the fix will be applied to the latest version only ?
> camel-salesforce - CometDReplayExtension does not keep replayId for each
> message/channel
>
>
> Key: CAMEL-15233
> URL: https://issues.apache.org/jira/browse/CAMEL-15233
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Reporter: Edgar Chernick
>Priority: Major
>
> CometDReplayExtension class try to read the replayId from the message by
> doing
> {code}
> final Object value = message.get(EXTENSION_NAME);
> {code}
> However, the replayId (based on this
> [https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/using_streaming_api_durability.htm])
> is actually within data -> event -> replayId.
> By doing the following (the same thing the salesforce consumer does
> https://github.com/apache/camel/blob/master/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/SalesforceConsumer.java#L250)
> {code}
> final Map data = (Map) message.get("data");
> final Map event = (Map) data.get("event");
> final Object value = event.get("replayId");
> {code}
> I was able to properly fetch the replayId from the message.
> Since the current version does not do this properly, If the component loses
> the connection and has to subscribe again it will use the replayid value from
> the endpoint which it will be outdated if any message was read before the
> connection failure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15233) camel-salesforce - CometDReplayExtension does not keep replayId for each message/channel
[
https://issues.apache.org/jira/browse/CAMEL-15233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149742#comment-17149742
]
Edgar Chernick commented on CAMEL-15233:
Hi guys, I've tried fixing the issue myself here
https://github.com/apache/camel/compare/master...edgarc-ciandt:master. Would
you guys mind taking a look and code reviewing it ?
I have deleted the CometDReplayExtension class and used another implementation
of it from
https://github.com/forcedotcom/EMP-Connector/blob/master/src/main/java/com/salesforce/emp/connector/ReplayExtension.java
I have also created some unit tests to cover it.
Another question. I would need to have this fixed on 2.25, do you guys think
it's possible or the fix will be applied to the latest version only ?
> camel-salesforce - CometDReplayExtension does not keep replayId for each
> message/channel
>
>
> Key: CAMEL-15233
> URL: https://issues.apache.org/jira/browse/CAMEL-15233
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Reporter: Edgar Chernick
>Priority: Major
>
> CometDReplayExtension class try to read the replayId from the message by
> doing
> {code}
> final Object value = message.get(EXTENSION_NAME);
> {code}
> However, the replayId (based on this
> [https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/using_streaming_api_durability.htm])
> is actually within data -> event -> replayId.
> By doing the following (the same thing the salesforce consumer does
> https://github.com/apache/camel/blob/master/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/SalesforceConsumer.java#L250)
> {code}
> final Map data = (Map) message.get("data");
> final Map event = (Map) data.get("event");
> final Object value = event.get("replayId");
> {code}
> I was able to properly fetch the replayId from the message.
> Since the current version does not do this properly, If the component loses
> the connection and has to subscribe again it will use the replayid value from
> the endpoint which it will be outdated if any message was read before the
> connection failure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14565) camel-spring-boot - Some auto configuration options has no descriptions
[ https://issues.apache.org/jira/browse/CAMEL-14565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149671#comment-17149671 ] Claus Ibsen commented on CAMEL-14565: - Yeah so its a spring boot tooling problem, they could (like we had once in camel) have the tool automatic download the -source JARs via maven and parse the .java file and grab its javadoc - we did that in some camel-main tooling. You can try to @override the parent option getter/setter and copy its javadoc, for example take one parameter and try with that. > camel-spring-boot - Some auto configuration options has no descriptions > --- > > Key: CAMEL-14565 > URL: https://issues.apache.org/jira/browse/CAMEL-14565 > Project: Camel > Issue Type: Task > Components: camel-spring-boot-starters >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.5.0 > > > [WARNING] Option camel.component.consul.cluster.service.acl-token has no > description > [WARNING] Option camel.component.consul.cluster.service.block-seconds has no > description > [WARNING] Option > camel.component.consul.cluster.service.connect-timeout-millis has no > description > [WARNING] Option camel.component.consul.cluster.service.consistency-mode has > no description > [WARNING] Option camel.component.consul.cluster.service.datacenter has no > description > [WARNING] Option camel.component.consul.cluster.service.first-index has no > description > [WARNING] Option camel.component.consul.cluster.service.near-node has no > description > [WARNING] Option camel.component.consul.cluster.service.node-meta has no > description > [WARNING] Option camel.component.consul.cluster.service.password has no > description > [WARNING] Option camel.component.consul.cluster.service.ping-instance has no > description > [WARNING] Option camel.component.consul.cluster.service.read-timeout-millis > has no description > [WARNING] Option camel.component.consul.cluster.service.recursive has no > description > [WARNING] Option camel.component.consul.cluster.service.root-path has no > description > [WARNING] Option camel.component.consul.cluster.service.session-lock-delay > has no description > [WARNING] Option > camel.component.consul.cluster.service.session-refresh-interval has no > description > [WARNING] Option camel.component.consul.cluster.service.session-ttl has no > description > [WARNING] Option > camel.component.consul.cluster.service.ssl-context-parameters has no > description > [WARNING] Option camel.component.consul.cluster.service.tags has no > description > [WARNING] Option camel.component.consul.cluster.service.url has no description > [WARNING] Option camel.component.consul.cluster.service.user-name has no > description > [WARNING] Option camel.component.consul.cluster.service.write-timeout-millis > has no description > [WARNING] Option camel.component.consul.health.check.repository.enabled has > no description > [WARNING] Option > camel.component.consul.health.check.repository.failure-threshold has no > description > [WARNING] Option camel.component.consul.health.check.repository.interval has > no description > [WARNING] Option camel.component.consul.service-registry.acl-token has no > description > [WARNING] Option camel.component.consul.service-registry.block-seconds has no > description > [WARNING] Option camel.component.consul.service-registry.check-interval has > no description > [WARNING] Option camel.component.consul.service-registry.check-ttl has no > description > [WARNING] Option > camel.component.consul.service-registry.connect-timeout-millis has no > description > [WARNING] Option camel.component.consul.service-registry.consistency-mode has > no description > [WARNING] Option camel.component.consul.service-registry.datacenter has no > description > [WARNING] Option camel.component.consul.service-registry.deregister-after has > no description > [WARNING] Option > camel.component.consul.service-registry.deregister-services-on-stop has no > description > [WARNING] Option camel.component.consul.service-registry.first-index has no > description > [WARNING] Option camel.component.consul.service-registry.near-node has no > description > [WARNING] Option camel.component.consul.service-registry.node-meta has no > description > [WARNING] Option > camel.component.consul.service-registry.override-service-host has no > description > [WARNING] Option camel.component.consul.service-registry.password has no > description > [WARNING] Option camel.component.consul.service-registry.ping-instance has no > description > [WARNING] Option camel.component.consul.service-registry.read-timeout-millis > has no description > [WARNING] Option camel.component.consul.service-registry.recursive has no
[jira] [Resolved] (CAMEL-13091) Ensure that all spring boot starters have all their options documented
[ https://issues.apache.org/jira/browse/CAMEL-13091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13091. - Resolution: Duplicate See ticket CAMEL-14565 > Ensure that all spring boot starters have all their options documented > -- > > Key: CAMEL-13091 > URL: https://issues.apache.org/jira/browse/CAMEL-13091 > Project: Camel > Issue Type: Task > Components: camel-spring-boot-starters >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Time Spent: 20m > Remaining Estimate: 0h > > Some of the camel components do not have component level docs for all their > options, which are generated into the spring boot metadata. > You can see this with the build WARNs when building all the starter JARs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15228) camel-kafka - Missing end of polling signal in Processors
[
https://issues.apache.org/jira/browse/CAMEL-15228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-15228.
-
Fix Version/s: 3.5.0
Resolution: Fixed
> camel-kafka - Missing end of polling signal in Processors
> -
>
> Key: CAMEL-15228
> URL: https://issues.apache.org/jira/browse/CAMEL-15228
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Affects Versions: 3.4.0
>Reporter: Jörg
>Assignee: Ramu
>Priority: Major
> Fix For: 3.5.0
>
>
> For batch requirements it is currently not possible to get a signal for the
> last result within a poll request in processors (over all partitions and
> topics).
> The problem with this is, that a Processor cannot know when the last record
> of a poll received and it is time for commits to all of the affected
> partitions, because you cannot be sure that there is always a content in
> every partition and therefore you have no info in Processer, if any further
> message arrives.
> Solution could be to add a property to the manual commit handler in the
> [KafkaConsumer.KafkaFetchRecords.doRun|https://github.com/apache/camel/blob/c86c860b7c5b5ef754970291b7ad7c4b32b443c6/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConsumer.java#L248]
>
> {code:java}
> exchange.getIn().setHeader(KafkaConstants.MANUAL_COMMIT, manual);
> //adding new exchange property
> exchange.getIn().setHeader(KafkaConstants.LAST_RECORD_OF_CURRENT_POLL_REQUEST,
> last_record_of_last_partition);
> {code}
> LAST_RECORD_IN_CURRENT_POLL_REQUEST should be a boolean to signal end of the
> [loop over all
> partitions|https://github.com/apache/camel/blob/c86c860b7c5b5ef754970291b7ad7c4b32b443c6/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConsumer.java#L313]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-13091) Ensure that all spring boot starters have all their options documented
[ https://issues.apache.org/jira/browse/CAMEL-13091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149667#comment-17149667 ] Claus Ibsen commented on CAMEL-13091: - There is another up to date JIRA about this, so we can find that ticket and close this as a duplicate > Ensure that all spring boot starters have all their options documented > -- > > Key: CAMEL-13091 > URL: https://issues.apache.org/jira/browse/CAMEL-13091 > Project: Camel > Issue Type: Task > Components: camel-spring-boot-starters >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Time Spent: 20m > Remaining Estimate: 0h > > Some of the camel components do not have component level docs for all their > options, which are generated into the spring boot metadata. > You can see this with the build WARNs when building all the starter JARs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13091) Ensure that all spring boot starters have all their options documented
[ https://issues.apache.org/jira/browse/CAMEL-13091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149665#comment-17149665 ] Claus Ibsen commented on CAMEL-13091: - Its in the source code typically in the javadocs in the camel components that the starters use to generate its documentation from. > Ensure that all spring boot starters have all their options documented > -- > > Key: CAMEL-13091 > URL: https://issues.apache.org/jira/browse/CAMEL-13091 > Project: Camel > Issue Type: Task > Components: camel-spring-boot-starters >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Time Spent: 20m > Remaining Estimate: 0h > > Some of the camel components do not have component level docs for all their > options, which are generated into the spring boot metadata. > You can see this with the build WARNs when building all the starter JARs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-12662) spring boot starter : auto generated starters with apt
[ https://issues.apache.org/jira/browse/CAMEL-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12662. - Resolution: Abandoned spring boot is split out and we have a way of generating starters via a script for new components > spring boot starter : auto generated starters with apt > -- > > Key: CAMEL-12662 > URL: https://issues.apache.org/jira/browse/CAMEL-12662 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot-starters, tooling >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 3.x > > > As today the auto generated auto configurations happen using a mix of camel > catalog, java source code parsing and other hacks which makes the process > hard to maintain. > In camel 3.0 we should improve annotations an leverage APT to generate the > starters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13091) Ensure that all spring boot starters have all their options documented
[ https://issues.apache.org/jira/browse/CAMEL-13091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149572#comment-17149572 ] rodrigo coelho commented on CAMEL-13091: Hello, Where can we find the descriptions for the camel-zookeeper? > Ensure that all spring boot starters have all their options documented > -- > > Key: CAMEL-13091 > URL: https://issues.apache.org/jira/browse/CAMEL-13091 > Project: Camel > Issue Type: Task > Components: camel-spring-boot-starters >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Time Spent: 20m > Remaining Estimate: 0h > > Some of the camel components do not have component level docs for all their > options, which are generated into the spring boot metadata. > You can see this with the build WARNs when building all the starter JARs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14958) Suggestion on search bar within smaller screen width.
[ https://issues.apache.org/jira/browse/CAMEL-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149558#comment-17149558 ] ASF GitHub Bot commented on CAMEL-14958: AemieJ commented on pull request #398: URL: https://github.com/apache/camel-website/pull/398#issuecomment-652535935 @zregvart I simplified a bit further using your suggestion. however certain changes are necessary. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Suggestion on search bar within smaller screen width. > - > > Key: CAMEL-14958 > URL: https://issues.apache.org/jira/browse/CAMEL-14958 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aemie >Priority: Major > Labels: outreachy2020, suggestions > Attachments: bootstrap-design-blog.png, > bootstrap-design-frontpage.png, design-frontpage.png, design-navbar.png, > inline-search.png, issue-facing.png, nav-search-icon-1220.png, > nav-searchbar-1220.png, nav-searchbar-414.png, navbar-search-414.png, > navbar-searchbar.png, transform-method.png > > > Within the small width screen, the setting is to only display the social icon > button as of now. However, I thought it would be a good idea to include the > search icon alongside the social button icons. On click of the social button > icons, we could include animation, for instance, a fade-in effect of the > search bar occupying the entire navbar. The user can do the search as > required. On the left side of the search bar, there will be back arrow, which > on click would give us the original navbar look with a fade-out effect. > Before I start working on this, I would like an opinion about this idea. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14777) Replace EmbeddedEngine with the new Debezium APIs
[ https://issues.apache.org/jira/browse/CAMEL-14777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omar Al-Safi resolved CAMEL-14777. -- Resolution: Fixed > Replace EmbeddedEngine with the new Debezium APIs > - > > Key: CAMEL-14777 > URL: https://issues.apache.org/jira/browse/CAMEL-14777 > Project: Camel > Issue Type: Task > Components: camel-debezium >Affects Versions: 3.2.0 >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Minor > Fix For: 3.5.0 > > > From Debezium 1.1.0, the current EmbeddedEngine is being deprecated and > replaced with Debezium API as mentioned > [here|http://[https://debezium.io/documentation/reference/1.1/development/engine.html]]. > Since in Camel we are using the EmbeddedEngine, we will need to migrate it > to the new APIs, preferably *before Debezium version 1.3.0*. > Also, it would make sense if we can see if we can utilize the converter > support in DBZ 1.2 per [this Jira ticket > |https://issues.redhat.com/browse/DBZ-1807] in camel-debezium components -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15266) camel-website - Contributing guide cleanup
Claus Ibsen created CAMEL-15266: --- Summary: camel-website - Contributing guide cleanup Key: CAMEL-15266 URL: https://issues.apache.org/jira/browse/CAMEL-15266 Project: Camel Issue Type: Task Components: documentation, website Reporter: Claus Ibsen Fix For: 3.5.0 On gitter chat. 1. Remove that last "more resources" section 2. On the github contribution.md file, just link to the same guide on the website (one place to maintain) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14963) camel-core - Parameterized RouteBuilder
[ https://issues.apache.org/jira/browse/CAMEL-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148410#comment-17148410 ] Claus Ibsen edited comment on CAMEL-14963 at 7/1/20, 2:56 PM: -- RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template *DONE* TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value *DONE* TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL TODO: spring boot routes collector TODO: camel-karaf XML DSL was (Author: davsclaus): RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template *DONE* TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL TODO: spring boot routes collector TODO: camel-karaf XML DSL > camel-core - Parameterized RouteBuilder > --- > > Key: CAMEL-14963 > URL: https://issues.apache.org/jira/browse/CAMEL-14963 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.5.0 > > > Had some talk with Luca about parameterized route builder/routes so you could > specify per route what parameters they has (required and optional) by > parameter name. > Then this information can be used by tooling, camel component etc to be able > to instantiate a route and specify the parameters it requires. > Some more details to follow. Just wanted to create a JIRA before forgetting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14963) camel-core - Parameterized RouteBuilder
[ https://issues.apache.org/jira/browse/CAMEL-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149409#comment-17149409 ] Claus Ibsen edited comment on CAMEL-14963 at 7/1/20, 2:56 PM: -- The model needs a bit to be changed due to XML XSD generation problem. So I am refining the model so the template is not extending route and linked in a different way. *DONE* was (Author: davsclaus): The model needs a bit to be changed due to XML XSD generation problem. So I am refining the model so the template is not extending route and linked in a different way. > camel-core - Parameterized RouteBuilder > --- > > Key: CAMEL-14963 > URL: https://issues.apache.org/jira/browse/CAMEL-14963 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.5.0 > > > Had some talk with Luca about parameterized route builder/routes so you could > specify per route what parameters they has (required and optional) by > parameter name. > Then this information can be used by tooling, camel component etc to be able > to instantiate a route and specify the parameters it requires. > Some more details to follow. Just wanted to create a JIRA before forgetting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15265) StaticEndpointBuilders - The static methods should be public
Claus Ibsen created CAMEL-15265: --- Summary: StaticEndpointBuilders - The static methods should be public Key: CAMEL-15265 URL: https://issues.apache.org/jira/browse/CAMEL-15265 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 3.4.0 Reporter: Claus Ibsen Fix For: 3.4.1, 3.5.0 I was hoping to use the new StaticEndpointBuilders to configure and possibly share for my routes and producer templates in Camel 3.4.0. However, I noticed all of the static methods are package private. Is that by design? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15264) Camel-AWS2-Kinesis: Add more operations support
[ https://issues.apache.org/jira/browse/CAMEL-15264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-15264. -- Resolution: Fixed > Camel-AWS2-Kinesis: Add more operations support > --- > > Key: CAMEL-15264 > URL: https://issues.apache.org/jira/browse/CAMEL-15264 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.5.0 > > > Like delete the delivery stream or changing the destination dynamically. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14963) camel-core - Parameterized RouteBuilder
[ https://issues.apache.org/jira/browse/CAMEL-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149409#comment-17149409 ] Claus Ibsen commented on CAMEL-14963: - The model needs a bit to be changed due to XML XSD generation problem. So I am refining the model so the template is not extending route and linked in a different way. > camel-core - Parameterized RouteBuilder > --- > > Key: CAMEL-14963 > URL: https://issues.apache.org/jira/browse/CAMEL-14963 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.5.0 > > > Had some talk with Luca about parameterized route builder/routes so you could > specify per route what parameters they has (required and optional) by > parameter name. > Then this information can be used by tooling, camel component etc to be able > to instantiate a route and specify the parameters it requires. > Some more details to follow. Just wanted to create a JIRA before forgetting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15257) camel jsonata integration
[ https://issues.apache.org/jira/browse/CAMEL-15257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149398#comment-17149398 ] Andrea Cosentino commented on CAMEL-15257: -- You're welcome to work on it. > camel jsonata integration > - > > Key: CAMEL-15257 > URL: https://issues.apache.org/jira/browse/CAMEL-15257 > Project: Camel > Issue Type: New Feature > Components: camel-jackson >Affects Versions: 3.4.0 >Reporter: shatk >Priority: Major > > Hello Team, > Similar to *camel-jolt,* looking for an integration of apache camel with > jsonata [[https://jsonata.org/]] query and transformation framework. We > need to expose Rest API's using apache camel and do json transformation using > json query language [jsonata for eg] without doing binding to java objects, > as the json structure is quite dynamic. > > jsonata java implementation : > [https://github.com/IBM/JSONata4Java] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15242) camel-debezium - Upgrade to 1.2
[ https://issues.apache.org/jira/browse/CAMEL-15242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149318#comment-17149318 ] Jiri Ondrusek commented on CAMEL-15242: --- [~omarsmak] no problem. It took me more time then expected because I had a problems to verify basic debezium-mongodb functionality (could not configure mongdb correctly) > camel-debezium - Upgrade to 1.2 > --- > > Key: CAMEL-15242 > URL: https://issues.apache.org/jira/browse/CAMEL-15242 > Project: Camel > Issue Type: Improvement > Components: camel-debezium >Reporter: Claus Ibsen >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.5.0 > > > 1.2 final has been released -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15242) camel-debezium - Upgrade to 1.2
[ https://issues.apache.org/jira/browse/CAMEL-15242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149302#comment-17149302 ] Omar Al-Safi commented on CAMEL-15242: -- hey [~jondruse], sorry I wasn't aware about this ticket and you were assigned to it > camel-debezium - Upgrade to 1.2 > --- > > Key: CAMEL-15242 > URL: https://issues.apache.org/jira/browse/CAMEL-15242 > Project: Camel > Issue Type: Improvement > Components: camel-debezium >Reporter: Claus Ibsen >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.5.0 > > > 1.2 final has been released -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15261) Handle Debezium configurations with regex
[ https://issues.apache.org/jira/browse/CAMEL-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omar Al-Safi resolved CAMEL-15261. -- Resolution: Fixed > Handle Debezium configurations with regex > -- > > Key: CAMEL-15261 > URL: https://issues.apache.org/jira/browse/CAMEL-15261 > Project: Camel > Issue Type: Improvement > Components: camel-debezium >Affects Versions: 3.4.0 >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Major > Fix For: 3.5.0 > > > With the release of Debezium version 1.2.0.Final, new configurations baed on > regex being introduced, for example this [one > here|https://github.com/debezium/debezium/blob/master/debezium-core/src/main/java/io/debezium/relational/RelationalDatabaseConnectorConfig.java#L294]. > > The easiest way is to ignore such fields from the maven plugin and instruct > the user to use `.additionalProperties` configuration property to set these > fields as pretty complicated to generate such fields. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-14777) Replace EmbeddedEngine with the new Debezium APIs
[ https://issues.apache.org/jira/browse/CAMEL-14777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-14777 started by Omar Al-Safi. > Replace EmbeddedEngine with the new Debezium APIs > - > > Key: CAMEL-14777 > URL: https://issues.apache.org/jira/browse/CAMEL-14777 > Project: Camel > Issue Type: Task > Components: camel-debezium >Affects Versions: 3.2.0 >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Minor > Fix For: 3.5.0 > > > From Debezium 1.1.0, the current EmbeddedEngine is being deprecated and > replaced with Debezium API as mentioned > [here|http://[https://debezium.io/documentation/reference/1.1/development/engine.html]]. > Since in Camel we are using the EmbeddedEngine, we will need to migrate it > to the new APIs, preferably *before Debezium version 1.3.0*. > Also, it would make sense if we can see if we can utilize the converter > support in DBZ 1.2 per [this Jira ticket > |https://issues.redhat.com/browse/DBZ-1807] in camel-debezium components -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15262) ZooKeeperCuratorHelper: wrong argument order when creating a new ExponentialBackoffRetry
[
https://issues.apache.org/jira/browse/CAMEL-15262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-15262:
-
Affects Version/s: (was: 3.4.1)
> ZooKeeperCuratorHelper: wrong argument order when creating a new
> ExponentialBackoffRetry
>
>
> Key: CAMEL-15262
> URL: https://issues.apache.org/jira/browse/CAMEL-15262
> Project: Camel
> Issue Type: Bug
> Components: camel-zookeeper
>Affects Versions: 3.4.0
>Reporter: Ahmed M
>Assignee: Andrea Cosentino
>Priority: Minor
>
> The constructor args {{maxRetries}} (reconnectMaxRetries) and {{maxSleepMs}}
> (reconnectMaxSleepTime) are reversed when creating a new
> {{ExponentialBackoffRetry}} in {{ZooKeeperCuratorHelper.createCurator}} :
> {code::title=ZooKeeperCuratorHelper.java}
> if (retryPolicy == null) {
> retryPolicy = new ExponentialBackoffRetry(
>
> (int)configuration.getReconnectBaseSleepTimeUnit().toMillis(configuration.getReconnectBaseSleepTime()),
>
> (int)configuration.getReconnectMaxSleepTimeUnit().toMillis(configuration.getReconnectMaxSleepTime()),
> configuration.getReconnectMaxRetries());
> }
> {code}
> [CuratorFramework API
> javadoc|https://curator.apache.org/apidocs/org/apache/curator/retry/ExponentialBackoffRetry.html]:
> {code:java}
> ExponentialBackoffRetry(int baseSleepTimeMs, int maxRetries, int maxSleepMs)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-15262) ZooKeeperCuratorHelper: wrong argument order when creating a new ExponentialBackoffRetry
[
https://issues.apache.org/jira/browse/CAMEL-15262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-15262:
-
Fix Version/s: 3.5.0
3.4.1
> ZooKeeperCuratorHelper: wrong argument order when creating a new
> ExponentialBackoffRetry
>
>
> Key: CAMEL-15262
> URL: https://issues.apache.org/jira/browse/CAMEL-15262
> Project: Camel
> Issue Type: Bug
> Components: camel-zookeeper
>Affects Versions: 3.4.0
>Reporter: Ahmed M
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.4.1, 3.5.0
>
>
> The constructor args {{maxRetries}} (reconnectMaxRetries) and {{maxSleepMs}}
> (reconnectMaxSleepTime) are reversed when creating a new
> {{ExponentialBackoffRetry}} in {{ZooKeeperCuratorHelper.createCurator}} :
> {code::title=ZooKeeperCuratorHelper.java}
> if (retryPolicy == null) {
> retryPolicy = new ExponentialBackoffRetry(
>
> (int)configuration.getReconnectBaseSleepTimeUnit().toMillis(configuration.getReconnectBaseSleepTime()),
>
> (int)configuration.getReconnectMaxSleepTimeUnit().toMillis(configuration.getReconnectMaxSleepTime()),
> configuration.getReconnectMaxRetries());
> }
> {code}
> [CuratorFramework API
> javadoc|https://curator.apache.org/apidocs/org/apache/curator/retry/ExponentialBackoffRetry.html]:
> {code:java}
> ExponentialBackoffRetry(int baseSleepTimeMs, int maxRetries, int maxSleepMs)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-15262) ZooKeeperCuratorHelper: wrong argument order when creating a new ExponentialBackoffRetry
[
https://issues.apache.org/jira/browse/CAMEL-15262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-15262:
Assignee: Andrea Cosentino
> ZooKeeperCuratorHelper: wrong argument order when creating a new
> ExponentialBackoffRetry
>
>
> Key: CAMEL-15262
> URL: https://issues.apache.org/jira/browse/CAMEL-15262
> Project: Camel
> Issue Type: Bug
> Components: camel-zookeeper
>Affects Versions: 3.4.0, 3.4.1
>Reporter: Ahmed M
>Assignee: Andrea Cosentino
>Priority: Minor
>
> The constructor args {{maxRetries}} (reconnectMaxRetries) and {{maxSleepMs}}
> (reconnectMaxSleepTime) are reversed when creating a new
> {{ExponentialBackoffRetry}} in {{ZooKeeperCuratorHelper.createCurator}} :
> {code::title=ZooKeeperCuratorHelper.java}
> if (retryPolicy == null) {
> retryPolicy = new ExponentialBackoffRetry(
>
> (int)configuration.getReconnectBaseSleepTimeUnit().toMillis(configuration.getReconnectBaseSleepTime()),
>
> (int)configuration.getReconnectMaxSleepTimeUnit().toMillis(configuration.getReconnectMaxSleepTime()),
> configuration.getReconnectMaxRetries());
> }
> {code}
> [CuratorFramework API
> javadoc|https://curator.apache.org/apidocs/org/apache/curator/retry/ExponentialBackoffRetry.html]:
> {code:java}
> ExponentialBackoffRetry(int baseSleepTimeMs, int maxRetries, int maxSleepMs)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15242) camel-debezium - Upgrade to 1.2
[ https://issues.apache.org/jira/browse/CAMEL-15242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149236#comment-17149236 ] Jiri Ondrusek commented on CAMEL-15242: --- Fixed via https://issues.apache.org/jira/browse/CAMEL-15261 > camel-debezium - Upgrade to 1.2 > --- > > Key: CAMEL-15242 > URL: https://issues.apache.org/jira/browse/CAMEL-15242 > Project: Camel > Issue Type: Improvement > Components: camel-debezium >Reporter: Claus Ibsen >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.5.0 > > > 1.2 final has been released -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14963) camel-core - Parameterized RouteBuilder
[ https://issues.apache.org/jira/browse/CAMEL-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148410#comment-17148410 ] Claus Ibsen edited comment on CAMEL-14963 at 7/1/20, 8:39 AM: -- RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template *DONE* TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL TODO: spring boot routes collector TODO: camel-karaf XML DSL was (Author: davsclaus): RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL TODO: spring boot routes collector TODO: camel-karaf XML DSL > camel-core - Parameterized RouteBuilder > --- > > Key: CAMEL-14963 > URL: https://issues.apache.org/jira/browse/CAMEL-14963 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.5.0 > > > Had some talk with Luca about parameterized route builder/routes so you could > specify per route what parameters they has (required and optional) by > parameter name. > Then this information can be used by tooling, camel component etc to be able > to instantiate a route and specify the parameters it requires. > Some more details to follow. Just wanted to create a JIRA before forgetting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14963) camel-core - Parameterized RouteBuilder
[ https://issues.apache.org/jira/browse/CAMEL-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148410#comment-17148410 ] Claus Ibsen edited comment on CAMEL-14963 at 7/1/20, 8:03 AM: -- RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL TODO: spring boot routes collector TODO: camel-karaf XML DSL was (Author: davsclaus): RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL TODO: spring boot routes collector > camel-core - Parameterized RouteBuilder > --- > > Key: CAMEL-14963 > URL: https://issues.apache.org/jira/browse/CAMEL-14963 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.5.0 > > > Had some talk with Luca about parameterized route builder/routes so you could > specify per route what parameters they has (required and optional) by > parameter name. > Then this information can be used by tooling, camel component etc to be able > to instantiate a route and specify the parameters it requires. > Some more details to follow. Just wanted to create a JIRA before forgetting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14963) camel-core - Parameterized RouteBuilder
[ https://issues.apache.org/jira/browse/CAMEL-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148410#comment-17148410 ] Claus Ibsen edited comment on CAMEL-14963 at 7/1/20, 8:02 AM: -- RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL TODO: spring boot routes collector was (Author: davsclaus): RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL > camel-core - Parameterized RouteBuilder > --- > > Key: CAMEL-14963 > URL: https://issues.apache.org/jira/browse/CAMEL-14963 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.5.0 > > > Had some talk with Luca about parameterized route builder/routes so you could > specify per route what parameters they has (required and optional) by > parameter name. > Then this information can be used by tooling, camel component etc to be able > to instantiate a route and specify the parameters it requires. > Some more details to follow. Just wanted to create a JIRA before forgetting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14963) camel-core - Parameterized RouteBuilder
[ https://issues.apache.org/jira/browse/CAMEL-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148410#comment-17148410 ] Claus Ibsen edited comment on CAMEL-14963 at 7/1/20, 8:00 AM: -- RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value TODO: camel-main load routeTemplate XML files *DONE* TODO: routeTemplateContextRef in XML DSL was (Author: davsclaus): RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value TODO: camel-main load routeTemplate XML files TODO: routeTemplateContextRef in XML DSL > camel-core - Parameterized RouteBuilder > --- > > Key: CAMEL-14963 > URL: https://issues.apache.org/jira/browse/CAMEL-14963 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.5.0 > > > Had some talk with Luca about parameterized route builder/routes so you could > specify per route what parameters they has (required and optional) by > parameter name. > Then this information can be used by tooling, camel component etc to be able > to instantiate a route and specify the parameters it requires. > Some more details to follow. Just wanted to create a JIRA before forgetting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14963) camel-core - Parameterized RouteBuilder
[ https://issues.apache.org/jira/browse/CAMEL-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148410#comment-17148410 ] Claus Ibsen edited comment on CAMEL-14963 at 7/1/20, 7:15 AM: -- RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value TODO: camel-main load routeTemplate XML files TODO: routeTemplateContextRef in XML DSL was (Author: davsclaus): RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value > camel-core - Parameterized RouteBuilder > --- > > Key: CAMEL-14963 > URL: https://issues.apache.org/jira/browse/CAMEL-14963 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.5.0 > > > Had some talk with Luca about parameterized route builder/routes so you could > specify per route what parameters they has (required and optional) by > parameter name. > Then this information can be used by tooling, camel component etc to be able > to instantiate a route and specify the parameters it requires. > Some more details to follow. Just wanted to create a JIRA before forgetting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14963) camel-core - Parameterized RouteBuilder
[ https://issues.apache.org/jira/browse/CAMEL-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148410#comment-17148410 ] Claus Ibsen edited comment on CAMEL-14963 at 7/1/20, 7:14 AM: -- RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL *DONE* TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test *DONE* TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value was (Author: davsclaus): RouteTemplate TODO: Model *DONE* TODO: Validation that template properties are known in the route TODO: Java DSL *DONE* TODO: XML DSL TODO: XML snippets *DONE* TODO: Java API to create new routes from route templates *DONE* TODO: Java unit test *DONE* TODO: XML unit test TODO: Example TODO: Documentation TODO: Add routes with anonymous route id (eg auto assigned) *DONE* TODO: JMX API such as dump route template TODO: Add detail on a route if it was created from a template and its template id *DONE* TODO: Model XML loader *DONE* TODO: Mark a parameter as optional, and also a default value > camel-core - Parameterized RouteBuilder > --- > > Key: CAMEL-14963 > URL: https://issues.apache.org/jira/browse/CAMEL-14963 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.5.0 > > > Had some talk with Luca about parameterized route builder/routes so you could > specify per route what parameters they has (required and optional) by > parameter name. > Then this information can be used by tooling, camel component etc to be able > to instantiate a route and specify the parameters it requires. > Some more details to follow. Just wanted to create a JIRA before forgetting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15264) Camel-AWS2-Kinesis: Add more operations support
Andrea Cosentino created CAMEL-15264: Summary: Camel-AWS2-Kinesis: Add more operations support Key: CAMEL-15264 URL: https://issues.apache.org/jira/browse/CAMEL-15264 Project: Camel Issue Type: New Feature Components: camel-aws2 Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.5.0 Like delete the delivery stream or changing the destination dynamically. -- This message was sent by Atlassian Jira (v8.3.4#803005)
