[jira] [Updated] (CAMEL-12178) Add getMessage and setMessage methods to the Exchange interface
[ https://issues.apache.org/jira/browse/CAMEL-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-12178: --- Description: Most of the time, the correct Camel Message is retrieve from the exchange using Message message = hasOut() ? getOut() : getIn(); With this enhancement, the common usage would be supported by these methods. To try this out, I had to change the Exchange interface, the DefaultExchange implementation (both in camel-core), and RichExchange (in camel-scala). Everything seemed to be fine with the change. was: Most of the time, the correct Camel Message is retrieve from the exchange using Message message = hasOut() ? getOut() : setOut(); With this enhancement, the common usage would be supported by these methods. To try this out, I had to change the Exchange interface, the DefaultExchange implementation (both in camel-core), and RichExchange (in camel-scala). Everything seemed to be fine with the change. > Add getMessage and setMessage methods to the Exchange interface > --- > > Key: CAMEL-12178 > URL: https://issues.apache.org/jira/browse/CAMEL-12178 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Quinn Stevenson >Priority: Trivial > > Most of the time, the correct Camel Message is retrieve from the exchange > using > > Message message = hasOut() ? getOut() : getIn(); > > With this enhancement, the common usage would be supported by these methods. > > To try this out, I had to change the Exchange interface, the DefaultExchange > implementation (both in camel-core), and RichExchange (in camel-scala). > Everything seemed to be fine with the change. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12179) Implement Camel Aws-Kinesis Using Kinesis Client Library(KCL)
[
https://issues.apache.org/jira/browse/CAMEL-12179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-12179:
-
External issue URL: (was: https://issues.jboss.org/browse/ENTESB-7537)
Environment: (was: * JBoss Fuse 6.3 R5
** camel 2.17.0)
External issue ID: (was: ENTESB-7537)
> Implement Camel Aws-Kinesis Using Kinesis Client Library(KCL)
> -
>
> Key: CAMEL-12179
> URL: https://issues.apache.org/jira/browse/CAMEL-12179
> Project: Camel
> Issue Type: New Feature
> Components: camel-aws
>Affects Versions: 2.17.0
>Reporter: Hisao Furuichi
>Assignee: Andrea Cosentino
>Priority: Major
>
> Amazon provides 2 options for Kinesis Java Client:
> * *Kinesis Client Library(KCL)*
> * *Kinesis Streams API*
> "*Kinesis Streams API*" is a low level API set, and "*KCL*" is a rich library.
> In the official document, "*KCL*" is described like this:
> {quote}
> The KCL is compiled into your application to enable fault-tolerant
> consumption of data from the stream.
> The KCL ensures that for every shard there is a record processor running and
> processing that shard.
> The library also simplifies reading data from the stream.
> The KCL uses an Amazon DynamoDB table to store control data. It creates one
> table per application that is processing data.
> The KCL takes care of many of the complex tasks associated with distributed
> computing, such as load-balancing across multiple instances, responding to
> instance failures, checkpointing processed records, and reacting to
> resharding.
> The KCL enables you to focus on writing record processing logic.
> {quote}
> Since "*Kinesis Streams API*" is used to implement current aws-kinesis
> component, usability and scalability are not provided by default.
> * User needs to specify *shardID*(ENTESB-7517) which might be changed
> dynamically
> * If a Stream uses multiple shards, user needs to create multiple endpoints
> for it. (Increasing number of shards are tips to scale out. If there are 200
> shards, user needs to maintain 200 endpoints)
> * If user wants to consume a same shard from multiple Camel runtimes, user
> needs to implement load-balancing
> By using "*KCL*" to implement *aws-kinesis*, above current
> difficulties/concern can be resolved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-12179) Implement Camel Aws-Kinesis Using Kinesis Client Library(KCL)
[
https://issues.apache.org/jira/browse/CAMEL-12179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-12179:
Assignee: Andrea Cosentino
> Implement Camel Aws-Kinesis Using Kinesis Client Library(KCL)
> -
>
> Key: CAMEL-12179
> URL: https://issues.apache.org/jira/browse/CAMEL-12179
> Project: Camel
> Issue Type: New Feature
> Components: camel-aws
>Affects Versions: 2.17.0
> Environment: * JBoss Fuse 6.3 R5
> ** camel 2.17.0
>Reporter: Hisao Furuichi
>Assignee: Andrea Cosentino
>Priority: Major
>
> Amazon provides 2 options for Kinesis Java Client:
> * *Kinesis Client Library(KCL)*
> * *Kinesis Streams API*
> "*Kinesis Streams API*" is a low level API set, and "*KCL*" is a rich library.
> In the official document, "*KCL*" is described like this:
> {quote}
> The KCL is compiled into your application to enable fault-tolerant
> consumption of data from the stream.
> The KCL ensures that for every shard there is a record processor running and
> processing that shard.
> The library also simplifies reading data from the stream.
> The KCL uses an Amazon DynamoDB table to store control data. It creates one
> table per application that is processing data.
> The KCL takes care of many of the complex tasks associated with distributed
> computing, such as load-balancing across multiple instances, responding to
> instance failures, checkpointing processed records, and reacting to
> resharding.
> The KCL enables you to focus on writing record processing logic.
> {quote}
> Since "*Kinesis Streams API*" is used to implement current aws-kinesis
> component, usability and scalability are not provided by default.
> * User needs to specify *shardID*(ENTESB-7517) which might be changed
> dynamically
> * If a Stream uses multiple shards, user needs to create multiple endpoints
> for it. (Increasing number of shards are tips to scale out. If there are 200
> shards, user needs to maintain 200 endpoints)
> * If user wants to consume a same shard from multiple Camel runtimes, user
> needs to implement load-balancing
> By using "*KCL*" to implement *aws-kinesis*, above current
> difficulties/concern can be resolved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12179) Implement Camel Aws-Kinesis Using Kinesis Client Library(KCL)
Hisao Furuichi created CAMEL-12179:
--
Summary: Implement Camel Aws-Kinesis Using Kinesis Client
Library(KCL)
Key: CAMEL-12179
URL: https://issues.apache.org/jira/browse/CAMEL-12179
Project: Camel
Issue Type: New Feature
Components: camel-aws
Affects Versions: 2.17.0
Environment: * JBoss Fuse 6.3 R5
** camel 2.17.0
Reporter: Hisao Furuichi
Amazon provides 2 options for Kinesis Java Client:
* *Kinesis Client Library(KCL)*
* *Kinesis Streams API*
"*Kinesis Streams API*" is a low level API set, and "*KCL*" is a rich library.
In the official document, "*KCL*" is described like this:
{quote}
The KCL is compiled into your application to enable fault-tolerant consumption
of data from the stream.
The KCL ensures that for every shard there is a record processor running and
processing that shard.
The library also simplifies reading data from the stream.
The KCL uses an Amazon DynamoDB table to store control data. It creates one
table per application that is processing data.
The KCL takes care of many of the complex tasks associated with distributed
computing, such as load-balancing across multiple instances, responding to
instance failures, checkpointing processed records, and reacting to resharding.
The KCL enables you to focus on writing record processing logic.
{quote}
Since "*Kinesis Streams API*" is used to implement current aws-kinesis
component, usability and scalability are not provided by default.
* User needs to specify *shardID*(ENTESB-7517) which might be changed
dynamically
* If a Stream uses multiple shards, user needs to create multiple endpoints for
it. (Increasing number of shards are tips to scale out. If there are 200
shards, user needs to maintain 200 endpoints)
* If user wants to consume a same shard from multiple Camel runtimes, user
needs to implement load-balancing
By using "*KCL*" to implement *aws-kinesis*, above current difficulties/concern
can be resolved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12178) Add getMessage and setMessage methods to the Exchange interface
Quinn Stevenson created CAMEL-12178: --- Summary: Add getMessage and setMessage methods to the Exchange interface Key: CAMEL-12178 URL: https://issues.apache.org/jira/browse/CAMEL-12178 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Quinn Stevenson Most of the time, the correct Camel Message is retrieve from the exchange using Message message = hasOut() ? getOut() : setOut(); With this enhancement, the common usage would be supported by these methods. To try this out, I had to change the Exchange interface, the DefaultExchange implementation (both in camel-core), and RichExchange (in camel-scala). Everything seemed to be fine with the change. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12177) Dns Routing Policy to start/stop routes based on dns changes.
Max created CAMEL-12177: --- Summary: Dns Routing Policy to start/stop routes based on dns changes. Key: CAMEL-12177 URL: https://issues.apache.org/jira/browse/CAMEL-12177 Project: Camel Issue Type: New Feature Components: camel-dns Affects Versions: 2.21.0 Reporter: Max Dns Routing Policy to start/stop routes based on dns changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12176) Camel-Dropbox /search and /get are not working
[
https://issues.apache.org/jira/browse/CAMEL-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamil updated CAMEL-12176:
--
Description:
First of all,
[documentation|https://github.com/apache/camel/blob/master/components/camel-dropbox/src/main/docs/dropbox-component.adoc]
states that "query" property in "search" operation is not mandatory, but:
{code:java}
from("direct:dropboxSearch").to("dropbox://search?remotePath=/={{dropbox.key}}"){code}
throws:
{code:java}
java.lang.IllegalArgumentException: Required value for 'query' is null
at com.dropbox.core.v2.files.SearchArg.(SearchArg.java:59)
~[dropbox-core-sdk-3.0.4.jar:na]
at com.dropbox.core.v2.files.SearchArg.(SearchArg.java:93)
~[dropbox-core-sdk-3.0.4.jar:na]
at
com.dropbox.core.v2.files.DbxUserFilesRequests.search(DbxUserFilesRequests.java:2416)
~[dropbox-core-sdk-3.0.4.jar:na]
at
org.apache.camel.component.dropbox.core.DropboxAPIFacade.search(DropboxAPIFacade.java:270)
~[camel-dropbox-2.20.1.jar:2.20.1]
at
org.apache.camel.component.dropbox.integration.producer.DropboxSearchProducer.process(DropboxSearchProducer.java:43)
~[camel-dropbox-2.20.1.jar:2.20.1]
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
~[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
~[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
~[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.SharedCamelInternalProcessor.process(SharedCamelInternalProcessor.java:186)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.SharedCamelInternalProcessor.process(SharedCamelInternalProcessor.java:86)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.impl.ProducerCache$1.doInProducer(ProducerCache.java:541)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.impl.ProducerCache$1.doInProducer(ProducerCache.java:506)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.impl.ProducerCache.doInProducer(ProducerCache.java:369)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.impl.ProducerCache.sendExchange(ProducerCache.java:506)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.impl.ProducerCache.send(ProducerCache.java:229)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.impl.DefaultProducerTemplate.send(DefaultProducerTemplate.java:144)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:161)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:370)
[camel-core-2.20.1.jar:2.20.1]{code}
On the other hand, when I put query=* like this:
{code:java}
from("direct:dropboxSearch").to("dropbox://search?remotePath=/=*={{dropbox.key}}"){code}
it throws:
{code:java}
org.apache.camel.component.dropbox.util.DropboxException: / does not exist or
can't obtain metadata
at
org.apache.camel.component.dropbox.core.DropboxAPIFacade.search(DropboxAPIFacade.java:283)
~[camel-dropbox-2.20.1.jar:2.20.1]
at
org.apache.camel.component.dropbox.integration.producer.DropboxSearchProducer.process(DropboxSearchProducer.java:43)
~[camel-dropbox-2.20.1.jar:2.20.1]
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
~[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
~[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
~[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
[camel-core-2.20.1.jar:2.20.1]
at
[jira] [Created] (CAMEL-12176) Camel-Dropbox /search and /get are not working
Kamil created CAMEL-12176:
-
Summary: Camel-Dropbox /search and /get are not working
Key: CAMEL-12176
URL: https://issues.apache.org/jira/browse/CAMEL-12176
Project: Camel
Issue Type: Bug
Components: camel-dropbox
Affects Versions: 2.20.1
Reporter: Kamil
First of all,
[documentation|https://github.com/apache/camel/blob/master/components/camel-dropbox/src/main/docs/dropbox-component.adoc]
states that "query" property in "search" operation is not mandatory, but:
{code:java}
from("direct:dropboxSearch").to("dropbox://search?remotePath=/={{dropbox.key}}"){code}
throws:
{code:java}
java.lang.IllegalArgumentException: Required value for 'query' is null
at com.dropbox.core.v2.files.SearchArg.(SearchArg.java:59)
~[dropbox-core-sdk-3.0.4.jar:na]
at com.dropbox.core.v2.files.SearchArg.(SearchArg.java:93)
~[dropbox-core-sdk-3.0.4.jar:na]
at
com.dropbox.core.v2.files.DbxUserFilesRequests.search(DbxUserFilesRequests.java:2416)
~[dropbox-core-sdk-3.0.4.jar:na]
at
org.apache.camel.component.dropbox.core.DropboxAPIFacade.search(DropboxAPIFacade.java:270)
~[camel-dropbox-2.20.1.jar:2.20.1]
at
org.apache.camel.component.dropbox.integration.producer.DropboxSearchProducer.process(DropboxSearchProducer.java:43)
~[camel-dropbox-2.20.1.jar:2.20.1]
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
~[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
~[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
~[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.SharedCamelInternalProcessor.process(SharedCamelInternalProcessor.java:186)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.SharedCamelInternalProcessor.process(SharedCamelInternalProcessor.java:86)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.impl.ProducerCache$1.doInProducer(ProducerCache.java:541)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.impl.ProducerCache$1.doInProducer(ProducerCache.java:506)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.impl.ProducerCache.doInProducer(ProducerCache.java:369)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.impl.ProducerCache.sendExchange(ProducerCache.java:506)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.impl.ProducerCache.send(ProducerCache.java:229)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.impl.DefaultProducerTemplate.send(DefaultProducerTemplate.java:144)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:161)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:370)
[camel-core-2.20.1.jar:2.20.1]{code}
On the other hand, when I put query=* like this:
{code:java}
from("direct:dropboxSearch").to("dropbox://search?remotePath=/=*={{dropbox.key}}"){code}
it throws:
{code:java}
org.apache.camel.component.dropbox.util.DropboxException: / does not exist or
can't obtain metadata
at
org.apache.camel.component.dropbox.core.DropboxAPIFacade.search(DropboxAPIFacade.java:283)
~[camel-dropbox-2.20.1.jar:2.20.1]
at
org.apache.camel.component.dropbox.integration.producer.DropboxSearchProducer.process(DropboxSearchProducer.java:43)
~[camel-dropbox-2.20.1.jar:2.20.1]
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
~[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
~[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
~[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
[camel-core-2.20.1.jar:2.20.1]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
[camel-core-2.20.1.jar:2.20.1]
at
[jira] [Commented] (CAMEL-11598) camel-spring-boot - actuator endpoints - Make it read-only by default
[ https://issues.apache.org/jira/browse/CAMEL-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334143#comment-16334143 ] Ramu kakarla commented on CAMEL-11598: --- is anything pending to close this case? > camel-spring-boot - actuator endpoints - Make it read-only by default > - > > Key: CAMEL-11598 > URL: https://issues.apache.org/jira/browse/CAMEL-11598 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.21.0 > > > We should make these commands read-only by default, as you can today stop and > start routes. This can be a little bit problematic. It may be nice to have > read-only actions to get route statistics etc. > We can then add some option the user must set to allow to control the routes > Maybe it should be named read-only and be true by default? > endpoints.camelroutes.read-only = true|false > Or we can come up with a better name. And allow to specify which actions to > turn on > endpoints.camelroutes.allow=info > endpoints.camelroutes.allow=info,start,stop > endpoints.camelroutes.allow=* > I am not sure what spring-boot may come OOTB in this regard, they may have > something also, for user roles to allow invoking certain operations etc. > But it would be nice with read-only OOTB so you can see the state of all your > routes always. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12174) Camel-AWS Kinesis Firehose: Expose options to avoid a required client in the registry
Andrea Cosentino created CAMEL-12174: Summary: Camel-AWS Kinesis Firehose: Expose options to avoid a required client in the registry Key: CAMEL-12174 URL: https://issues.apache.org/jira/browse/CAMEL-12174 Project: Camel Issue Type: Improvement Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 2.21.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12175) Camel-AWS Kinesis Firehose: Expose options to avoid a required client in the registry
Andrea Cosentino created CAMEL-12175: Summary: Camel-AWS Kinesis Firehose: Expose options to avoid a required client in the registry Key: CAMEL-12175 URL: https://issues.apache.org/jira/browse/CAMEL-12175 Project: Camel Issue Type: Improvement Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 2.21.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CAMEL-12174) Camel-AWS Kinesis Firehose: Expose options to avoid a required client in the registry
[ https://issues.apache.org/jira/browse/CAMEL-12174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino closed CAMEL-12174. Resolution: Fixed > Camel-AWS Kinesis Firehose: Expose options to avoid a required client in the > registry > - > > Key: CAMEL-12174 > URL: https://issues.apache.org/jira/browse/CAMEL-12174 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.21.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12154) Camel does not set Saxon parameters in a XQuery 3.0 compatible way
[
https://issues.apache.org/jira/browse/CAMEL-12154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12154.
-
Resolution: Fixed
> Camel does not set Saxon parameters in a XQuery 3.0 compatible way
> --
>
> Key: CAMEL-12154
> URL: https://issues.apache.org/jira/browse/CAMEL-12154
> Project: Camel
> Issue Type: Improvement
> Components: camel-saxon
>Affects Versions: 2.18.5, 2.19.4, 2.20.1
> Environment: any
>Reporter: Niels Bertram
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.19.5, 2.20.2, 2.21.0
>
>
> When injecting parameters into the Saxon XQuery engine, the Camel component
> is not sophisticated enough to inject the parameter as the right type for
> Saxon to bind it properly.
> Let's say we have a XQuery 3.0 compliant variable definition:
> {code:java}
> declare variable $extParam as xs:boolean external := false();
> {code}
> and we set a property on the exchange
> {code:java}
> exchange.setProperty("extParam ", true);
> {code}
> our XQuery execution will fail with the following error as the value bound
> into Saxon is not a Boolean type:
> {code:java}
> Type error on line 3 column 5
> XPTY0004: Required item type of value of variable $extParam is xs:boolean;
> supplied value
> has item type xs:string
> {code}
> The part(s) that need to get more sophisticated are:
> *
> [XQueryBuilder.addParameter()|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L656]
> * [XQueryBuilder.configureQuery() - set in
> body|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L626]
> * [XQueryBuilder.configureQuery() - set out
> body|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L638]
> At the bare minimum probably should be supporting to set query parameters for
> all the basic types like string, boolean, int, decimal etc.
> I was thinking of a simple if then else block to check the content type and
> then call the appropriate Saxon value wrapper but am a bit unsure as the body
> could be simple type or DOM or Source or something else depending on the
> marshalling that is going on beforehand.
> Here a very basic setup that shows what is happening when Saxon parameters
> are just bound as Object values:
> {code:java}
> package com.virginaustralia.bind.xquery;
> import static org.junit.Assert.*;
> import org.junit.Before;
> import org.junit.Test;
> import net.sf.saxon.Configuration;
> import net.sf.saxon.om.Item;
> import net.sf.saxon.om.StructuredQName;
> import net.sf.saxon.query.DynamicQueryContext;
> import net.sf.saxon.query.XQueryExpression;
> import net.sf.saxon.value.BooleanValue;
> import net.sf.saxon.value.ObjectValue;
> public class ParameterDynamicTest {
> private static final String TEST_QUERY = new StringBuilder()
> .append("xquery version \"3.0\" encoding \"UTF-8\";\n")
> .append("declare variable $extParam as xs:boolean external := false();\n")
> .append("if($extParam) then(true()) else (false())")
> .toString();
> Configuration conf = new Configuration();
> XQueryExpression query;
> DynamicQueryContext context;
> @Before
> public void setup() throws Exception {
> conf.setCompileWithTracing(true);
> query = conf.newStaticQueryContext().compileQuery(TEST_QUERY);
> context = new DynamicQueryContext(conf);
> }
> /**
> * This is what Camel XQueryBuilder executes, which leads to a parameter
> binding type error.
> *
> */
> @Test
> public void testObjectParameter() throws Exception {
> context.setParameter(StructuredQName.fromClarkName("extParam"), new
> ObjectValue<>(true));
> Item result = query.iterator(context).next();
> assertTrue(result instanceof BooleanValue);
> assertEquals(true, ((BooleanValue) result).getBooleanValue());
> }
> /**
> * This is what Camel XQueryBuilder should execute to allow Saxon to bind the
> parameter type properly.
> */
> @Test
> public void testBooleanParameter() throws Exception {
> context.setParameter(StructuredQName.fromClarkName("extParam"),
> BooleanValue.TRUE);
> Item result = query.iterator(context).next();
> assertTrue(result instanceof BooleanValue);
> assertEquals(true, ((BooleanValue) result).getBooleanValue());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12172) Camel-AWS Kinesis: Add the ability to specify credentials and region at component level
[ https://issues.apache.org/jira/browse/CAMEL-12172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12172. -- Resolution: Fixed > Camel-AWS Kinesis: Add the ability to specify credentials and region at > component level > --- > > Key: CAMEL-12172 > URL: https://issues.apache.org/jira/browse/CAMEL-12172 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.21.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12154) Camel does not set Saxon parameters in a XQuery 3.0 compatible way
[
https://issues.apache.org/jira/browse/CAMEL-12154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334048#comment-16334048
]
Claus Ibsen commented on CAMEL-12154:
-
Okay I found a solution, thanks for reporing and providing the unit test
> Camel does not set Saxon parameters in a XQuery 3.0 compatible way
> --
>
> Key: CAMEL-12154
> URL: https://issues.apache.org/jira/browse/CAMEL-12154
> Project: Camel
> Issue Type: Improvement
> Components: camel-saxon
>Affects Versions: 2.18.5, 2.19.4, 2.20.1
> Environment: any
>Reporter: Niels Bertram
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.19.5, 2.20.2, 2.21.0
>
>
> When injecting parameters into the Saxon XQuery engine, the Camel component
> is not sophisticated enough to inject the parameter as the right type for
> Saxon to bind it properly.
> Let's say we have a XQuery 3.0 compliant variable definition:
> {code:java}
> declare variable $extParam as xs:boolean external := false();
> {code}
> and we set a property on the exchange
> {code:java}
> exchange.setProperty("extParam ", true);
> {code}
> our XQuery execution will fail with the following error as the value bound
> into Saxon is not a Boolean type:
> {code:java}
> Type error on line 3 column 5
> XPTY0004: Required item type of value of variable $extParam is xs:boolean;
> supplied value
> has item type xs:string
> {code}
> The part(s) that need to get more sophisticated are:
> *
> [XQueryBuilder.addParameter()|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L656]
> * [XQueryBuilder.configureQuery() - set in
> body|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L626]
> * [XQueryBuilder.configureQuery() - set out
> body|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L638]
> At the bare minimum probably should be supporting to set query parameters for
> all the basic types like string, boolean, int, decimal etc.
> I was thinking of a simple if then else block to check the content type and
> then call the appropriate Saxon value wrapper but am a bit unsure as the body
> could be simple type or DOM or Source or something else depending on the
> marshalling that is going on beforehand.
> Here a very basic setup that shows what is happening when Saxon parameters
> are just bound as Object values:
> {code:java}
> package com.virginaustralia.bind.xquery;
> import static org.junit.Assert.*;
> import org.junit.Before;
> import org.junit.Test;
> import net.sf.saxon.Configuration;
> import net.sf.saxon.om.Item;
> import net.sf.saxon.om.StructuredQName;
> import net.sf.saxon.query.DynamicQueryContext;
> import net.sf.saxon.query.XQueryExpression;
> import net.sf.saxon.value.BooleanValue;
> import net.sf.saxon.value.ObjectValue;
> public class ParameterDynamicTest {
> private static final String TEST_QUERY = new StringBuilder()
> .append("xquery version \"3.0\" encoding \"UTF-8\";\n")
> .append("declare variable $extParam as xs:boolean external := false();\n")
> .append("if($extParam) then(true()) else (false())")
> .toString();
> Configuration conf = new Configuration();
> XQueryExpression query;
> DynamicQueryContext context;
> @Before
> public void setup() throws Exception {
> conf.setCompileWithTracing(true);
> query = conf.newStaticQueryContext().compileQuery(TEST_QUERY);
> context = new DynamicQueryContext(conf);
> }
> /**
> * This is what Camel XQueryBuilder executes, which leads to a parameter
> binding type error.
> *
> */
> @Test
> public void testObjectParameter() throws Exception {
> context.setParameter(StructuredQName.fromClarkName("extParam"), new
> ObjectValue<>(true));
> Item result = query.iterator(context).next();
> assertTrue(result instanceof BooleanValue);
> assertEquals(true, ((BooleanValue) result).getBooleanValue());
> }
> /**
> * This is what Camel XQueryBuilder should execute to allow Saxon to bind the
> parameter type properly.
> */
> @Test
> public void testBooleanParameter() throws Exception {
> context.setParameter(StructuredQName.fromClarkName("extParam"),
> BooleanValue.TRUE);
> Item result = query.iterator(context).next();
> assertTrue(result instanceof BooleanValue);
> assertEquals(true, ((BooleanValue) result).getBooleanValue());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12154) Camel does not set Saxon parameters in a XQuery 3.0 compatible way
[
https://issues.apache.org/jira/browse/CAMEL-12154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-12154:
Fix Version/s: 2.21.0
2.20.2
2.19.5
> Camel does not set Saxon parameters in a XQuery 3.0 compatible way
> --
>
> Key: CAMEL-12154
> URL: https://issues.apache.org/jira/browse/CAMEL-12154
> Project: Camel
> Issue Type: Improvement
> Components: camel-saxon
>Affects Versions: 2.18.5, 2.19.4, 2.20.1
> Environment: any
>Reporter: Niels Bertram
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.19.5, 2.20.2, 2.21.0
>
>
> When injecting parameters into the Saxon XQuery engine, the Camel component
> is not sophisticated enough to inject the parameter as the right type for
> Saxon to bind it properly.
> Let's say we have a XQuery 3.0 compliant variable definition:
> {code:java}
> declare variable $extParam as xs:boolean external := false();
> {code}
> and we set a property on the exchange
> {code:java}
> exchange.setProperty("extParam ", true);
> {code}
> our XQuery execution will fail with the following error as the value bound
> into Saxon is not a Boolean type:
> {code:java}
> Type error on line 3 column 5
> XPTY0004: Required item type of value of variable $extParam is xs:boolean;
> supplied value
> has item type xs:string
> {code}
> The part(s) that need to get more sophisticated are:
> *
> [XQueryBuilder.addParameter()|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L656]
> * [XQueryBuilder.configureQuery() - set in
> body|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L626]
> * [XQueryBuilder.configureQuery() - set out
> body|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L638]
> At the bare minimum probably should be supporting to set query parameters for
> all the basic types like string, boolean, int, decimal etc.
> I was thinking of a simple if then else block to check the content type and
> then call the appropriate Saxon value wrapper but am a bit unsure as the body
> could be simple type or DOM or Source or something else depending on the
> marshalling that is going on beforehand.
> Here a very basic setup that shows what is happening when Saxon parameters
> are just bound as Object values:
> {code:java}
> package com.virginaustralia.bind.xquery;
> import static org.junit.Assert.*;
> import org.junit.Before;
> import org.junit.Test;
> import net.sf.saxon.Configuration;
> import net.sf.saxon.om.Item;
> import net.sf.saxon.om.StructuredQName;
> import net.sf.saxon.query.DynamicQueryContext;
> import net.sf.saxon.query.XQueryExpression;
> import net.sf.saxon.value.BooleanValue;
> import net.sf.saxon.value.ObjectValue;
> public class ParameterDynamicTest {
> private static final String TEST_QUERY = new StringBuilder()
> .append("xquery version \"3.0\" encoding \"UTF-8\";\n")
> .append("declare variable $extParam as xs:boolean external := false();\n")
> .append("if($extParam) then(true()) else (false())")
> .toString();
> Configuration conf = new Configuration();
> XQueryExpression query;
> DynamicQueryContext context;
> @Before
> public void setup() throws Exception {
> conf.setCompileWithTracing(true);
> query = conf.newStaticQueryContext().compileQuery(TEST_QUERY);
> context = new DynamicQueryContext(conf);
> }
> /**
> * This is what Camel XQueryBuilder executes, which leads to a parameter
> binding type error.
> *
> */
> @Test
> public void testObjectParameter() throws Exception {
> context.setParameter(StructuredQName.fromClarkName("extParam"), new
> ObjectValue<>(true));
> Item result = query.iterator(context).next();
> assertTrue(result instanceof BooleanValue);
> assertEquals(true, ((BooleanValue) result).getBooleanValue());
> }
> /**
> * This is what Camel XQueryBuilder should execute to allow Saxon to bind the
> parameter type properly.
> */
> @Test
> public void testBooleanParameter() throws Exception {
> context.setParameter(StructuredQName.fromClarkName("extParam"),
> BooleanValue.TRUE);
> Item result = query.iterator(context).next();
> assertTrue(result instanceof BooleanValue);
> assertEquals(true, ((BooleanValue) result).getBooleanValue());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-12154) Camel does not set Saxon parameters in a XQuery 3.0 compatible way
[
https://issues.apache.org/jira/browse/CAMEL-12154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-12154:
---
Assignee: Claus Ibsen
> Camel does not set Saxon parameters in a XQuery 3.0 compatible way
> --
>
> Key: CAMEL-12154
> URL: https://issues.apache.org/jira/browse/CAMEL-12154
> Project: Camel
> Issue Type: Improvement
> Components: camel-saxon
>Affects Versions: 2.18.5, 2.19.4, 2.20.1
> Environment: any
>Reporter: Niels Bertram
>Assignee: Claus Ibsen
>Priority: Minor
>
> When injecting parameters into the Saxon XQuery engine, the Camel component
> is not sophisticated enough to inject the parameter as the right type for
> Saxon to bind it properly.
> Let's say we have a XQuery 3.0 compliant variable definition:
> {code:java}
> declare variable $extParam as xs:boolean external := false();
> {code}
> and we set a property on the exchange
> {code:java}
> exchange.setProperty("extParam ", true);
> {code}
> our XQuery execution will fail with the following error as the value bound
> into Saxon is not a Boolean type:
> {code:java}
> Type error on line 3 column 5
> XPTY0004: Required item type of value of variable $extParam is xs:boolean;
> supplied value
> has item type xs:string
> {code}
> The part(s) that need to get more sophisticated are:
> *
> [XQueryBuilder.addParameter()|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L656]
> * [XQueryBuilder.configureQuery() - set in
> body|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L626]
> * [XQueryBuilder.configureQuery() - set out
> body|https://github.com/apache/camel/blob/camel-2.20.x/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java#L638]
> At the bare minimum probably should be supporting to set query parameters for
> all the basic types like string, boolean, int, decimal etc.
> I was thinking of a simple if then else block to check the content type and
> then call the appropriate Saxon value wrapper but am a bit unsure as the body
> could be simple type or DOM or Source or something else depending on the
> marshalling that is going on beforehand.
> Here a very basic setup that shows what is happening when Saxon parameters
> are just bound as Object values:
> {code:java}
> package com.virginaustralia.bind.xquery;
> import static org.junit.Assert.*;
> import org.junit.Before;
> import org.junit.Test;
> import net.sf.saxon.Configuration;
> import net.sf.saxon.om.Item;
> import net.sf.saxon.om.StructuredQName;
> import net.sf.saxon.query.DynamicQueryContext;
> import net.sf.saxon.query.XQueryExpression;
> import net.sf.saxon.value.BooleanValue;
> import net.sf.saxon.value.ObjectValue;
> public class ParameterDynamicTest {
> private static final String TEST_QUERY = new StringBuilder()
> .append("xquery version \"3.0\" encoding \"UTF-8\";\n")
> .append("declare variable $extParam as xs:boolean external := false();\n")
> .append("if($extParam) then(true()) else (false())")
> .toString();
> Configuration conf = new Configuration();
> XQueryExpression query;
> DynamicQueryContext context;
> @Before
> public void setup() throws Exception {
> conf.setCompileWithTracing(true);
> query = conf.newStaticQueryContext().compileQuery(TEST_QUERY);
> context = new DynamicQueryContext(conf);
> }
> /**
> * This is what Camel XQueryBuilder executes, which leads to a parameter
> binding type error.
> *
> */
> @Test
> public void testObjectParameter() throws Exception {
> context.setParameter(StructuredQName.fromClarkName("extParam"), new
> ObjectValue<>(true));
> Item result = query.iterator(context).next();
> assertTrue(result instanceof BooleanValue);
> assertEquals(true, ((BooleanValue) result).getBooleanValue());
> }
> /**
> * This is what Camel XQueryBuilder should execute to allow Saxon to bind the
> parameter type properly.
> */
> @Test
> public void testBooleanParameter() throws Exception {
> context.setParameter(StructuredQName.fromClarkName("extParam"),
> BooleanValue.TRUE);
> Item result = query.iterator(context).next();
> assertTrue(result instanceof BooleanValue);
> assertEquals(true, ((BooleanValue) result).getBooleanValue());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12173) Camel-AWS Kinesis Firehose: Add the ability to specify credentials and region at component level
Andrea Cosentino created CAMEL-12173: Summary: Camel-AWS Kinesis Firehose: Add the ability to specify credentials and region at component level Key: CAMEL-12173 URL: https://issues.apache.org/jira/browse/CAMEL-12173 Project: Camel Issue Type: Improvement Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 2.21.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12172) Camel-AWS Kinesis: Add the ability to specify credentials and region at component level
Andrea Cosentino created CAMEL-12172: Summary: Camel-AWS Kinesis: Add the ability to specify credentials and region at component level Key: CAMEL-12172 URL: https://issues.apache.org/jira/browse/CAMEL-12172 Project: Camel Issue Type: Improvement Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 2.21.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12171) Camel-AWS DDB Stream: Add the ability to specify credentials and region at component level
[ https://issues.apache.org/jira/browse/CAMEL-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12171. -- Resolution: Fixed > Camel-AWS DDB Stream: Add the ability to specify credentials and region at > component level > -- > > Key: CAMEL-12171 > URL: https://issues.apache.org/jira/browse/CAMEL-12171 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.21.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12155) Indicate Camel-Dozer major upgrade in Camel 2.20 release note and specify how to migrate
[ https://issues.apache.org/jira/browse/CAMEL-12155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12155. - Resolution: Fixed Assignee: Claus Ibsen > Indicate Camel-Dozer major upgrade in Camel 2.20 release note and specify how > to migrate > > > Key: CAMEL-12155 > URL: https://issues.apache.org/jira/browse/CAMEL-12155 > Project: Camel > Issue Type: Task > Components: documentation >Affects Versions: 2.20.0 >Reporter: Aurelien Pupier >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.21.0 > > > For Camel 2.20, Camel Dozer has been upgraded rom version 5.x to 6.1. there > are breaking changes: > * see Dozer migration guides > [https://dozermapper.github.io/gitbook/migration/v5-to-v6.html] and > [https://dozermapper.github.io/gitbook/migration/v6-to-v61.html] > * Camel has consequently an API break too: > org.apache.camel.converter.dozer.DozerBeanMapperConfiguration > > It would be nice to add a note in the release note: > [http://camel.apache.org/camel-2200-release.html#Camel2.20.0Release-Importantchangestoconsiderwhenupgrading] > > I have not found where to propose update to the release note, seems that it > is not part of github repo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12133) Update Camel documentation for ThrottlingExceptionRoutePolicy
[ https://issues.apache.org/jira/browse/CAMEL-12133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12133. - Resolution: Fixed Assignee: Claus Ibsen Fix Version/s: 2.21.0 Thanks for the doc update > Update Camel documentation for ThrottlingExceptionRoutePolicy > -- > > Key: CAMEL-12133 > URL: https://issues.apache.org/jira/browse/CAMEL-12133 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Mike Barlotta >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.21.0 > > > The `ThrottlingExceptionPolicy` circuit breaker EIP needs some documentation > Perhaps on the Route Policy page but open to suggestions > http://camel.apache.org/routepolicy.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12171) Camel-AWS DDB Stream: Add the ability to specify credentials and region at component level
Andrea Cosentino created CAMEL-12171: Summary: Camel-AWS DDB Stream: Add the ability to specify credentials and region at component level Key: CAMEL-12171 URL: https://issues.apache.org/jira/browse/CAMEL-12171 Project: Camel Issue Type: Improvement Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 2.21.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12169) [XChange] Add initial support for order management
[ https://issues.apache.org/jira/browse/CAMEL-12169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated CAMEL-12169: --- Summary: [XChange] Add initial support for order management (was: [XChange] Add initial support for orders) > [XChange] Add initial support for order management > -- > > Key: CAMEL-12169 > URL: https://issues.apache.org/jira/browse/CAMEL-12169 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12168) [XChange] Add initial support for market data queries
[ https://issues.apache.org/jira/browse/CAMEL-12168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated CAMEL-12168: --- Summary: [XChange] Add initial support for market data queries (was: [XChange] Add initial support for market data) > [XChange] Add initial support for market data queries > - > > Key: CAMEL-12168 > URL: https://issues.apache.org/jira/browse/CAMEL-12168 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12066) [XChange] Add initial support for crypto currencies
[ https://issues.apache.org/jira/browse/CAMEL-12066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated CAMEL-12066: --- Summary: [XChange] Add initial support for crypto currencies (was: Add support for crypto currencies) > [XChange] Add initial support for crypto currencies > --- > > Key: CAMEL-12066 > URL: https://issues.apache.org/jira/browse/CAMEL-12066 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > > Integrate with various Bitcoin and other crypto currency exchanges. > There is project called [XChange|https://github.com/timmolter/XChange], which > offers a common API to interact with a [large number of > exchanges|https://github.com/timmolter/XChange/wiki/Exchange-Support]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12170) [XChange] Add initial support for account management
[ https://issues.apache.org/jira/browse/CAMEL-12170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler reassigned CAMEL-12170: -- Assignee: Thomas Diesler > [XChange] Add initial support for account management > > > Key: CAMEL-12170 > URL: https://issues.apache.org/jira/browse/CAMEL-12170 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12168) [XChange] Add initial support for market data
[ https://issues.apache.org/jira/browse/CAMEL-12168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler reassigned CAMEL-12168: -- Assignee: Thomas Diesler > [XChange] Add initial support for market data > - > > Key: CAMEL-12168 > URL: https://issues.apache.org/jira/browse/CAMEL-12168 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12169) [XChange] Add initial support for orders
Thomas Diesler created CAMEL-12169: -- Summary: [XChange] Add initial support for orders Key: CAMEL-12169 URL: https://issues.apache.org/jira/browse/CAMEL-12169 Project: Camel Issue Type: New Feature Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12170) [XChange] Add initial support for account management
Thomas Diesler created CAMEL-12170: -- Summary: [XChange] Add initial support for account management Key: CAMEL-12170 URL: https://issues.apache.org/jira/browse/CAMEL-12170 Project: Camel Issue Type: New Feature Reporter: Thomas Diesler -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12168) [XChange] Add initial support for market data
Thomas Diesler created CAMEL-12168: -- Summary: [XChange] Add initial support for market data Key: CAMEL-12168 URL: https://issues.apache.org/jira/browse/CAMEL-12168 Project: Camel Issue Type: New Feature Reporter: Thomas Diesler -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12167) [XChange] Get the list of supported currency pairs
Thomas Diesler created CAMEL-12167: -- Summary: [XChange] Get the list of supported currency pairs Key: CAMEL-12167 URL: https://issues.apache.org/jira/browse/CAMEL-12167 Project: Camel Issue Type: New Feature Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message was sent by Atlassian JIRA (v7.6.3#76005)
