[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API
Title: Message Title Dmitry Volodin updated an issue Camel / CAMEL-10766 Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API Change By: Dmitry Volodin Fix Version/s: 2.19.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API
Title: Message Title Dmitry Volodin commented on CAMEL-10766 Re: Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API I've submitted a pull request on Github... Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API
Title: Message Title Dmitry Volodin updated an issue Camel / CAMEL-10766 Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API Change By: Dmitry Volodin Attachment: CAMEL-10766.patch Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] [Commented] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API
[
https://issues.apache.org/jira/browse/CAMEL-10766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849824#comment-15849824
]
Dmitry Volodin commented on CAMEL-10766:
Yes, ES 2.4.x will officially support until 28.02.2018
https://www.elastic.co/support/eol
> Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x
> Java API
> -
>
> Key: CAMEL-10766
> URL: https://issues.apache.org/jira/browse/CAMEL-10766
> Project: Camel
> Issue Type: New Feature
> Components: camel-elasticsearch
>Reporter: Dmitry Volodin
> Fix For: 2.19.0
>
>
> We required Camel ElasticSearch component with latest ElasticSearch 5.x API
> support. For backward compatibility we've migrated curent camel-elasticsearch
> to the new camel-elasticsearch5.
> As ${lucene-version} was defined globally, it affected on both ElasticSearch
> API versions - 2.4.3 and 5.1.2 and one of the components doesn't work
> correctly. I was removed global Apache Lucene library global definition and
> place it to the dependent components. Please correct dependencies if needed.
> Also uploaded new component and all changes as patch.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API
[
https://issues.apache.org/jira/browse/CAMEL-10766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin resolved CAMEL-10766.
Resolution: Fixed
> Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x
> Java API
> -
>
> Key: CAMEL-10766
> URL: https://issues.apache.org/jira/browse/CAMEL-10766
> Project: Camel
> Issue Type: New Feature
> Components: camel-elasticsearch
>Reporter: Dmitry Volodin
> Fix For: 2.19.0
>
>
> We required Camel ElasticSearch component with latest ElasticSearch 5.x API
> support. For backward compatibility we've migrated curent camel-elasticsearch
> to the new camel-elasticsearch5.
> As ${lucene-version} was defined globally, it affected on both ElasticSearch
> API versions - 2.4.3 and 5.1.2 and one of the components doesn't work
> correctly. I was removed global Apache Lucene library global definition and
> place it to the dependent components. Please correct dependencies if needed.
> Also uploaded new component and all changes as patch.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API
Title: Message Title Dmitry Volodin updated an issue Camel / CAMEL-10766 Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API Change By: Dmitry Volodin Attachment: CAMEL-10766.patch Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API
Title: Message Title
Dmitry Volodin created an issue
Camel / CAMEL-10766
Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API
Issue Type:
Task
Affects Versions:
2.19.0
Assignee:
Unassigned
Components:
camel-elasticsearch
Created:
30/Jan/17 15:40
Fix Versions:
2.19.0
Priority:
Minor
Reporter:
Dmitry Volodin
We required Camel ElasticSearch component with latest ElasticSearch 5.x API support. For backward compatibility we've migrated curent camel-elasticsearch to the new camel-elasticsearch5. As $ {lucene-version}
was defined globally, it affected on both ElasticSearch API versions - 2.4.3 and 5.1.2 and one of the components doesn't work correctly. I was removed global Apache Lucene library global definition and place it to the dependent components. Please correct dependencies if needed. Also uploaded new component and all changes as patch.
[jira] [Created] (CAMEL-11056) Create a new camel-olingo4 component for supporting OData 4.0
Dmitry Volodin created CAMEL-11056: -- Summary: Create a new camel-olingo4 component for supporting OData 4.0 Key: CAMEL-11056 URL: https://issues.apache.org/jira/browse/CAMEL-11056 Project: Camel Issue Type: New Feature Components: camel-olingo2 Affects Versions: 2.19.0 Reporter: Dmitry Volodin Priority: Minor We required Camel Olingo component with the OData 4.0 support as now OData Version 4.0 is OASIS based and widely using standard. For backward compatibility we've migrated current camel-olingo2 to the new camel-olingo4 component, except deprecated and some new features. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-11058) camel-olingo2 component doesn't support OData 3.0
Dmitry Volodin created CAMEL-11058: -- Summary: camel-olingo2 component doesn't support OData 3.0 Key: CAMEL-11058 URL: https://issues.apache.org/jira/browse/CAMEL-11058 Project: Camel Issue Type: Bug Components: camel-olingo2 Affects Versions: 2.19.0 Environment: Created a sample to demonstrate this incompatibility https://github.com/dmvolod/test-olingo2-odata3 Reporter: Dmitry Volodin Priority: Trivial Component camel-olingo2 doesn't support OData 3.0 as olingo-odata2 library never did it. It would be nice to remove this info (OData 3.0) from the documentation and component descriptions -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-11135) camel-protobuf component improvements
[ https://issues.apache.org/jira/browse/CAMEL-11135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11135: --- Summary: camel-protobuf component improvements (was: camel-protobuf component imrovements) > camel-protobuf component improvements > - > > Key: CAMEL-11135 > URL: https://issues.apache.org/jira/browse/CAMEL-11135 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.19.0 >Reporter: Dmitry Volodin > Labels: grpc, protobuf > Fix For: 2.19.0 > > > The following camel-protobuf component improvements are require: > 1. Automatic .proto file processing and Java stubs generation (no manual > steps requires if library version or .proto file were changed) > 2. Ability to serialize/deserialize prorbuf message from JSON format in > addition to native message format using embedded protobuf-java-util library. > This feature could help in conjunction with camel-grpc component > 3. Documentation improvements and test files misprintings and formatting > correction -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-11135) camel-protobuf component imrovements
Dmitry Volodin created CAMEL-11135: -- Summary: camel-protobuf component imrovements Key: CAMEL-11135 URL: https://issues.apache.org/jira/browse/CAMEL-11135 Project: Camel Issue Type: New Feature Affects Versions: 2.19.0 Reporter: Dmitry Volodin Fix For: 2.19.0 The following camel-protobuf component improvements are require: 1. Automatic .proto file processing and Java stubs generation (no manual steps requires if library version or .proto file were changed) 2. Ability to serialize/deserialize prorbuf message from JSON format in addition to native message format using embedded protobuf-java-util library. This feature could help in conjunction with camel-grpc component 3. Documentation improvements and test files misprintings and formatting correction -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-11107) Create a new camel-grpc component
Dmitry Volodin created CAMEL-11107: -- Summary: Create a new camel-grpc component Key: CAMEL-11107 URL: https://issues.apache.org/jira/browse/CAMEL-11107 Project: Camel Issue Type: Sub-task Affects Versions: 2.19.0 Reporter: Dmitry Volodin Create a new camel-grpc component which allows to do Remote Procedure Call (RPC) Protocol Buffers (protobuf)] format over HTTP/2 transport. Stage 1: Producer with basic parameters and calling sync and async methods Stage 2: Consumer and extended parameters (future PR) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-11107) Create a new camel-grpc component
[ https://issues.apache.org/jira/browse/CAMEL-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11107: --- Description: Create a new camel-grpc component which allows to do Remote Procedure Call (RPC) Protocol Buffers (protobuf)] format over HTTP/2 transport. Stage 1: Producer with basic parameters and calling sync and async methods Stage 2: Consumer and extended producer parameters (separate future PR) was: Create a new camel-grpc component which allows to do Remote Procedure Call (RPC) Protocol Buffers (protobuf)] format over HTTP/2 transport. Stage 1: Producer with basic parameters and calling sync and async methods Stage 2: Consumer and extended parameters (future PR) > Create a new camel-grpc component > -- > > Key: CAMEL-11107 > URL: https://issues.apache.org/jira/browse/CAMEL-11107 > Project: Camel > Issue Type: Sub-task >Affects Versions: 2.19.0 >Reporter: Dmitry Volodin > Fix For: Future > > > Create a new camel-grpc component which allows to do Remote Procedure Call > (RPC) Protocol Buffers (protobuf)] format over HTTP/2 transport. > Stage 1: Producer with basic parameters and calling sync and async methods > Stage 2: Consumer and extended producer parameters (separate future PR) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-11107) Create a new camel-grpc component
[ https://issues.apache.org/jira/browse/CAMEL-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11107: --- Labels: grpc protobuf (was: ) > Create a new camel-grpc component > -- > > Key: CAMEL-11107 > URL: https://issues.apache.org/jira/browse/CAMEL-11107 > Project: Camel > Issue Type: Sub-task >Affects Versions: 2.19.0 >Reporter: Dmitry Volodin >Assignee: Andrea Cosentino > Labels: grpc, protobuf > Fix For: Future > > > Create a new camel-grpc component which allows to do Remote Procedure Call > (RPC) Protocol Buffers (protobuf)] format over HTTP/2 transport. > Stage 1: Producer with basic parameters and calling sync and async methods > Stage 2: Consumer and extended producer parameters (separate future PR) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11114) Create cache DSL
[
https://issues.apache.org/jira/browse/CAMEL-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957017#comment-15957017
]
Dmitry Volodin commented on CAMEL-4:
Nicola, this a good idea and desirable feature, please also add method which
could invalidate cache by key. For example, we can catch event from foreign
system that the data has changed and clear (invalidate) cache for the data and
systems consistency.
> Create cache DSL
>
>
> Key: CAMEL-4
> URL: https://issues.apache.org/jira/browse/CAMEL-4
> Project: Camel
> Issue Type: New Feature
>Reporter: Nicola Ferraro
> Fix For: 2.20.0
>
>
> We should evaluate adding a new "cache" dsl that can be used with all cache
> components in Camel. A default implementation may use also caffeine, included
> in camel-core.
> A possible usage example may be:
> {code}
> from("xxx")
> .cache().on("${header.yyy}").ttl(60) // caches the body
>
> .to("http4://a-service-that-makes-me-pay-for-each-request.com/api/expensive-endpoint")
> .transform().zzz()
>
> .to("http4://or-a-service-that-i-can-call-few-times-a-day.com/api/limited-endpoint")
> .unmarshal()
> .endCache()
> {code}
> It should be also useful to protect internal services when using Camel e.g.
> as a api-gateway (almost what hystrix does in case of failure of the target
> host).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (CAMEL-11534) Incorrect transferExchange option test in camel-jms component
Dmitry Volodin created CAMEL-11534: -- Summary: Incorrect transferExchange option test in camel-jms component Key: CAMEL-11534 URL: https://issues.apache.org/jira/browse/CAMEL-11534 Project: Camel Issue Type: Test Components: camel-jms, tests Affects Versions: 2.19.1, 2.20.0 Reporter: Dmitry Volodin Priority: Minor Fix For: 2.20.0 transferExchange set to 'true' or 'false' doesn't affect to the JUnit test -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11530) RabbitMQ component doesn't handle network failure properly when using autoAck=false and automaticRecovery=true
[
https://issues.apache.org/jira/browse/CAMEL-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081852#comment-16081852
]
Dmitry Volodin commented on CAMEL-11530:
Looks like this is similar to CAMEL-11480
> RabbitMQ component doesn't handle network failure properly when using
> autoAck=false and automaticRecovery=true
> --
>
> Key: CAMEL-11530
> URL: https://issues.apache.org/jira/browse/CAMEL-11530
> Project: Camel
> Issue Type: Bug
> Components: camel-rabbitmq
>Affects Versions: 2.17.6
> Environment: RabbitMQ 3.5.7
>Reporter: Arnaud CHOTARD
> Attachments: channel.png, connections.png, jmx.png, queue.png
>
>
> When using autoAck=false and automaticRecoveryEnabled=true on Camel RabbitMQ
> consumer, we are facing problem during network failure recovery on our
> production environments.
> Before CAMEL-8742, tested with Camel 2.16.2, the automatic recovery is
> managed directly by RabbitMQ native client. When network failure is
> recovering, the old channel is reconnect and messages are proccessed
> correctly.
> After CAMEL-8742, tested with Camel 2.17.6, the Camel RabbitMQ component open
> new channel when network failure is recovering. On the other hand, RabbitMQ
> native client will also reconnect old channels when using
> automaticRecoveryEnabled=true. So two channel are now open. The two recovery
> method make conflict. As consequence, new messages publish in RabbitMQ remain
> unacked and the Camel exchange are not processing on Camel route.
> To recover from this, we should delete, recreate the queue in production
> environment and restart Camel application. So, the unacked messages are being
> lost.
> What do you think of this problem ?
> Thank you
> Camel RabbitMQ Consumer Route :
> {code:java}
> from("rabbitmq:///?" +
> "connectionFactory=#brokerConnectionFactory" +
> "=" + brokerAdresses +
> "="+ brokerQueue +
> "=false" +
> "=false" +
> "=false"
> )
> .bean("", "");
> {code}
> RabbitMQ Connection Factory with automaticRecoveryEnabled=true
> {code}
> class="com.rabbitmq.client.ConnectionFactory">
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11424) Endless wait when unhandled exception occurs in camel-olingo
[ https://issues.apache.org/jira/browse/CAMEL-11424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080955#comment-16080955 ] Dmitry Volodin commented on CAMEL-11424: Sean, please perform following steps for creating PR 1. fork an Apache Camel repo on GitHub 2. on your OS host perform git clone https://github.com//camel.git git remote add origin https://github.com//camel.git git remote add upstream https://github.com/apache/camel.git 3. Fill your user name and email git config --global user.name "John Doe" git config --global user.email john...@example.com 4. git checkout -b CAMEL-11424 5. Change the code 6. git push origin CAMEL-11424 7. Create PR on GitHub from submitted branch > Endless wait when unhandled exception occurs in camel-olingo > > > Key: CAMEL-11424 > URL: https://issues.apache.org/jira/browse/CAMEL-11424 > Project: Camel > Issue Type: Bug > Components: camel-olingo2 >Affects Versions: 2.17.7, 2.19.0 >Reporter: Sean Haynes > Attachments: camel-11424-olingo2.patch, camel-11424-olingo4.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > In Olingo2AppImpl.readContent()/writeContent() if a RuntimeError or any other > unhandled exception/error occurs the wait for response will never get > triggered and the component ends up in an endless wait state. These > functions should be modified to capture any type of throwable/exception/error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11424) Endless wait when unhandled exception occurs in camel-olingo
[ https://issues.apache.org/jira/browse/CAMEL-11424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080594#comment-16080594 ] Dmitry Volodin commented on CAMEL-11424: [~sarhaynes], please pay attention, that camel-olingo4 looks like has the same problem and need to by fixed also. > Endless wait when unhandled exception occurs in camel-olingo > > > Key: CAMEL-11424 > URL: https://issues.apache.org/jira/browse/CAMEL-11424 > Project: Camel > Issue Type: Bug > Components: camel-olingo2 >Affects Versions: 2.17.7, 2.19.0 >Reporter: Sean Haynes > Attachments: camel-11424.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > In Olingo2AppImpl.readContent()/writeContent() if a RuntimeError or any other > unhandled exception/error occurs the wait for response will never get > triggered and the component ends up in an endless wait state. These > functions should be modified to capture any type of throwable/exception/error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11424) Endless wait when unhandled exception occurs in camel-olingo
[ https://issues.apache.org/jira/browse/CAMEL-11424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11424: --- Component/s: camel-olingo4 > Endless wait when unhandled exception occurs in camel-olingo > > > Key: CAMEL-11424 > URL: https://issues.apache.org/jira/browse/CAMEL-11424 > Project: Camel > Issue Type: Bug > Components: camel-olingo2, camel-olingo4 >Affects Versions: 2.17.7, 2.19.0 >Reporter: Sean Haynes > Attachments: camel-11424-olingo2.patch, camel-11424-olingo4.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > In Olingo2AppImpl.readContent()/writeContent() if a RuntimeError or any other > unhandled exception/error occurs the wait for response will never get > triggered and the component ends up in an endless wait state. These > functions should be modified to capture any type of throwable/exception/error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11424) Endless wait when unhandled exception occurs in camel-olingo
[ https://issues.apache.org/jira/browse/CAMEL-11424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080610#comment-16080610 ] Dmitry Volodin commented on CAMEL-11424: Sean, it would be nice to use GitHub pull request (PR) rather than patch. Please submit them each one per issue. Thank you. > Endless wait when unhandled exception occurs in camel-olingo > > > Key: CAMEL-11424 > URL: https://issues.apache.org/jira/browse/CAMEL-11424 > Project: Camel > Issue Type: Bug > Components: camel-olingo2 >Affects Versions: 2.17.7, 2.19.0 >Reporter: Sean Haynes > Attachments: camel-11424.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > In Olingo2AppImpl.readContent()/writeContent() if a RuntimeError or any other > unhandled exception/error occurs the wait for response will never get > triggered and the component ends up in an endless wait state. These > functions should be modified to capture any type of throwable/exception/error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11527) camel-olingo2 uses upper-case UTF-7 as Accept header instead of lower case utf-7
[
https://issues.apache.org/jira/browse/CAMEL-11527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080094#comment-16080094
]
Dmitry Volodin commented on CAMEL-11527:
[~jpoth] camel-olingo2 component and OData 2.0 format are still actively using
Please also note, that camel-olingo4 component has the same problem and need to
be fixed.
Can you fix camel-olingo4 in the same PR?
> camel-olingo2 uses upper-case UTF-7 as Accept header instead of lower case
> utf-7
>
>
> Key: CAMEL-11527
> URL: https://issues.apache.org/jira/browse/CAMEL-11527
> Project: Camel
> Issue Type: Bug
> Components: camel-olingo2
>Affects Versions: 2.19.1
>Reporter: John Poth
>
> Not sure if this component is still used/should be deprecated but I have the
> fix locally so might as well :)
> The problem is that odata2 services are expecting lower-case
> [ut7|http://grepcode.com/file/repo1.maven.org/maven2/org.apache.olingo/olingo-odata2-core-incubating/1.0.0/org/apache/olingo/odata2/core/commons/ContentType.java#112]
> as Accept header while we provide UTF-7 which produces the following error:
> {code}
> org.apache.camel.RuntimeCamelException: Error reading EDM: No match for
> accept header
> at
> org.apache.camel.component.olingo2.Olingo2AppWrapper.getEdm(Olingo2AppWrapper.java:93)
> [226:org.apache.camel.camel-olingo2:2.20.0.SNAPSHOT]
> at
> org.apache.camel.component.olingo2.Olingo2Endpoint.interceptProperties(Olingo2Endpoint.java:163)
> [226:org.apache.camel.camel-olingo2:2.20.0.SNAPSHOT]
> at
> org.apache.camel.component.olingo2.Olingo2Producer.process(Olingo2Producer.java:53)
> [226:org.apache.camel.camel-olingo2:2.20.0.SNAPSHOT]
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> [57:org.apache.camel.camel-core:2.20.0.SNAPSHOT]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [57:org.apache.camel.camel-core:2.20.0.SNAPSHOT]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [57:org.apache.camel.camel-core:2.20.0.SNAPSHOT]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
> [57:org.apache.camel.camel-core:2.20.0.SNAPSHOT]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> [57:org.apache.camel.camel-core:2.20.0.SNAPSHOT]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [57:org.apache.camel.camel-core:2.20.0.SNAPSHOT]
> at
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:451)
> [57:org.apache.camel.camel-core:2.20.0.SNAPSHOT]
> at
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:218)
> [57:org.apache.camel.camel-core:2.20.0.SNAPSHOT]
> at
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:182)
> [57:org.apache.camel.camel-core:2.20.0.SNAPSHOT]
> at
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
> [57:org.apache.camel.camel-core:2.20.0.SNAPSHOT]
> at
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
> [57:org.apache.camel.camel-core:2.20.0.SNAPSHOT]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> [?:?]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> [?:?]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:?]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> Caused by: org.apache.olingo.odata2.api.exception.ODataApplicationException:
> No match for accept header
> at
> org.apache.camel.component.olingo2.api.impl.AbstractFutureCallback.checkStatus(AbstractFutureCallback.java:65)
> ~[?:?]
> at
> org.apache.camel.component.olingo2.api.impl.AbstractFutureCallback.completed(AbstractFutureCallback.java:84)
> ~[?:?]
> at
> org.apache.camel.component.olingo2.api.impl.AbstractFutureCallback.completed(AbstractFutureCallback.java:41)
> ~[?:?]
> at
> org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:119) ~[?:?]
> at
> org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:181)
> ~[?:?]
>
[jira] [Created] (CAMEL-11569) Implements CAMEL-11425 for camel-olingo4
Dmitry Volodin created CAMEL-11569: -- Summary: Implements CAMEL-11425 for camel-olingo4 Key: CAMEL-11569 URL: https://issues.apache.org/jira/browse/CAMEL-11569 Project: Camel Issue Type: Improvement Components: camel-olingo4 Affects Versions: 2.20.0 Reporter: Dmitry Volodin Assignee: Dmitry Volodin Fix For: 2.20.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (CAMEL-11569) Implements CAMEL-11425 for camel-olingo4
[ https://issues.apache.org/jira/browse/CAMEL-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11569 started by Dmitry Volodin. -- > Implements CAMEL-11425 for camel-olingo4 > > > Key: CAMEL-11569 > URL: https://issues.apache.org/jira/browse/CAMEL-11569 > Project: Camel > Issue Type: Improvement > Components: camel-olingo4 >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11605) Invalid accept header
[ https://issues.apache.org/jira/browse/CAMEL-11605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11605: --- Fix Version/s: 2.20.0 > Invalid accept header > - > > Key: CAMEL-11605 > URL: https://issues.apache.org/jira/browse/CAMEL-11605 > Project: Camel > Issue Type: Bug > Components: camel-olingo4 >Affects Versions: 2.20.0 >Reporter: Marc Giger >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > Attachments: accept-header.diff > > > Commit 958f7f33fa40868dec6a878f1c97f6d7339a9b3b introduced a regression > to olingo4 (maybe olingo2 is also affected, not tested). > The ACCEPT header doesn't include the subtype anymore: > ACCEPT: application > Should be ACCEPT: application/json for example. > Patch for olingo4 attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11605) Invalid accept header
[ https://issues.apache.org/jira/browse/CAMEL-11605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102883#comment-16102883 ] Dmitry Volodin commented on CAMEL-11605: [~giger], thanks for patch, PR submitted! > Invalid accept header > - > > Key: CAMEL-11605 > URL: https://issues.apache.org/jira/browse/CAMEL-11605 > Project: Camel > Issue Type: Bug > Components: camel-olingo4 >Affects Versions: 2.20.0 >Reporter: Marc Giger >Assignee: Dmitry Volodin > Attachments: accept-header.diff > > > Commit 958f7f33fa40868dec6a878f1c97f6d7339a9b3b introduced a regression > to olingo4 (maybe olingo2 is also affected, not tested). > The ACCEPT header doesn't include the subtype anymore: > ACCEPT: application > Should be ACCEPT: application/json for example. > Patch for olingo4 attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11605) Invalid accept header
[ https://issues.apache.org/jira/browse/CAMEL-11605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-11605: -- Assignee: Dmitry Volodin > Invalid accept header > - > > Key: CAMEL-11605 > URL: https://issues.apache.org/jira/browse/CAMEL-11605 > Project: Camel > Issue Type: Bug > Components: camel-olingo4 >Affects Versions: 2.20.0 >Reporter: Marc Giger >Assignee: Dmitry Volodin > Attachments: accept-header.diff > > > Commit 958f7f33fa40868dec6a878f1c97f6d7339a9b3b introduced a regression > to olingo4 (maybe olingo2 is also affected, not tested). > The ACCEPT header doesn't include the subtype anymore: > ACCEPT: application > Should be ACCEPT: application/json for example. > Patch for olingo4 attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (CAMEL-11605) Invalid accept header
[ https://issues.apache.org/jira/browse/CAMEL-11605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11605 started by Dmitry Volodin. -- > Invalid accept header > - > > Key: CAMEL-11605 > URL: https://issues.apache.org/jira/browse/CAMEL-11605 > Project: Camel > Issue Type: Bug > Components: camel-olingo4 >Affects Versions: 2.20.0 >Reporter: Marc Giger >Assignee: Dmitry Volodin > Attachments: accept-header.diff > > > Commit 958f7f33fa40868dec6a878f1c97f6d7339a9b3b introduced a regression > to olingo4 (maybe olingo2 is also affected, not tested). > The ACCEPT header doesn't include the subtype anymore: > ACCEPT: application > Should be ACCEPT: application/json for example. > Patch for olingo4 attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11597) Adding support for setting authentication client properties for elasticsearch
[
https://issues.apache.org/jira/browse/CAMEL-11597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-11597:
--
Assignee: (was: Dmitry Volodin)
> Adding support for setting authentication client properties for elasticsearch
> -
>
> Key: CAMEL-11597
> URL: https://issues.apache.org/jira/browse/CAMEL-11597
> Project: Camel
> Issue Type: Improvement
> Components: camel-elasticsearch5
>Affects Versions: 2.20.0
>Reporter: Flemming Harms
>Priority: Minor
>
> The current implementation does not allow to override the client instance or
> setup client authentication.
> Adding following additional properties for support authentication
> {code:java}
> final Settings.Builder settings = Settings.builder()
> .put("cluster.name", configuration.getClusterName())
> .put("client.transport.ignore_cluster_name", false)
> .put("client.transport.sniff", configuration.getClientTransportSniff())
> .put("transport.ping_schedule", configuration.getPingSchedule())
> .put("client.transport.ping_timeout", configuration.getPingTimeout())
> .put("client.transport.sniff", configuration.getClientTransportSniff())
> .put("xpack.security.transport.ssl.enabled", configuration.getEnabledSSL())
> .put("request.headers.X-Found-Cluster", configuration.getClusterName());
> if (configuration.getUser() != null && configuration.getPassword() != null)
> {
> settings.put("xpack.security.user", configuration.getUser() +":"+
> configuration.getPassword());
>}
>return settings.build();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (CAMEL-11597) Adding support for setting authentication client properties for elasticsearch
[
https://issues.apache.org/jira/browse/CAMEL-11597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-11597:
--
Assignee: Dmitry Volodin
> Adding support for setting authentication client properties for elasticsearch
> -
>
> Key: CAMEL-11597
> URL: https://issues.apache.org/jira/browse/CAMEL-11597
> Project: Camel
> Issue Type: Improvement
> Components: camel-elasticsearch5
>Affects Versions: 2.20.0
>Reporter: Flemming Harms
>Assignee: Dmitry Volodin
>Priority: Minor
>
> The current implementation does not allow to override the client instance or
> setup client authentication.
> Adding following additional properties for support authentication
> {code:java}
> final Settings.Builder settings = Settings.builder()
> .put("cluster.name", configuration.getClusterName())
> .put("client.transport.ignore_cluster_name", false)
> .put("client.transport.sniff", configuration.getClientTransportSniff())
> .put("transport.ping_schedule", configuration.getPingSchedule())
> .put("client.transport.ping_timeout", configuration.getPingTimeout())
> .put("client.transport.sniff", configuration.getClientTransportSniff())
> .put("xpack.security.transport.ssl.enabled", configuration.getEnabledSSL())
> .put("request.headers.X-Found-Cluster", configuration.getClusterName());
> if (configuration.getUser() != null && configuration.getPassword() != null)
> {
> settings.put("xpack.security.user", configuration.getUser() +":"+
> configuration.getPassword());
>}
>return settings.build();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (CAMEL-11517) transferExchange option doesn't work as expected
[ https://issues.apache.org/jira/browse/CAMEL-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin closed CAMEL-11517. -- Resolution: Not A Problem > transferExchange option doesn't work as expected > > > Key: CAMEL-11517 > URL: https://issues.apache.org/jira/browse/CAMEL-11517 > Project: Camel > Issue Type: Bug > Components: camel-jms >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Labels: test > Attachments: amq-screenshot.png > > > I've tested a camel-amqp component with ActiveMQ Artemis (AMQ) system and > detected that all Camel Headers (in my case CamelHttp* ) were propagated > inside the message properties. > Next, changed some (JmsTransferExchangeTest, JmsInOutTransferExchangeTest) > transferExchange related tests (from 'transferExchange=true' to > 'transferExchange=false') and all test were passed successfully that looks > very strange. > This issue need to be verify. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11517) transferExchange option doesn't work as expected
[ https://issues.apache.org/jira/browse/CAMEL-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076350#comment-16076350 ] Dmitry Volodin commented on CAMEL-11517: It's expected behavior and transferExchange option works as defined, however tests are not correctly implemented. All Camel headers are propagated to JMS (AMQ) and headerFilterStrategy need to be specified for disabling header propagation. A new issue for fixing tests will create. > transferExchange option doesn't work as expected > > > Key: CAMEL-11517 > URL: https://issues.apache.org/jira/browse/CAMEL-11517 > Project: Camel > Issue Type: Bug > Components: camel-jms >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Labels: test > Attachments: amq-screenshot.png > > > I've tested a camel-amqp component with ActiveMQ Artemis (AMQ) system and > detected that all Camel Headers (in my case CamelHttp* ) were propagated > inside the message properties. > Next, changed some (JmsTransferExchangeTest, JmsInOutTransferExchangeTest) > transferExchange related tests (from 'transferExchange=true' to > 'transferExchange=false') and all test were passed successfully that looks > very strange. > This issue need to be verify. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11517) transferExchange option doesn't work as expected
Dmitry Volodin created CAMEL-11517: -- Summary: transferExchange option doesn't work as expected Key: CAMEL-11517 URL: https://issues.apache.org/jira/browse/CAMEL-11517 Project: Camel Issue Type: Bug Components: camel-activemq, camel-amqp, camel-jms Affects Versions: 2.20.0 Reporter: Dmitry Volodin Priority: Minor Attachments: amq-screenshot.png I've tested a camel-amqp component with ActiveMQ Artemis (AMQ) system and detected that all Camel Headers (in my case CamelCxf* and other HTTP related) were propagated inside the message properties. Next, changed some (JmsTransferExchangeTest, JmsInOutTransferExchangeTest) transferExchange related tests (from 'transferExchange=true' to 'transferExchange=false') and all test were passed successfully that looks very strange. This issue need to be verify. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11517) transferExchange option doesn't work as expected
[ https://issues.apache.org/jira/browse/CAMEL-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11517: --- Attachment: amq-screenshot.png > transferExchange option doesn't work as expected > > > Key: CAMEL-11517 > URL: https://issues.apache.org/jira/browse/CAMEL-11517 > Project: Camel > Issue Type: Bug > Components: camel-activemq, camel-amqp, camel-jms >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Priority: Minor > Attachments: amq-screenshot.png > > > I've tested a camel-amqp component with ActiveMQ Artemis (AMQ) system and > detected that all Camel Headers (in my case CamelCxf* and other HTTP related) > were propagated inside the message properties. > Next, changed some (JmsTransferExchangeTest, JmsInOutTransferExchangeTest) > transferExchange related tests (from 'transferExchange=true' to > 'transferExchange=false') and all test were passed successfully that looks > very strange. > This issue need to be verify. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11517) transferExchange option doesn't work as expected
[ https://issues.apache.org/jira/browse/CAMEL-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11517: --- Description: I've tested a camel-amqp component with ActiveMQ Artemis (AMQ) system and detected that all Camel Headers (in my case CamelHttp* ) were propagated inside the message properties. Next, changed some (JmsTransferExchangeTest, JmsInOutTransferExchangeTest) transferExchange related tests (from 'transferExchange=true' to 'transferExchange=false') and all test were passed successfully that looks very strange. This issue need to be verify. was: I've tested a camel-amqp component with ActiveMQ Artemis (AMQ) system and detected that all Camel Headers (in my case CamelCxf* and other HTTP related) were propagated inside the message properties. Next, changed some (JmsTransferExchangeTest, JmsInOutTransferExchangeTest) transferExchange related tests (from 'transferExchange=true' to 'transferExchange=false') and all test were passed successfully that looks very strange. This issue need to be verify. > transferExchange option doesn't work as expected > > > Key: CAMEL-11517 > URL: https://issues.apache.org/jira/browse/CAMEL-11517 > Project: Camel > Issue Type: Bug > Components: camel-activemq, camel-amqp, camel-jms >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Priority: Minor > Attachments: amq-screenshot.png > > > I've tested a camel-amqp component with ActiveMQ Artemis (AMQ) system and > detected that all Camel Headers (in my case CamelHttp* ) were propagated > inside the message properties. > Next, changed some (JmsTransferExchangeTest, JmsInOutTransferExchangeTest) > transferExchange related tests (from 'transferExchange=true' to > 'transferExchange=false') and all test were passed successfully that looks > very strange. > This issue need to be verify. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11517) transferExchange option doesn't work as expected
[ https://issues.apache.org/jira/browse/CAMEL-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-11517: -- Assignee: Dmitry Volodin > transferExchange option doesn't work as expected > > > Key: CAMEL-11517 > URL: https://issues.apache.org/jira/browse/CAMEL-11517 > Project: Camel > Issue Type: Bug > Components: camel-activemq, camel-amqp, camel-jms >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Attachments: amq-screenshot.png > > > I've tested a camel-amqp component with ActiveMQ Artemis (AMQ) system and > detected that all Camel Headers (in my case CamelHttp* ) were propagated > inside the message properties. > Next, changed some (JmsTransferExchangeTest, JmsInOutTransferExchangeTest) > transferExchange related tests (from 'transferExchange=true' to > 'transferExchange=false') and all test were passed successfully that looks > very strange. > This issue need to be verify. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11517) transferExchange option doesn't work as expected
[ https://issues.apache.org/jira/browse/CAMEL-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11517: --- Component/s: (was: camel-amqp) (was: camel-activemq) > transferExchange option doesn't work as expected > > > Key: CAMEL-11517 > URL: https://issues.apache.org/jira/browse/CAMEL-11517 > Project: Camel > Issue Type: Bug > Components: camel-jms >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Labels: test > Attachments: amq-screenshot.png > > > I've tested a camel-amqp component with ActiveMQ Artemis (AMQ) system and > detected that all Camel Headers (in my case CamelHttp* ) were propagated > inside the message properties. > Next, changed some (JmsTransferExchangeTest, JmsInOutTransferExchangeTest) > transferExchange related tests (from 'transferExchange=true' to > 'transferExchange=false') and all test were passed successfully that looks > very strange. > This issue need to be verify. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11517) transferExchange option doesn't work as expected
[ https://issues.apache.org/jira/browse/CAMEL-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11517: --- Labels: test (was: ) > transferExchange option doesn't work as expected > > > Key: CAMEL-11517 > URL: https://issues.apache.org/jira/browse/CAMEL-11517 > Project: Camel > Issue Type: Bug > Components: camel-jms >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Labels: test > Attachments: amq-screenshot.png > > > I've tested a camel-amqp component with ActiveMQ Artemis (AMQ) system and > detected that all Camel Headers (in my case CamelHttp* ) were propagated > inside the message properties. > Next, changed some (JmsTransferExchangeTest, JmsInOutTransferExchangeTest) > transferExchange related tests (from 'transferExchange=true' to > 'transferExchange=false') and all test were passed successfully that looks > very strange. > This issue need to be verify. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11174) REST-DSL support for Google Protobuf
[ https://issues.apache.org/jira/browse/CAMEL-11174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15985253#comment-15985253 ] Dmitry Volodin commented on CAMEL-11174: Hi Luis! It's a not a good idea to overload core and rest-dsl subsystems with non-typical functions, i.e. marshal/unmarshal third-party binary formats, etc. As camel supports protobuf format OOB, you could create a very simple route like this for implementing described scenario: http://camel.apache.org/schema/spring;> P.S. The gRPC or Thrift RPC are working much quickly, however your case is good example to be implemented as sample. > REST-DSL support for Google Protobuf > > > Key: CAMEL-11174 > URL: https://issues.apache.org/jira/browse/CAMEL-11174 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Luis > > It would be nice to be able to output something other that just XML/JSON > from a camel rest dsl route, namely Google Protobuf or Apache thrift. > The idea would be that one could have addional MIME types add one could > define how they are handled. > So for example application/x-protobuf could be handle by Protobuf. > One example article that comes to mind is: > https://javarants.com/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis-563ce40d15d9 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-11174) REST-DSL support for Google Protobuf
[
https://issues.apache.org/jira/browse/CAMEL-11174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15985253#comment-15985253
]
Dmitry Volodin edited comment on CAMEL-11174 at 4/26/17 6:05 PM:
-
Hi Luis!
It's a not a good idea to overload core and rest-dsl subsystems with
non-typical functions, i.e. marshal/unmarshal third-party binary formats, etc.
As camel supports protobuf format OOB, you could create a very simple route
like this for implementing described scenario:
{code:xml}
http://camel.apache.org/schema/spring;>
{code}
P.S. The gRPC or Thrift RPC are working much quickly, however your case is good
example to be implemented as sample.
was (Author: dmvolod):
Hi Luis!
It's a not a good idea to overload core and rest-dsl subsystems with
non-typical functions, i.e. marshal/unmarshal third-party binary formats, etc.
As camel supports protobuf format OOB, you could create a very simple route
like this for implementing described scenario:
http://camel.apache.org/schema/spring;>
P.S. The gRPC or Thrift RPC are working much quickly, however your case is good
example to be implemented as sample.
> REST-DSL support for Google Protobuf
>
>
> Key: CAMEL-11174
> URL: https://issues.apache.org/jira/browse/CAMEL-11174
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Luis
>
> It would be nice to be able to output something other that just XML/JSON
> from a camel rest dsl route, namely Google Protobuf or Apache thrift.
> The idea would be that one could have addional MIME types add one could
> define how they are handled.
> So for example application/x-protobuf could be handle by Protobuf.
> One example article that comes to mind is:
> https://javarants.com/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis-563ce40d15d9
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-11174) REST-DSL support for Google Protobuf
[
https://issues.apache.org/jira/browse/CAMEL-11174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15985253#comment-15985253
]
Dmitry Volodin edited comment on CAMEL-11174 at 4/26/17 7:36 PM:
-
Hi Luis!
It's not a good idea to overload core and rest-dsl subsystems with non-typical
functions, i.e. marshal/unmarshal third-party binary formats, etc. As camel
supports protobuf format OOB, you could create a very simple route like this
for implementing described scenario:
{code:xml}
http://camel.apache.org/schema/spring;>
{code}
P.S. The gRPC or Thrift RPC are working much faster, however your case is good
example to be implemented as sample.
was (Author: dmvolod):
Hi Luis!
It's a not a good idea to overload core and rest-dsl subsystems with
non-typical functions, i.e. marshal/unmarshal third-party binary formats, etc.
As camel supports protobuf format OOB, you could create a very simple route
like this for implementing described scenario:
{code:xml}
http://camel.apache.org/schema/spring;>
{code}
P.S. The gRPC or Thrift RPC are working much quickly, however your case is good
example to be implemented as sample.
> REST-DSL support for Google Protobuf
>
>
> Key: CAMEL-11174
> URL: https://issues.apache.org/jira/browse/CAMEL-11174
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Luis
>
> It would be nice to be able to output something other that just XML/JSON
> from a camel rest dsl route, namely Google Protobuf or Apache thrift.
> The idea would be that one could have addional MIME types add one could
> define how they are handled.
> So for example application/x-protobuf could be handle by Protobuf.
> One example article that comes to mind is:
> https://javarants.com/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis-563ce40d15d9
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (CAMEL-11213) camel-grpc doesn't terminate channel when producer stops
Dmitry Volodin created CAMEL-11213: -- Summary: camel-grpc doesn't terminate channel when producer stops Key: CAMEL-11213 URL: https://issues.apache.org/jira/browse/CAMEL-11213 Project: Camel Issue Type: Bug Components: camel-grpc Reporter: Dmitry Volodin Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11213) camel-grpc doesn't terminate channel when producer stops
[ https://issues.apache.org/jira/browse/CAMEL-11213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15986712#comment-15986712 ] Dmitry Volodin commented on CAMEL-11213: This can cause memory leaks > camel-grpc doesn't terminate channel when producer stops > - > > Key: CAMEL-11213 > URL: https://issues.apache.org/jira/browse/CAMEL-11213 > Project: Camel > Issue Type: Bug > Components: camel-grpc >Reporter: Dmitry Volodin >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11174) REST-DSL support for Google Protobuf
[ https://issues.apache.org/jira/browse/CAMEL-11174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987025#comment-15987025 ] Dmitry Volodin commented on CAMEL-11174: Thanks for ideas Luis! As camel-grpc client component will be released as part of 2.19 build, we are working on the native server implementation now. Looks like a new camel-grpc-gateway component need to be implemented and integrated with swagger-rest-dsl-generator Please also note, that starting 2.19 camel-protobuf data format able to marshal/unmarshal from/to JSON in advance to binary data. > REST-DSL support for Google Protobuf > > > Key: CAMEL-11174 > URL: https://issues.apache.org/jira/browse/CAMEL-11174 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Luis > > It would be nice to be able to output something other that just XML/JSON > from a camel rest dsl route, namely Google Protobuf or Apache thrift. > The idea would be that one could have addional MIME types add one could > define how they are handled. > So for example application/x-protobuf could be handle by Protobuf. > One example article that comes to mind is: > https://javarants.com/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis-563ce40d15d9 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-11696) Add security and advanced properties to the camel-thrift component
Dmitry Volodin created CAMEL-11696: -- Summary: Add security and advanced properties to the camel-thrift component Key: CAMEL-11696 URL: https://issues.apache.org/jira/browse/CAMEL-11696 Project: Camel Issue Type: Sub-task Reporter: Dmitry Volodin Assignee: Dmitry Volodin Priority: Minor Add advanced properties available in Apache Thrift library as well as security (auth, SSL, etc.) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11695) Add security and advanced properties to the camel-grpc component
Dmitry Volodin created CAMEL-11695: -- Summary: Add security and advanced properties to the camel-grpc component Key: CAMEL-11695 URL: https://issues.apache.org/jira/browse/CAMEL-11695 Project: Camel Issue Type: Sub-task Components: camel-grpc Reporter: Dmitry Volodin Assignee: Dmitry Volodin Priority: Minor Add advanced properties available in gRPC library as well as security (auth, SSL, etc.) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (CAMEL-11695) Add security and advanced properties to the camel-grpc component
[ https://issues.apache.org/jira/browse/CAMEL-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11695 started by Dmitry Volodin. -- > Add security and advanced properties to the camel-grpc component > > > Key: CAMEL-11695 > URL: https://issues.apache.org/jira/browse/CAMEL-11695 > Project: Camel > Issue Type: Sub-task > Components: camel-grpc >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 2.20.0 > > > Add advanced properties available in gRPC library as well as security (auth, > SSL, etc.) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (CAMEL-11696) Add security and advanced properties to the camel-thrift component
[ https://issues.apache.org/jira/browse/CAMEL-11696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11696 started by Dmitry Volodin. -- > Add security and advanced properties to the camel-thrift component > -- > > Key: CAMEL-11696 > URL: https://issues.apache.org/jira/browse/CAMEL-11696 > Project: Camel > Issue Type: Sub-task >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Labels: rpc, thrift > Fix For: 2.20.0 > > > Add advanced properties available in Apache Thrift library as well as > security (auth, SSL, etc.) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11288) camel-grpc producer incorrectly called async services
[ https://issues.apache.org/jira/browse/CAMEL-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-11288: -- Assignee: Dmitry Volodin > camel-grpc producer incorrectly called async services > - > > Key: CAMEL-11288 > URL: https://issues.apache.org/jira/browse/CAMEL-11288 > Project: Camel > Issue Type: Bug > Components: camel-grpc >Affects Versions: 2.19.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Critical > > Error occurs when calling procedures with async (stream incoming and outgoing > parameters). This is not handled as expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11288) camel-grpc producer incorrectly called async services
[ https://issues.apache.org/jira/browse/CAMEL-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16012675#comment-16012675 ] Dmitry Volodin commented on CAMEL-11288: It would be nice to backport this issue to the 2.19.1 after merge > camel-grpc producer incorrectly called async services > - > > Key: CAMEL-11288 > URL: https://issues.apache.org/jira/browse/CAMEL-11288 > Project: Camel > Issue Type: Bug > Components: camel-grpc >Affects Versions: 2.19.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Critical > > Error occurs when calling procedures with async (stream incoming and outgoing > parameters). This is not handled as expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11432) Unable to skip tests when building camel-grpc
[
https://issues.apache.org/jira/browse/CAMEL-11432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057506#comment-16057506
]
Dmitry Volodin commented on CAMEL-11432:
camel-prorobuf has the same problem, need to be fixed
> Unable to skip tests when building camel-grpc
> -
>
> Key: CAMEL-11432
> URL: https://issues.apache.org/jira/browse/CAMEL-11432
> Project: Camel
> Issue Type: Improvement
> Components: camel-grpc
>Reporter: James Netherton
>Assignee: Dmitry Volodin
>Priority: Trivial
> Fix For: 2.20.0
>
>
> The groovy script within the camel-grpc component pom.xml does not take into
> consideration whether the user ran the build with {{-DskipTests}}. Thus tests
> are always executed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (CAMEL-11432) Unable to skip tests when building camel-grpc
[
https://issues.apache.org/jira/browse/CAMEL-11432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-11432:
--
Assignee: Dmitry Volodin
> Unable to skip tests when building camel-grpc
> -
>
> Key: CAMEL-11432
> URL: https://issues.apache.org/jira/browse/CAMEL-11432
> Project: Camel
> Issue Type: Improvement
> Components: camel-grpc
>Reporter: James Netherton
>Assignee: Dmitry Volodin
>Priority: Trivial
> Fix For: 2.20.0
>
>
> The groovy script within the camel-grpc component pom.xml does not take into
> consideration whether the user ran the build with {{-DskipTests}}. Thus tests
> are always executed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (CAMEL-11432) Unable to skip tests when building camel-grpc
[
https://issues.apache.org/jira/browse/CAMEL-11432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-11432:
--
Assignee: (was: Dmitry Volodin)
> Unable to skip tests when building camel-grpc
> -
>
> Key: CAMEL-11432
> URL: https://issues.apache.org/jira/browse/CAMEL-11432
> Project: Camel
> Issue Type: Improvement
> Components: camel-grpc
>Reporter: James Netherton
>Priority: Trivial
> Fix For: 2.20.0
>
>
> The groovy script within the camel-grpc component pom.xml does not take into
> consideration whether the user ran the build with {{-DskipTests}}. Thus tests
> are always executed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11419) Camel IgniteComponent fails to create cache with underscore e.g cache_name
[
https://issues.apache.org/jira/browse/CAMEL-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16059627#comment-16059627
]
Dmitry Volodin commented on CAMEL-11419:
Please provide more info about Camel version you are using and detail test case.
With the latest Camel snapshot, I tried to add following test to the JUnit
IgniteCacheTest and it has passed successfully
{code:java}
@Test
public void testAddEntryUnderscoreCacheName) {
template.requestBodyAndHeader("ignite-cache:test_cache?operation=PUT",
"1234",
IgniteConstants.IGNITE_CACHE_KEY, "abcd");
assert_().that(ignite().cache("test_cache").size(CachePeekMode.ALL)).isEqualTo(1);
assert_().that(ignite().cache("test_cache").get("abcd")).isEqualTo("1234");
}
{code}
> Camel IgniteComponent fails to create cache with underscore e.g cache_name
> ---
>
> Key: CAMEL-11419
> URL: https://issues.apache.org/jira/browse/CAMEL-11419
> Project: Camel
> Issue Type: Bug
> Components: camel-ignite
>Reporter: LAXMIKANT KAMATH
>
> Camel IgniteComponent fails to create cache with underscore e.g cache_name
> IgniteComponent igniteComponent =
> IgniteComponent.fromLocation(igniteClientConfig);
> main.bind("ignite", igniteComponent);
> main.run();
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Work started] (CAMEL-11436) camel-spring-ldap - Has test failures
[ https://issues.apache.org/jira/browse/CAMEL-11436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11436 started by Dmitry Volodin. -- > camel-spring-ldap - Has test failures > - > > Key: CAMEL-11436 > URL: https://issues.apache.org/jira/browse/CAMEL-11436 > Project: Camel > Issue Type: Test >Affects Versions: 2.20.0 >Reporter: Claus Ibsen >Assignee: Dmitry Volodin > > This module fails testing for me in all its tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11436) camel-spring-ldap - Has test failures
[ https://issues.apache.org/jira/browse/CAMEL-11436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-11436: -- Assignee: Dmitry Volodin > camel-spring-ldap - Has test failures > - > > Key: CAMEL-11436 > URL: https://issues.apache.org/jira/browse/CAMEL-11436 > Project: Camel > Issue Type: Test >Affects Versions: 2.20.0 >Reporter: Claus Ibsen >Assignee: Dmitry Volodin > > This module fails testing for me in all its tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11456) Make the camel-grpc component more cloud service friendly
[ https://issues.apache.org/jira/browse/CAMEL-11456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-11456: -- Assignee: Dmitry Volodin > Make the camel-grpc component more cloud service friendly > - > > Key: CAMEL-11456 > URL: https://issues.apache.org/jira/browse/CAMEL-11456 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > > Change an URI to be able expose and call component in cloud service > infrastructure easy > Now, the component URI is looks like grpc:host:port/service instead of > passing host and port via parameters -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (CAMEL-11456) Make the camel-grpc component more cloud service friendly
[ https://issues.apache.org/jira/browse/CAMEL-11456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11456 started by Dmitry Volodin. -- > Make the camel-grpc component more cloud service friendly > - > > Key: CAMEL-11456 > URL: https://issues.apache.org/jira/browse/CAMEL-11456 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > > Change an URI to be able expose and call component in cloud service > infrastructure easy > Now, the component URI is looks like grpc:host:port/service instead of > passing host and port via parameters -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11456) Make the camel-grpc component more cloud service friendly
Dmitry Volodin created CAMEL-11456: -- Summary: Make the camel-grpc component more cloud service friendly Key: CAMEL-11456 URL: https://issues.apache.org/jira/browse/CAMEL-11456 Project: Camel Issue Type: Improvement Components: camel-grpc Reporter: Dmitry Volodin Priority: Minor Change an URI to be able expose and call component in cloud service infrastructure easy Now, the component URI is looks like grpc:host:port/service instead of passing host and port via parameters -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11333) Create a new camel-thrift RPC component
[ https://issues.apache.org/jira/browse/CAMEL-11333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin resolved CAMEL-11333. Resolution: Fixed > Create a new camel-thrift RPC component > --- > > Key: CAMEL-11333 > URL: https://issues.apache.org/jira/browse/CAMEL-11333 > Project: Camel > Issue Type: Sub-task >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Labels: rpc, thrift > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11343) gRPC component cannot load service class
[
https://issues.apache.org/jira/browse/CAMEL-11343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-11343:
---
Fix Version/s: 2.20.0
2.19.1
> gRPC component cannot load service class
>
>
> Key: CAMEL-11343
> URL: https://issues.apache.org/jira/browse/CAMEL-11343
> Project: Camel
> Issue Type: Improvement
> Components: camel-grpc
>Affects Versions: 2.19.0
>Reporter: James Netherton
>Assignee: Dmitry Volodin
> Fix For: 2.19.1, 2.20.0
>
>
> Class {{GrpcUtils}} does:
> {code}
> Class grpcServiceClass = Class.forName(serviceClassName);
> {code}
> Unfortunately, that causes the class loading to be done from the
> {{GrpcUtils}} {{ClassLoader}}, which may not be appropriate in modular
> environments (OSGi, JavaEE, etc)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (CAMEL-11343) gRPC component cannot load service class
[
https://issues.apache.org/jira/browse/CAMEL-11343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-11343:
--
Assignee: Dmitry Volodin (was: James Netherton)
> gRPC component cannot load service class
>
>
> Key: CAMEL-11343
> URL: https://issues.apache.org/jira/browse/CAMEL-11343
> Project: Camel
> Issue Type: Improvement
> Components: camel-grpc
>Affects Versions: 2.19.0
>Reporter: James Netherton
>Assignee: Dmitry Volodin
> Fix For: 2.19.1, 2.20.0
>
>
> Class {{GrpcUtils}} does:
> {code}
> Class grpcServiceClass = Class.forName(serviceClassName);
> {code}
> Unfortunately, that causes the class loading to be done from the
> {{GrpcUtils}} {{ClassLoader}}, which may not be appropriate in modular
> environments (OSGi, JavaEE, etc)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CAMEL-11343) gRPC component cannot load service class
[
https://issues.apache.org/jira/browse/CAMEL-11343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-11343:
---
Fix Version/s: (was: 2.19.1)
> gRPC component cannot load service class
>
>
> Key: CAMEL-11343
> URL: https://issues.apache.org/jira/browse/CAMEL-11343
> Project: Camel
> Issue Type: Improvement
> Components: camel-grpc
>Affects Versions: 2.19.0
>Reporter: James Netherton
>Assignee: Dmitry Volodin
> Fix For: 2.20.0
>
>
> Class {{GrpcUtils}} does:
> {code}
> Class grpcServiceClass = Class.forName(serviceClassName);
> {code}
> Unfortunately, that causes the class loading to be done from the
> {{GrpcUtils}} {{ClassLoader}}, which may not be appropriate in modular
> environments (OSGi, JavaEE, etc)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CAMEL-11345) Remove dependency on spring-core from gRPC component
[ https://issues.apache.org/jira/browse/CAMEL-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026452#comment-16026452 ] Dmitry Volodin commented on CAMEL-11345: [~jamesnetherton], as for as I understand, org.springframework.util.ReflectionUtils are using inside camel-sql, camel-spring and camel-hdfs (via wrapper). It's much easy to use this utils rather than Java reflection API (was in camel-grpc in early build) However there are no limitation to back original Java reflection API > Remove dependency on spring-core from gRPC component > > > Key: CAMEL-11345 > URL: https://issues.apache.org/jira/browse/CAMEL-11345 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: James Netherton >Priority: Trivial > > As far as I can tell, Spring is only used in the gRPC component to pull in > some utility classes: > org.springframework.util.ObjectUtils > org.springframework.util.ReflectionUtils > Can we not replace these with equivalent Camel util classes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11343) gRPC component cannot load service class
[
https://issues.apache.org/jira/browse/CAMEL-11343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026472#comment-16026472
]
Dmitry Volodin commented on CAMEL-11343:
Camel 2.19.1. requires separate PR (based on camel-2.19.x branch)
> gRPC component cannot load service class
>
>
> Key: CAMEL-11343
> URL: https://issues.apache.org/jira/browse/CAMEL-11343
> Project: Camel
> Issue Type: Improvement
> Components: camel-grpc
>Affects Versions: 2.19.0
>Reporter: James Netherton
>Assignee: Dmitry Volodin
> Fix For: 2.20.0
>
>
> Class {{GrpcUtils}} does:
> {code}
> Class grpcServiceClass = Class.forName(serviceClassName);
> {code}
> Unfortunately, that causes the class loading to be done from the
> {{GrpcUtils}} {{ClassLoader}}, which may not be appropriate in modular
> environments (OSGi, JavaEE, etc)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CAMEL-11237) camel-grpc - Add a grpc consumer
[ https://issues.apache.org/jira/browse/CAMEL-11237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11237: --- Issue Type: Sub-task (was: New Feature) Parent: CAMEL-9008 > camel-grpc - Add a grpc consumer > > > Key: CAMEL-11237 > URL: https://issues.apache.org/jira/browse/CAMEL-11237 > Project: Camel > Issue Type: Sub-task > Components: camel-grpc >Reporter: Nicola Ferraro >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > > We should allow using grpc from consumer-side. See also (CAMEL-11236). > Added this for tracking as I think [~dmvolod] is already working on it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-9008) Contributing GRPC / Thrift support to Camel
[ https://issues.apache.org/jira/browse/CAMEL-9008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-9008: - Assignee: Dmitry Volodin > Contributing GRPC / Thrift support to Camel > --- > > Key: CAMEL-9008 > URL: https://issues.apache.org/jira/browse/CAMEL-9008 > Project: Camel > Issue Type: New Feature >Reporter: Andrew Harmel-Law >Assignee: Dmitry Volodin > Fix For: Future > > > Hi, > We're building Microservices with Camel, predominantly producing from REST > DSL components and have got to the point where having an easy way to swap in > GRPC [1] / Thrift [2] endpoints and clients would be of great help. > We wondered if this was already on the cards for a future release, and if we > might be able to work on it, and if not, if it would be something we could > work on and contribute (with guidance to smooth the design and > implementation)? > Kind regards, the Capgemini UK and Indian Camel teams > [1] http://www.grpc.io/ > [2] https://thrift.apache.org/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11345) Remove dependency on spring-core from gRPC component
[ https://issues.apache.org/jira/browse/CAMEL-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027745#comment-16027745 ] Dmitry Volodin commented on CAMEL-11345: invokeMethod(Method method, Object target, Object... args) findMethod(Class clazz, String name, Class... paramTypes) > Remove dependency on spring-core from gRPC component > > > Key: CAMEL-11345 > URL: https://issues.apache.org/jira/browse/CAMEL-11345 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: James Netherton >Priority: Trivial > > As far as I can tell, Spring is only used in the gRPC component to pull in > some utility classes: > org.springframework.util.ObjectUtils > org.springframework.util.ReflectionUtils > Can we not replace these with equivalent Camel util classes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11345) Remove dependency on spring-core from gRPC component
[ https://issues.apache.org/jira/browse/CAMEL-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027740#comment-16027740 ] Dmitry Volodin commented on CAMEL-11345: [~davsclaus], I can't find how to use ReflectionHelper to do findMethod or invokeMethod Or this means that I need to add required methods to ReflectionHelper from the ReflectionUtils? > Remove dependency on spring-core from gRPC component > > > Key: CAMEL-11345 > URL: https://issues.apache.org/jira/browse/CAMEL-11345 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: James Netherton >Priority: Trivial > > As far as I can tell, Spring is only used in the gRPC component to pull in > some utility classes: > org.springframework.util.ObjectUtils > org.springframework.util.ReflectionUtils > Can we not replace these with equivalent Camel util classes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-11345) Remove dependency on spring-core from gRPC component
[ https://issues.apache.org/jira/browse/CAMEL-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin resolved CAMEL-11345. Resolution: Fixed > Remove dependency on spring-core from gRPC component > > > Key: CAMEL-11345 > URL: https://issues.apache.org/jira/browse/CAMEL-11345 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: James Netherton >Assignee: Dmitry Volodin >Priority: Trivial > Fix For: 2.19.1, 2.20.0 > > > As far as I can tell, Spring is only used in the gRPC component to pull in > some utility classes: > org.springframework.util.ObjectUtils > org.springframework.util.ReflectionUtils > Can we not replace these with equivalent Camel util classes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-11237) camel-grpc - Add a grpc consumer
[ https://issues.apache.org/jira/browse/CAMEL-11237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin resolved CAMEL-11237. Resolution: Fixed > camel-grpc - Add a grpc consumer > > > Key: CAMEL-11237 > URL: https://issues.apache.org/jira/browse/CAMEL-11237 > Project: Camel > Issue Type: Sub-task > Components: camel-grpc >Reporter: Nicola Ferraro >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > > We should allow using grpc from consumer-side. See also (CAMEL-11236). > Added this for tracking as I think [~dmvolod] is already working on it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11334) camel-grpc - Unit test fails due port number issue
[
https://issues.apache.org/jira/browse/CAMEL-11334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026116#comment-16026116
]
Dmitry Volodin commented on CAMEL-11334:
Looks like this problem occurs inside GrpcConsumerConcurrentTest due to hight
number of CONCURRENT_THREAD_COUNT = 300.
It's better to reduce this number to lower value, for example 100.
> camel-grpc - Unit test fails due port number issue
> --
>
> Key: CAMEL-11334
> URL: https://issues.apache.org/jira/browse/CAMEL-11334
> Project: Camel
> Issue Type: Test
> Components: camel-grpc
>Affects Versions: 2.20.0
>Reporter: Claus Ibsen
>Assignee: Nicola Ferraro
>
> It seems to take on a low port number like 1101 and then failing
> {code}
> 2017-05-25 19:45:42,614 [ult-executor-72] INFO GrpcConsumerConcurrentTest
> - Exception
> io.grpc.StatusRuntimeException: UNAVAILABLE
> at io.grpc.Status.asRuntimeException(Status.java:540)
> ~[grpc-core-1.2.0.jar:1.2.0]
> at
> io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:392)
> [grpc-stub-1.2.0.jar:1.2.0]
> at
> io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:428)
> [grpc-core-1.2.0.jar:1.2.0]
> at io.grpc.internal.ClientCallImpl.access$100(ClientCallImpl.java:76)
> [grpc-core-1.2.0.jar:1.2.0]
> at
> io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:514)
> [grpc-core-1.2.0.jar:1.2.0]
> at
> io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$700(ClientCallImpl.java:431)
> [grpc-core-1.2.0.jar:1.2.0]
> at
> io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:546)
> [grpc-core-1.2.0.jar:1.2.0]
> at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:52)
> [grpc-core-1.2.0.jar:1.2.0]
> at
> io.grpc.internal.SerializingExecutor$TaskRunner.run(SerializingExecutor.java:152)
> [grpc-core-1.2.0.jar:1.2.0]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
> Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException:
> Connection refused: localhost/0:0:0:0:0:0:0:1:1101
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> ~[?:1.8.0_131]
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> ~[?:1.8.0_131]
> at
> io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
> ~[netty-transport-4.1.8.Final.jar:4.1.8.Final]
> at
> io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
> ~[netty-transport-4.1.8.Final.jar:4.1.8.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
> ~[netty-transport-4.1.8.Final.jar:4.1.8.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
> ~[netty-transport-4.1.8.Final.jar:4.1.8.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
> ~[netty-transport-4.1.8.Final.jar:4.1.8.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
> ~[netty-transport-4.1.8.Final.jar:4.1.8.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
> ~[netty-common-4.1.8.Final.jar:4.1.8.Final]
> at
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
> ~[netty-common-4.1.8.Final.jar:4.1.8.Final]
> ... 1 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CAMEL-11288) camel-grpc producer incorrectly called async services
[ https://issues.apache.org/jira/browse/CAMEL-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11288: --- Fix Version/s: 2.20.0 2.19.1 > camel-grpc producer incorrectly called async services > - > > Key: CAMEL-11288 > URL: https://issues.apache.org/jira/browse/CAMEL-11288 > Project: Camel > Issue Type: Bug > Components: camel-grpc >Affects Versions: 2.19.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Critical > Fix For: 2.19.1, 2.20.0 > > > Error occurs when calling procedures with async (stream incoming and outgoing > parameters). This is not handled as expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-11288) camel-grpc producer incorrectly called async services
Dmitry Volodin created CAMEL-11288: -- Summary: camel-grpc producer incorrectly called async services Key: CAMEL-11288 URL: https://issues.apache.org/jira/browse/CAMEL-11288 Project: Camel Issue Type: Bug Components: camel-grpc Affects Versions: 2.19.0 Reporter: Dmitry Volodin Priority: Critical Error occurs when calling procedures with async (stream incoming and outgoing parameters). This is not handled as expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-11345) Remove dependency on spring-core from gRPC component
[ https://issues.apache.org/jira/browse/CAMEL-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-11345: -- Assignee: Dmitry Volodin > Remove dependency on spring-core from gRPC component > > > Key: CAMEL-11345 > URL: https://issues.apache.org/jira/browse/CAMEL-11345 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: James Netherton >Assignee: Dmitry Volodin >Priority: Trivial > > As far as I can tell, Spring is only used in the gRPC component to pull in > some utility classes: > org.springframework.util.ObjectUtils > org.springframework.util.ReflectionUtils > Can we not replace these with equivalent Camel util classes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-11345) Remove dependency on spring-core from gRPC component
[ https://issues.apache.org/jira/browse/CAMEL-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11345 started by Dmitry Volodin. -- > Remove dependency on spring-core from gRPC component > > > Key: CAMEL-11345 > URL: https://issues.apache.org/jira/browse/CAMEL-11345 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: James Netherton >Assignee: Dmitry Volodin >Priority: Trivial > > As far as I can tell, Spring is only used in the gRPC component to pull in > some utility classes: > org.springframework.util.ObjectUtils > org.springframework.util.ReflectionUtils > Can we not replace these with equivalent Camel util classes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-11345) Remove dependency on spring-core from gRPC component
[ https://issues.apache.org/jira/browse/CAMEL-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11345: --- Fix Version/s: 2.20.0 2.19.1 > Remove dependency on spring-core from gRPC component > > > Key: CAMEL-11345 > URL: https://issues.apache.org/jira/browse/CAMEL-11345 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: James Netherton >Assignee: Dmitry Volodin >Priority: Trivial > Fix For: 2.19.1, 2.20.0 > > > As far as I can tell, Spring is only used in the gRPC component to pull in > some utility classes: > org.springframework.util.ObjectUtils > org.springframework.util.ReflectionUtils > Can we not replace these with equivalent Camel util classes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11345) Remove dependency on spring-core from gRPC component
[ https://issues.apache.org/jira/browse/CAMEL-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16028225#comment-16028225 ] Dmitry Volodin commented on CAMEL-11345: 2.19.1 requires separate PR > Remove dependency on spring-core from gRPC component > > > Key: CAMEL-11345 > URL: https://issues.apache.org/jira/browse/CAMEL-11345 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: James Netherton >Assignee: Dmitry Volodin >Priority: Trivial > Fix For: 2.19.1, 2.20.0 > > > As far as I can tell, Spring is only used in the gRPC component to pull in > some utility classes: > org.springframework.util.ObjectUtils > org.springframework.util.ReflectionUtils > Can we not replace these with equivalent Camel util classes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11369) camel-spring-boot-starter generator paste incorrect default value
[ https://issues.apache.org/jira/browse/CAMEL-11369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030835#comment-16030835 ] Dmitry Volodin commented on CAMEL-11369: No, sorry, I have no time. > camel-spring-boot-starter generator paste incorrect default value > - > > Key: CAMEL-11369 > URL: https://issues.apache.org/jira/browse/CAMEL-11369 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot-starters, tooling >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin > Fix For: 2.20.0 > > > I've created a new data component and submit it via PR > https://github.com/apache/camel/pull/1729 > The spring-bootstarter *DataFormatConfiguration class contains incorrectly > defined default value: > private String contentTypeFormat = String.binary; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-11369) camel-spring-boot-starter generator paste incorrect default value
Dmitry Volodin created CAMEL-11369: -- Summary: camel-spring-boot-starter generator paste incorrect default value Key: CAMEL-11369 URL: https://issues.apache.org/jira/browse/CAMEL-11369 Project: Camel Issue Type: Bug Components: camel-spring-boot-starters Affects Versions: 2.20.0 Reporter: Dmitry Volodin I've created a new data component and submit it via PR https://github.com/apache/camel/pull/1729 The spring-bootstarter *DataFormatConfiguration class contains incorrectly defined default value: private String contentTypeFormat = String.binary; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (CAMEL-11369) camel-spring-boot-starter generator paste incorrect default value
[ https://issues.apache.org/jira/browse/CAMEL-11369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11369: --- Comment: was deleted (was: No, sorry, I have no time.) > camel-spring-boot-starter generator paste incorrect default value > - > > Key: CAMEL-11369 > URL: https://issues.apache.org/jira/browse/CAMEL-11369 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot-starters, tooling >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > > I've created a new data component and submit it via PR > https://github.com/apache/camel/pull/1729 > The spring-bootstarter *DataFormatConfiguration class contains incorrectly > defined default value: > private String contentTypeFormat = String.binary; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-11332) Create a new camel-thrift data format
[ https://issues.apache.org/jira/browse/CAMEL-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin resolved CAMEL-11332. Resolution: Fixed > Create a new camel-thrift data format > - > > Key: CAMEL-11332 > URL: https://issues.apache.org/jira/browse/CAMEL-11332 > Project: Camel > Issue Type: Sub-task >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Labels: thrift > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-11369) camel-spring-boot-starter generator paste incorrect default value
[ https://issues.apache.org/jira/browse/CAMEL-11369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin resolved CAMEL-11369. Resolution: Fixed > camel-spring-boot-starter generator paste incorrect default value > - > > Key: CAMEL-11369 > URL: https://issues.apache.org/jira/browse/CAMEL-11369 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot-starters, tooling >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > > I've created a new data component and submit it via PR > https://github.com/apache/camel/pull/1729 > The spring-bootstarter *DataFormatConfiguration class contains incorrectly > defined default value: > private String contentTypeFormat = String.binary; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-11333) Create a new camel-thrift RPC component
[ https://issues.apache.org/jira/browse/CAMEL-11333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11333 started by Dmitry Volodin. -- > Create a new camel-thrift RPC component > --- > > Key: CAMEL-11333 > URL: https://issues.apache.org/jira/browse/CAMEL-11333 > Project: Camel > Issue Type: Sub-task >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Labels: rpc, thrift > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-11369) camel-spring-boot-starter generator paste incorrect default value
[ https://issues.apache.org/jira/browse/CAMEL-11369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11369 started by Dmitry Volodin. -- > camel-spring-boot-starter generator paste incorrect default value > - > > Key: CAMEL-11369 > URL: https://issues.apache.org/jira/browse/CAMEL-11369 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot-starters, tooling >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > > I've created a new data component and submit it via PR > https://github.com/apache/camel/pull/1729 > The spring-bootstarter *DataFormatConfiguration class contains incorrectly > defined default value: > private String contentTypeFormat = String.binary; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-11369) camel-spring-boot-starter generator paste incorrect default value
[ https://issues.apache.org/jira/browse/CAMEL-11369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-11369: -- Assignee: Dmitry Volodin > camel-spring-boot-starter generator paste incorrect default value > - > > Key: CAMEL-11369 > URL: https://issues.apache.org/jira/browse/CAMEL-11369 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot-starters, tooling >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > > I've created a new data component and submit it via PR > https://github.com/apache/camel/pull/1729 > The spring-bootstarter *DataFormatConfiguration class contains incorrectly > defined default value: > private String contentTypeFormat = String.binary; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-11333) Create a new camel-thrift RPC component
[ https://issues.apache.org/jira/browse/CAMEL-11333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11333: --- Flags: (was: Patch) > Create a new camel-thrift RPC component > --- > > Key: CAMEL-11333 > URL: https://issues.apache.org/jira/browse/CAMEL-11333 > Project: Camel > Issue Type: Sub-task >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Labels: rpc, thrift > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11333) Create a new camel-thrift RPC component
[ https://issues.apache.org/jira/browse/CAMEL-11333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11333: --- Flags: Patch > Create a new camel-thrift RPC component > --- > > Key: CAMEL-11333 > URL: https://issues.apache.org/jira/browse/CAMEL-11333 > Project: Camel > Issue Type: Sub-task >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Labels: rpc, thrift > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11237) camel-grpc - Add a grpc consumer
[ https://issues.apache.org/jira/browse/CAMEL-11237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000634#comment-16000634 ] Dmitry Volodin commented on CAMEL-11237: [~nibbio84], yes, working on it and will commit soon, but can't grab issue as "Assignee". > camel-grpc - Add a grpc consumer > > > Key: CAMEL-11237 > URL: https://issues.apache.org/jira/browse/CAMEL-11237 > Project: Camel > Issue Type: New Feature > Components: camel-grpc >Reporter: Nicola Ferraro > Fix For: 2.20.0 > > > We should allow using grpc from consumer-side. See also (CAMEL-11236). > Added this for tracking as I think [~dmvolod] is already working on it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-11237) camel-grpc - Add a grpc consumer
[ https://issues.apache.org/jira/browse/CAMEL-11237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11237 started by Dmitry Volodin. -- > camel-grpc - Add a grpc consumer > > > Key: CAMEL-11237 > URL: https://issues.apache.org/jira/browse/CAMEL-11237 > Project: Camel > Issue Type: New Feature > Components: camel-grpc >Reporter: Nicola Ferraro >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > > We should allow using grpc from consumer-side. See also (CAMEL-11236). > Added this for tracking as I think [~dmvolod] is already working on it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-11237) camel-grpc - Add a grpc consumer
[ https://issues.apache.org/jira/browse/CAMEL-11237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-11237: -- Assignee: Dmitry Volodin > camel-grpc - Add a grpc consumer > > > Key: CAMEL-11237 > URL: https://issues.apache.org/jira/browse/CAMEL-11237 > Project: Camel > Issue Type: New Feature > Components: camel-grpc >Reporter: Nicola Ferraro >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > > We should allow using grpc from consumer-side. See also (CAMEL-11236). > Added this for tracking as I think [~dmvolod] is already working on it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11237) camel-grpc - Add a grpc consumer
[ https://issues.apache.org/jira/browse/CAMEL-11237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000639#comment-16000639 ] Dmitry Volodin commented on CAMEL-11237: Thanks a lot [~davsclaus] > camel-grpc - Add a grpc consumer > > > Key: CAMEL-11237 > URL: https://issues.apache.org/jira/browse/CAMEL-11237 > Project: Camel > Issue Type: New Feature > Components: camel-grpc >Reporter: Nicola Ferraro >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > > We should allow using grpc from consumer-side. See also (CAMEL-11236). > Added this for tracking as I think [~dmvolod] is already working on it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-11333) Create a new camel-thrift RPC component
[ https://issues.apache.org/jira/browse/CAMEL-11333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-11333: -- Assignee: Dmitry Volodin > Create a new camel-thrift RPC component > --- > > Key: CAMEL-11333 > URL: https://issues.apache.org/jira/browse/CAMEL-11333 > Project: Camel > Issue Type: Sub-task >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Labels: rpc, thrift > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-11332) Create a new camel-thrift data format
[ https://issues.apache.org/jira/browse/CAMEL-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11332: --- Summary: Create a new camel-thrift data format (was: Create a new camel-thrift data format component) > Create a new camel-thrift data format > - > > Key: CAMEL-11332 > URL: https://issues.apache.org/jira/browse/CAMEL-11332 > Project: Camel > Issue Type: Sub-task >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Labels: thrift > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-11333) Create a new camel-thrift RPC component
Dmitry Volodin created CAMEL-11333: -- Summary: Create a new camel-thrift RPC component Key: CAMEL-11333 URL: https://issues.apache.org/jira/browse/CAMEL-11333 Project: Camel Issue Type: Sub-task Reporter: Dmitry Volodin Fix For: 2.20.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-11332) Create a new camel-thrift data format
[ https://issues.apache.org/jira/browse/CAMEL-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11332 started by Dmitry Volodin. -- > Create a new camel-thrift data format > - > > Key: CAMEL-11332 > URL: https://issues.apache.org/jira/browse/CAMEL-11332 > Project: Camel > Issue Type: Sub-task >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin > Labels: thrift > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-11456) Make the camel-grpc component more cloud service friendly
[ https://issues.apache.org/jira/browse/CAMEL-11456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin resolved CAMEL-11456. Resolution: Fixed > Make the camel-grpc component more cloud service friendly > - > > Key: CAMEL-11456 > URL: https://issues.apache.org/jira/browse/CAMEL-11456 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 2.20.0 > > > Change an URI to be able expose and call component in cloud service > infrastructure easy > Now, the component URI is looks like grpc:host:port/service instead of > passing host and port via parameters -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11456) Make the camel-grpc component more cloud service friendly
[ https://issues.apache.org/jira/browse/CAMEL-11456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-11456: --- Fix Version/s: 2.20.0 > Make the camel-grpc component more cloud service friendly > - > > Key: CAMEL-11456 > URL: https://issues.apache.org/jira/browse/CAMEL-11456 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 2.20.0 > > > Change an URI to be able expose and call component in cloud service > infrastructure easy > Now, the component URI is looks like grpc:host:port/service instead of > passing host and port via parameters -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-9008) Contributing GRPC / Thrift support to Camel
[ https://issues.apache.org/jira/browse/CAMEL-9008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176728#comment-16176728 ] Dmitry Volodin commented on CAMEL-9008: --- I will submit PR with the new functions till the end of the next week, with some cut off of the beginning functionality, due to the missing some functions in Apache Thrift. > Contributing GRPC / Thrift support to Camel > --- > > Key: CAMEL-9008 > URL: https://issues.apache.org/jira/browse/CAMEL-9008 > Project: Camel > Issue Type: New Feature >Reporter: Andrew Harmel-Law >Assignee: Dmitry Volodin > Fix For: 2.20.0 > > > Hi, > We're building Microservices with Camel, predominantly producing from REST > DSL components and have got to the point where having an easy way to swap in > GRPC [1] / Thrift [2] endpoints and clients would be of great help. > We wondered if this was already on the cards for a future release, and if we > might be able to work on it, and if not, if it would be something we could > work on and contribute (with guidance to smooth the design and > implementation)? > Kind regards, the Capgemini UK and Indian Camel teams > [1] http://www.grpc.io/ > [2] https://thrift.apache.org/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-9008) Contributing GRPC / Thrift support to Camel
[ https://issues.apache.org/jira/browse/CAMEL-9008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-9008: -- Labels: microservice rpc (was: ) > Contributing GRPC / Thrift support to Camel > --- > > Key: CAMEL-9008 > URL: https://issues.apache.org/jira/browse/CAMEL-9008 > Project: Camel > Issue Type: New Feature >Reporter: Andrew Harmel-Law >Assignee: Dmitry Volodin > Labels: microservice, rpc > Fix For: 2.20.0 > > > Hi, > We're building Microservices with Camel, predominantly producing from REST > DSL components and have got to the point where having an easy way to swap in > GRPC [1] / Thrift [2] endpoints and clients would be of great help. > We wondered if this was already on the cards for a future release, and if we > might be able to work on it, and if not, if it would be something we could > work on and contribute (with guidance to smooth the design and > implementation)? > Kind regards, the Capgemini UK and Indian Camel teams > [1] http://www.grpc.io/ > [2] https://thrift.apache.org/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
