[jira] [Updated] (CAMEL-15912) Able to load custom font from file in camel-pdf
[ https://issues.apache.org/jira/browse/CAMEL-15912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-15912: --- Description: There are 14 standard fonts provided OOB and not able to load custom fonts from file in camel-pdf component [Custom fonts with Apache PDFBox component|https://carbonrider.github.io/pdfbox_tutorial/pdf_embed_font.html] was:There are 14 standard fonts provided OOB and not able to load custom fonts from file in camel-pdf component > Able to load custom font from file in camel-pdf > --- > > Key: CAMEL-15912 > URL: https://issues.apache.org/jira/browse/CAMEL-15912 > Project: Camel > Issue Type: New Feature > Components: camel-pdf >Reporter: Dmitry Volodin >Priority: Minor > Fix For: Future > > > There are 14 standard fonts provided OOB and not able to load custom fonts > from file in camel-pdf component > [Custom fonts with Apache PDFBox > component|https://carbonrider.github.io/pdfbox_tutorial/pdf_embed_font.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15912) Able to load custom font from file in camel-pdf
[ https://issues.apache.org/jira/browse/CAMEL-15912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-15912: --- Summary: Able to load custom font from file in camel-pdf (was: Able to load custom font from file) > Able to load custom font from file in camel-pdf > --- > > Key: CAMEL-15912 > URL: https://issues.apache.org/jira/browse/CAMEL-15912 > Project: Camel > Issue Type: New Feature > Components: camel-pdf >Reporter: Dmitry Volodin >Priority: Minor > Fix For: Future > > > There are 14 standard fonts provided OOB and not able to load custom fonts > from file in camel-pdf component -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15912) Able to load custom font from file
[ https://issues.apache.org/jira/browse/CAMEL-15912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-15912: --- Component/s: camel-pdf > Able to load custom font from file > -- > > Key: CAMEL-15912 > URL: https://issues.apache.org/jira/browse/CAMEL-15912 > Project: Camel > Issue Type: New Feature > Components: camel-pdf >Reporter: Dmitry Volodin >Priority: Minor > Fix For: Future > > > There are 14 standard fonts provided OOB and not able to load custom fonts > from file in camel-pdf component -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15912) Able to load custom font from file
Dmitry Volodin created CAMEL-15912: -- Summary: Able to load custom font from file Key: CAMEL-15912 URL: https://issues.apache.org/jira/browse/CAMEL-15912 Project: Camel Issue Type: New Feature Reporter: Dmitry Volodin Fix For: Future There are 14 standard fonts provided OOB and not able to load custom fonts from file in camel-pdf component -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15883) Able to run multiple gRPC services on single endpoint (host:port)
Dmitry Volodin created CAMEL-15883: -- Summary: Able to run multiple gRPC services on single endpoint (host:port) Key: CAMEL-15883 URL: https://issues.apache.org/jira/browse/CAMEL-15883 Project: Camel Issue Type: Improvement Components: camel-grpc Reporter: Dmitry Volodin Fix For: Future There was a question on SO about this function https://stackoverflow.com/questions/64972954/using-apache-camel-for-routing-grpc-traffic-using-the-same-port-per-route#new-answer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15766) camel-spring-boot - No converter found capable of converting from type [java.lang.String] to type [org.apache.camel.component.http.HttpClientConfigurer]
[
https://issues.apache.org/jira/browse/CAMEL-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17231366#comment-17231366
]
Dmitry Volodin commented on CAMEL-15766:
[~davsclaus] not sure that's related to conversion. It's related to the
modified Customizers logic as it's calling later than Sping requires custom
httpClientConfig for binding.
> camel-spring-boot - No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
>
>
> Key: CAMEL-15766
> URL: https://issues.apache.org/jira/browse/CAMEL-15766
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-spring-boot
>Affects Versions: 3.6.0
>Reporter: Marco Santarelli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.7.0
>
>
> When trying to use a custom http-configurer, I believe I am experiencing a
> regression when upgrading to Camel 3.6.0
> I am using spring-boot 2.3.4.RELEASE, and I am declaring my custom configurer
> bean using:
> {code:java}
> camel.component.http.http-client-configurer=#httpClientConfig
> {code}
> When updating to Camel 3.6.0, that configuration results in:
> {code:java}
> ***
> APPLICATION FAILED TO START
> ***
> Description:
> Failed to bind properties under 'camel.component.http.http-client-configurer'
> to org.apache.camel.component.http.HttpClientConfigurer:
> Property: camel.component.http.http-client-configurer
> Value: httpClientConfig
> Origin: class path resource [application.properties]:1:45
> Reason: No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
> Action:
> Update your application's configuration{code}
>
> See [https://github.com/santam85/camel-3.6.0-http-configurer-bean] for a
> reproduction example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-15766) camel-spring-boot - No converter found capable of converting from type [java.lang.String] to type [org.apache.camel.component.http.HttpClientConfigurer]
[
https://issues.apache.org/jira/browse/CAMEL-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17231366#comment-17231366
]
Dmitry Volodin edited comment on CAMEL-15766 at 11/13/20, 10:45 AM:
[~davsclaus] not sure that's related to conversion. It's related to the
modified Customizers logic as it's calling later than Spring requires custom
httpClientConfig for binding.
was (Author: dmvolod):
[~davsclaus] not sure that's related to conversion. It's related to the
modified Customizers logic as it's calling later than Sping requires custom
httpClientConfig for binding.
> camel-spring-boot - No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
>
>
> Key: CAMEL-15766
> URL: https://issues.apache.org/jira/browse/CAMEL-15766
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-spring-boot
>Affects Versions: 3.6.0
>Reporter: Marco Santarelli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.7.0
>
>
> When trying to use a custom http-configurer, I believe I am experiencing a
> regression when upgrading to Camel 3.6.0
> I am using spring-boot 2.3.4.RELEASE, and I am declaring my custom configurer
> bean using:
> {code:java}
> camel.component.http.http-client-configurer=#httpClientConfig
> {code}
> When updating to Camel 3.6.0, that configuration results in:
> {code:java}
> ***
> APPLICATION FAILED TO START
> ***
> Description:
> Failed to bind properties under 'camel.component.http.http-client-configurer'
> to org.apache.camel.component.http.HttpClientConfigurer:
> Property: camel.component.http.http-client-configurer
> Value: httpClientConfig
> Origin: class path resource [application.properties]:1:45
> Reason: No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
> Action:
> Update your application's configuration{code}
>
> See [https://github.com/santam85/camel-3.6.0-http-configurer-bean] for a
> reproduction example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-15766) camel-spring-boot - No converter found capable of converting from type [java.lang.String] to type [org.apache.camel.component.http.HttpClientConfigurer]
[
https://issues.apache.org/jira/browse/CAMEL-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-15766:
--
Assignee: (was: Dmitry Volodin)
> camel-spring-boot - No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
>
>
> Key: CAMEL-15766
> URL: https://issues.apache.org/jira/browse/CAMEL-15766
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-spring-boot
>Affects Versions: 3.6.0
>Reporter: Marco Santarelli
>Priority: Major
> Fix For: 3.7.0
>
>
> When trying to use a custom http-configurer, I believe I am experiencing a
> regression when upgrading to Camel 3.6.0
> I am using spring-boot 2.3.4.RELEASE, and I am declaring my custom configurer
> bean using:
> {code:java}
> camel.component.http.http-client-configurer=#httpClientConfig
> {code}
> When updating to Camel 3.6.0, that configuration results in:
> {code:java}
> ***
> APPLICATION FAILED TO START
> ***
> Description:
> Failed to bind properties under 'camel.component.http.http-client-configurer'
> to org.apache.camel.component.http.HttpClientConfigurer:
> Property: camel.component.http.http-client-configurer
> Value: httpClientConfig
> Origin: class path resource [application.properties]:1:45
> Reason: No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
> Action:
> Update your application's configuration{code}
>
> See [https://github.com/santam85/camel-3.6.0-http-configurer-bean] for a
> reproduction example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15766) camel-spring-boot - No converter found capable of converting from type [java.lang.String] to type [org.apache.camel.component.http.HttpClientConfigurer]
[
https://issues.apache.org/jira/browse/CAMEL-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223539#comment-17223539
]
Dmitry Volodin commented on CAMEL-15766:
The debug of the problem
{code:java}
2020-10-30 10:17:15.122 WARN 528990 --- [ main]
ConfigServletWebServerApplicationContext : Exception encountered during context
initialization - cancelling refresh attempt:
org.springframework.beans.factory.UnsatisfiedDependencyException: Error
creating bean with name
'org.apache.camel.component.http.springboot.HttpComponentAutoConfiguration':
Unsatisfied dependency expressed through field 'configuration'; nested
exception is
org.springframework.boot.context.properties.ConfigurationPropertiesBindException:
Error creating bean with name
'camel.component.http-org.apache.camel.component.http.springboot.HttpComponentConfiguration':
Could not bind properties to 'HttpComponentConfiguration' :
prefix=camel.component.http, ignoreInvalidFields=false,
ignoreUnknownFields=true; nested exception is
org.springframework.boot.context.properties.bind.BindException: Failed to bind
properties under 'camel.component.http.http-client-configurer' to
org.apache.camel.component.http.HttpClientConfigurer
{code}
> camel-spring-boot - No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
>
>
> Key: CAMEL-15766
> URL: https://issues.apache.org/jira/browse/CAMEL-15766
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-spring-boot
>Affects Versions: 3.6.0
>Reporter: Marco Santarelli
>Assignee: Dmitry Volodin
>Priority: Major
> Fix For: 3.7.0
>
>
> When trying to use a custom http-configurer, I believe I am experiencing a
> regression when upgrading to Camel 3.6.0
> I am using spring-boot 2.3.4.RELEASE, and I am declaring my custom configurer
> bean using:
> {code:java}
> camel.component.http.http-client-configurer=#httpClientConfig
> {code}
> When updating to Camel 3.6.0, that configuration results in:
> {code:java}
> ***
> APPLICATION FAILED TO START
> ***
> Description:
> Failed to bind properties under 'camel.component.http.http-client-configurer'
> to org.apache.camel.component.http.HttpClientConfigurer:
> Property: camel.component.http.http-client-configurer
> Value: httpClientConfig
> Origin: class path resource [application.properties]:1:45
> Reason: No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
> Action:
> Update your application's configuration{code}
>
> See [https://github.com/santam85/camel-3.6.0-http-configurer-bean] for a
> reproduction example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-15766) camel-spring-boot - No converter found capable of converting from type [java.lang.String] to type [org.apache.camel.component.http.HttpClientConfigurer]
[
https://issues.apache.org/jira/browse/CAMEL-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-15766:
--
Assignee: Dmitry Volodin
> camel-spring-boot - No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
>
>
> Key: CAMEL-15766
> URL: https://issues.apache.org/jira/browse/CAMEL-15766
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-spring-boot
>Affects Versions: 3.6.0
>Reporter: Marco Santarelli
>Assignee: Dmitry Volodin
>Priority: Major
> Fix For: 3.7.0
>
>
> When trying to use a custom http-configurer, I believe I am experiencing a
> regression when upgrading to Camel 3.6.0
> I am using spring-boot 2.3.4.RELEASE, and I am declaring my custom configurer
> bean using:
> {code:java}
> camel.component.http.http-client-configurer=#httpClientConfig
> {code}
> When updating to Camel 3.6.0, that configuration results in:
> {code:java}
> ***
> APPLICATION FAILED TO START
> ***
> Description:
> Failed to bind properties under 'camel.component.http.http-client-configurer'
> to org.apache.camel.component.http.HttpClientConfigurer:
> Property: camel.component.http.http-client-configurer
> Value: httpClientConfig
> Origin: class path resource [application.properties]:1:45
> Reason: No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
> Action:
> Update your application's configuration{code}
>
> See [https://github.com/santam85/camel-3.6.0-http-configurer-bean] for a
> reproduction example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-15774) [Website] suppress warnings for unimplemented camel-quarkus components; upgrade to Antora 3.0.0-alpha.1
[ https://issues.apache.org/jira/browse/CAMEL-15774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-15774: --- Component/s: website > [Website] suppress warnings for unimplemented camel-quarkus components; > upgrade to Antora 3.0.0-alpha.1 > --- > > Key: CAMEL-15774 > URL: https://issues.apache.org/jira/browse/CAMEL-15774 > Project: Camel > Issue Type: Bug > Components: website >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > With Antora 3.0.0-alpha.1, include:: instructions can suppress "asciidoctor: > ERROR: atlasmap-component.adoc: line 11: include target not found: ..." > errors by including > [opts=optional]. This modifies tooling to include this in the generated > includes for cq bits, updates the generated files correspondingly, and > upgrades the Antora version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15773) (website) Workaround xref-validator bogus errors
[ https://issues.apache.org/jira/browse/CAMEL-15773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-15773: --- Component/s: (was: came-core) website > (website) Workaround xref-validator bogus errors > > > Key: CAMEL-15773 > URL: https://issues.apache.org/jira/browse/CAMEL-15773 > Project: Camel > Issue Type: Task > Components: website >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > The recent change to the Antora xref-validator to validate nav files is > useful but bogus as it reclassifies nav files as pages, breaking the index > extension used to generate tables. > We can work around this by explicitly excluding nav files from the indexTable > macro. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15749) Unable to configure hash symbol as commentMarker for csv data format
[
https://issues.apache.org/jira/browse/CAMEL-15749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin resolved CAMEL-15749.
Fix Version/s: 3.7.0
Resolution: Fixed
> Unable to configure hash symbol as commentMarker for csv data format
>
>
> Key: CAMEL-15749
> URL: https://issues.apache.org/jira/browse/CAMEL-15749
> Project: Camel
> Issue Type: Bug
> Components: camel-csv
>Affects Versions: 3.6.0
>Reporter: Viacheslav Zhivaev
>Assignee: Dmitry Volodin
>Priority: Minor
> Fix For: 3.7.0
>
> Attachments: App.java, pom.xml, test.xml
>
>
> Hi all,
> I tried to run my camel configuration (after update to camel 3.6.0,
> previously running 3.0.6 without an issue) and got following error:
>
> {noformat}
> org.apache.camel.FailedToCreateRouteException: Failed to create route route1
> at: >>> Unmarshal[org.apache.camel.model.dataformat.CsvDataFormat@192613f]
> <<< in route: Route(route1)[From[direct://test] -> [Unmarshal[org.apache.c...
> because of Error binding property (commentMarker=#) with name: commentMarker
> on bean: org.apache.camel.dataformat.csv.CsvDataFormat@42dc5a with value: #
> at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:384)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:111)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:431)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:393)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2606)
> ~[camel-base-3.6.0.jar:3.6.0]
> at
> org.apache.camel.support.service.BaseService.init(BaseService.java:83)
> ~[camel-api-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2378)
> ~[camel-base-3.6.0.jar:3.6.0]
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> ~[camel-api-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2395)
> ~[camel-base-3.6.0.jar:3.6.0]
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:130)
> ~[camel-spring-3.6.0.jar:3.6.0]
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:167)
> ~[camel-spring-3.6.0.jar:3.6.0]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:404)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:361)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:898)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:554)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:758)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:750)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:315)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1237)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1226)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
>
[jira] [Commented] (CAMEL-15749) Unable to configure hash symbol as commentMarker for csv data format
[
https://issues.apache.org/jira/browse/CAMEL-15749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17220845#comment-17220845
]
Dmitry Volodin commented on CAMEL-15749:
The reason of the problem why it happens, hash symbol (#) is a property binding
sign a tries to parse value.
For Character it doesn't make sense as it's only one symbol and looks like need
to be fixed in core.
> Unable to configure hash symbol as commentMarker for csv data format
>
>
> Key: CAMEL-15749
> URL: https://issues.apache.org/jira/browse/CAMEL-15749
> Project: Camel
> Issue Type: Bug
> Components: camel-csv
>Affects Versions: 3.6.0
>Reporter: Viacheslav Zhivaev
>Assignee: Dmitry Volodin
>Priority: Minor
> Attachments: App.java, pom.xml, test.xml
>
>
> Hi all,
> I tried to run my camel configuration (after update to camel 3.6.0,
> previously running 3.0.6 without an issue) and got following error:
>
> {noformat}
> org.apache.camel.FailedToCreateRouteException: Failed to create route route1
> at: >>> Unmarshal[org.apache.camel.model.dataformat.CsvDataFormat@192613f]
> <<< in route: Route(route1)[From[direct://test] -> [Unmarshal[org.apache.c...
> because of Error binding property (commentMarker=#) with name: commentMarker
> on bean: org.apache.camel.dataformat.csv.CsvDataFormat@42dc5a with value: #
> at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:384)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:111)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:431)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:393)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2606)
> ~[camel-base-3.6.0.jar:3.6.0]
> at
> org.apache.camel.support.service.BaseService.init(BaseService.java:83)
> ~[camel-api-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2378)
> ~[camel-base-3.6.0.jar:3.6.0]
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> ~[camel-api-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2395)
> ~[camel-base-3.6.0.jar:3.6.0]
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:130)
> ~[camel-spring-3.6.0.jar:3.6.0]
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:167)
> ~[camel-spring-3.6.0.jar:3.6.0]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:404)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:361)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:898)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:554)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:758)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:750)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:315)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1237)
>
[jira] [Assigned] (CAMEL-15749) Unable to configure hash symbol as commentMarker for csv data format
[
https://issues.apache.org/jira/browse/CAMEL-15749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-15749:
--
Assignee: Dmitry Volodin
> Unable to configure hash symbol as commentMarker for csv data format
>
>
> Key: CAMEL-15749
> URL: https://issues.apache.org/jira/browse/CAMEL-15749
> Project: Camel
> Issue Type: Bug
> Components: camel-csv
>Affects Versions: 3.6.0
>Reporter: Viacheslav Zhivaev
>Assignee: Dmitry Volodin
>Priority: Minor
> Attachments: App.java, pom.xml, test.xml
>
>
> Hi all,
> I tried to run my camel configuration (after update to camel 3.6.0,
> previously running 3.0.6 without an issue) and got following error:
>
> {noformat}
> org.apache.camel.FailedToCreateRouteException: Failed to create route route1
> at: >>> Unmarshal[org.apache.camel.model.dataformat.CsvDataFormat@192613f]
> <<< in route: Route(route1)[From[direct://test] -> [Unmarshal[org.apache.c...
> because of Error binding property (commentMarker=#) with name: commentMarker
> on bean: org.apache.camel.dataformat.csv.CsvDataFormat@42dc5a with value: #
> at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:384)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:111)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:431)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:393)
> ~[camel-core-engine-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2606)
> ~[camel-base-3.6.0.jar:3.6.0]
> at
> org.apache.camel.support.service.BaseService.init(BaseService.java:83)
> ~[camel-api-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2378)
> ~[camel-base-3.6.0.jar:3.6.0]
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> ~[camel-api-3.6.0.jar:3.6.0]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2395)
> ~[camel-base-3.6.0.jar:3.6.0]
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:130)
> ~[camel-spring-3.6.0.jar:3.6.0]
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:167)
> ~[camel-spring-3.6.0.jar:3.6.0]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:404)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:361)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:898)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:554)
> ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:758)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:750)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:315)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1237)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1226)
> [spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
> at test.App.main(App.java:17) [classes/:na]
[jira] [Resolved] (CAMEL-15754) camel-grpc Improve the propagation consumer strategy
[ https://issues.apache.org/jira/browse/CAMEL-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin resolved CAMEL-15754. Resolution: Fixed > camel-grpc Improve the propagation consumer strategy > - > > Key: CAMEL-15754 > URL: https://issues.apache.org/jira/browse/CAMEL-15754 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: Rajasekhar Bhupasamudram >Assignee: Dmitry Volodin >Priority: Critical > Fix For: 3.7.0 > > > In the GrpcRequestPropagationStreamObserver, the responseStream.onCompleted() > is called every time an onNext method is invoked by the client via a grpc > call. This does not leverage the Http 2.0 abilities to send the responses > back to the client asynchronously. > Once the camel route is traversed, the server is sending some response to the > client using the onNext method calls. But, sometimes, it may be a good idea > to not to send any data immediately and call the onCompleted methods. > I propose to allow the camel route to control this behavior with some > properties. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15754) camel-grpc Improve the propagation consumer strategy
[ https://issues.apache.org/jira/browse/CAMEL-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17220533#comment-17220533 ] Dmitry Volodin commented on CAMEL-15754: Thanks, [~rajasekharb] for PR. > camel-grpc Improve the propagation consumer strategy > - > > Key: CAMEL-15754 > URL: https://issues.apache.org/jira/browse/CAMEL-15754 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: Rajasekhar Bhupasamudram >Assignee: Dmitry Volodin >Priority: Critical > Fix For: 3.7.0 > > > In the GrpcRequestPropagationStreamObserver, the responseStream.onCompleted() > is called every time an onNext method is invoked by the client via a grpc > call. This does not leverage the Http 2.0 abilities to send the responses > back to the client asynchronously. > Once the camel route is traversed, the server is sending some response to the > client using the onNext method calls. But, sometimes, it may be a good idea > to not to send any data immediately and call the onCompleted methods. > I propose to allow the camel route to control this behavior with some > properties. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15754) camel-grpc Improve the propagation consumer strategy
[ https://issues.apache.org/jira/browse/CAMEL-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-15754: -- Assignee: Dmitry Volodin > camel-grpc Improve the propagation consumer strategy > - > > Key: CAMEL-15754 > URL: https://issues.apache.org/jira/browse/CAMEL-15754 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Reporter: Rajasekhar Bhupasamudram >Assignee: Dmitry Volodin >Priority: Critical > Fix For: 3.7.0 > > > In the GrpcRequestPropagationStreamObserver, the responseStream.onCompleted() > is called every time an onNext method is invoked by the client via a grpc > call. This does not leverage the Http 2.0 abilities to send the responses > back to the client asynchronously. > Once the camel route is traversed, the server is sending some response to the > client using the onNext method calls. But, sometimes, it may be a good idea > to not to send any data immediately and call the onCompleted methods. > I propose to allow the camel route to control this behavior with some > properties. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15751) camel-grpc - Provide access to stream observer in the camel Exchange
[
https://issues.apache.org/jira/browse/CAMEL-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17220248#comment-17220248
]
Dmitry Volodin commented on CAMEL-15751:
Also there are two options for consumer strategy: {color:#871094}AGGREGATION
and {color}{color:#871094}PROPAGATION{color}
{color:#871094}{color:#172b4d}Can you try to use PROPAGATION, process request
and send it later after processing?{color}{color}{color:#871094}
{color}
> camel-grpc - Provide access to stream observer in the camel Exchange
>
>
> Key: CAMEL-15751
> URL: https://issues.apache.org/jira/browse/CAMEL-15751
> Project: Camel
> Issue Type: New Feature
> Components: camel-grpc
>Reporter: Rajasekhar Bhupasamudram
>Assignee: Dmitry Volodin
>Priority: Minor
> Fix For: 3.7.0
>
>
> Current camel-grpc module provides both the consumer and producer abilities.
> But, does not allow the camel route to have control over when the responses
> are sent back to the client.
>
> {code:java}
>
> uri="grpc://remotehost:1101/org.apache.camel.component.grpc.PingPong?consumerStrategy=PROPAGATION"/>
>
>
> {code}
>
> Consider the as an example for grpc consumer (server streaming end point).
> In the above, myCustomProcessor can modify the Exchange and set a Message,
> but if it needs to respond to the client multiple times with a time gap,
> using _responseObserver.onNext()_ method calls, then it can't. There is a
> possibility to collect all the responses in a list and send the list items
> one after the other. But, if the processor needs to wait for certain amount
> of time to compute the next response, and then invoke the onNext, it is not
> possible.
> I think it is a limitation of the camel-grpc component and propose to enhance
> it by setting the responseObserver as a property in the Exchange object.
> Another improvement that I see is that, In the
> _GrpcRequestPropagationStreamObserver_,
> # The _responseStream.onCompleted()_ is called every time an onNext is
> invoked. This does not leverage the Http 2.0 abilities to send the responses
> back to the client asynchronously.
> # Every time, the camel route is traversed, the server is sending some
> response to the client using the onNext method calls. But, sometimes, it may
> be a good idea to not to send any data immediately.
> I propose to allow the camel route to control this behavior with some
> properties.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-15751) camel-grpc - Provide access to stream observer in the camel Exchange
[
https://issues.apache.org/jira/browse/CAMEL-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17220245#comment-17220245
]
Dmitry Volodin edited comment on CAMEL-15751 at 10/25/20, 6:11 AM:
---
Hi [~rajasekharb] . Could you please separate issues from each other:
# Base improvement to provide access to stream observer in the camel Exchange
# Another improvement related to the _GrpcRequestPropagationStreamObserver_
_For the second, please open a new one with the case of improvement and leave
in the current issue and PR just a new feature_
_Thank you._
was (Author: dmvolod):
Hi [~rajasekharb] . Could you please separate issues from each others:
# Base improvement to provide access to stream observer in the camel Exchange
# Another improvement related to the _GrpcRequestPropagationStreamObserver_
_For the second, please open a new one with the case of improvement and leave
in the current issue and PR just a new feature_
_Thank you._
> camel-grpc - Provide access to stream observer in the camel Exchange
>
>
> Key: CAMEL-15751
> URL: https://issues.apache.org/jira/browse/CAMEL-15751
> Project: Camel
> Issue Type: New Feature
> Components: camel-grpc
>Reporter: Rajasekhar Bhupasamudram
>Assignee: Dmitry Volodin
>Priority: Minor
> Fix For: 3.7.0
>
>
> Current camel-grpc module provides both the consumer and producer abilities.
> But, does not allow the camel route to have control over when the responses
> are sent back to the client.
>
> {code:java}
>
> uri="grpc://remotehost:1101/org.apache.camel.component.grpc.PingPong?consumerStrategy=PROPAGATION"/>
>
>
> {code}
>
> Consider the as an example for grpc consumer (server streaming end point).
> In the above, myCustomProcessor can modify the Exchange and set a Message,
> but if it needs to respond to the client multiple times with a time gap,
> using _responseObserver.onNext()_ method calls, then it can't. There is a
> possibility to collect all the responses in a list and send the list items
> one after the other. But, if the processor needs to wait for certain amount
> of time to compute the next response, and then invoke the onNext, it is not
> possible.
> I think it is a limitation of the camel-grpc component and propose to enhance
> it by setting the responseObserver as a property in the Exchange object.
> Another improvement that I see is that, In the
> _GrpcRequestPropagationStreamObserver_,
> # The _responseStream.onCompleted()_ is called every time an onNext is
> invoked. This does not leverage the Http 2.0 abilities to send the responses
> back to the client asynchronously.
> # Every time, the camel route is traversed, the server is sending some
> response to the client using the onNext method calls. But, sometimes, it may
> be a good idea to not to send any data immediately.
> I propose to allow the camel route to control this behavior with some
> properties.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15751) camel-grpc - Provide access to stream observer in the camel Exchange
[
https://issues.apache.org/jira/browse/CAMEL-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17220245#comment-17220245
]
Dmitry Volodin commented on CAMEL-15751:
Hi [~rajasekharb] . Could you please separate issues from each others:
# Base improvement to provide access to stream observer in the camel Exchange
# Another improvement related to the _GrpcRequestPropagationStreamObserver_
_For the second, please open a new one with the case of improvement and leave
in the current issue and PR just a new feature_
_Thank you._
> camel-grpc - Provide access to stream observer in the camel Exchange
>
>
> Key: CAMEL-15751
> URL: https://issues.apache.org/jira/browse/CAMEL-15751
> Project: Camel
> Issue Type: New Feature
> Components: camel-grpc
>Reporter: Rajasekhar Bhupasamudram
>Assignee: Dmitry Volodin
>Priority: Minor
> Fix For: 3.7.0
>
>
> Current camel-grpc module provides both the consumer and producer abilities.
> But, does not allow the camel route to have control over when the responses
> are sent back to the client.
>
> {code:java}
>
> uri="grpc://remotehost:1101/org.apache.camel.component.grpc.PingPong?consumerStrategy=PROPAGATION"/>
>
>
> {code}
>
> Consider the as an example for grpc consumer (server streaming end point).
> In the above, myCustomProcessor can modify the Exchange and set a Message,
> but if it needs to respond to the client multiple times with a time gap,
> using _responseObserver.onNext()_ method calls, then it can't. There is a
> possibility to collect all the responses in a list and send the list items
> one after the other. But, if the processor needs to wait for certain amount
> of time to compute the next response, and then invoke the onNext, it is not
> possible.
> I think it is a limitation of the camel-grpc component and propose to enhance
> it by setting the responseObserver as a property in the Exchange object.
> Another improvement that I see is that, In the
> _GrpcRequestPropagationStreamObserver_,
> # The _responseStream.onCompleted()_ is called every time an onNext is
> invoked. This does not leverage the Http 2.0 abilities to send the responses
> back to the client asynchronously.
> # Every time, the camel route is traversed, the server is sending some
> response to the client using the onNext method calls. But, sometimes, it may
> be a good idea to not to send any data immediately.
> I propose to allow the camel route to control this behavior with some
> properties.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-15751) camel-grpc - Provide access to stream observer in the camel Exchange
[
https://issues.apache.org/jira/browse/CAMEL-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-15751:
--
Assignee: Dmitry Volodin
> camel-grpc - Provide access to stream observer in the camel Exchange
>
>
> Key: CAMEL-15751
> URL: https://issues.apache.org/jira/browse/CAMEL-15751
> Project: Camel
> Issue Type: New Feature
> Components: camel-grpc
>Reporter: Rajasekhar Bhupasamudram
>Assignee: Dmitry Volodin
>Priority: Minor
> Fix For: 3.7.0
>
>
> Current camel-grpc module provides both the consumer and producer abilities.
> But, does not allow the camel route to have control over when the responses
> are sent back to the client.
>
> {code:java}
>
> uri="grpc://remotehost:1101/org.apache.camel.component.grpc.PingPong?consumerStrategy=PROPAGATION"/>
>
>
> {code}
>
> Consider the as an example for grpc consumer (server streaming end point).
> In the above, myCustomProcessor can modify the Exchange and set a Message,
> but if it needs to respond to the client multiple times with a time gap,
> using _responseObserver.onNext()_ method calls, then it can't. There is a
> possibility to collect all the responses in a list and send the list items
> one after the other. But, if the processor needs to wait for certain amount
> of time to compute the next response, and then invoke the onNext, it is not
> possible.
> I think it is a limitation of the camel-grpc component and propose to enhance
> it by setting the responseObserver as a property in the Exchange object.
> Another improvement that I see is that, In the
> _GrpcRequestPropagationStreamObserver_,
> # The _responseStream.onCompleted()_ is called every time an onNext is
> invoked. This does not leverage the Http 2.0 abilities to send the responses
> back to the client asynchronously.
> # Every time, the camel route is traversed, the server is sending some
> response to the client using the onNext method calls. But, sometimes, it may
> be a good idea to not to send any data immediately.
> I propose to allow the camel route to control this behavior with some
> properties.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15145) Create a gRPC component based on vert.x
[ https://issues.apache.org/jira/browse/CAMEL-15145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17121126#comment-17121126 ] Dmitry Volodin commented on CAMEL-15145: [~jamesnetherton], yes, sounds good, but I would like to try investigate is it possible to migrate current implementation to the vertx-grpc I would be nice to have just one implementation for gRPC rather than more one. Otherwise, I think it possible to extend vertx-grpc for unsupported features if needed. > Create a gRPC component based on vert.x > --- > > Key: CAMEL-15145 > URL: https://issues.apache.org/jira/browse/CAMEL-15145 > Project: Camel > Issue Type: New Feature >Reporter: James Netherton >Priority: Minor > Fix For: 3.x > > > It'd be good for Quarkus integration if the the gRPC component could support > vertx-grpc (for both producer & consumer). > Not sure if it's feasible or correct to modify the existing camel-grpc > component to support this. Hence I propose a new component. > [~dmvolod] what do you think? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14989) [camel-mongodb] Missing ObjectId converter
[
https://issues.apache.org/jira/browse/CAMEL-14989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-14989:
---
Fix Version/s: 3.3.0
> [camel-mongodb] Missing ObjectId converter
> --
>
> Key: CAMEL-14989
> URL: https://issues.apache.org/jira/browse/CAMEL-14989
> Project: Camel
> Issue Type: Improvement
> Components: camel-mongodb
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Major
> Fix For: 3.3.0
>
>
> When we use default __id_ document parameter, Mongo assume it's an _ObjectId_
> type. If we include a converter we simplify the creation of any route by just
> adding:
> {code}
>.convertBodyTo(ObjectId.class)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14989) [camel-mongodb] Missing ObjectId converter
[
https://issues.apache.org/jira/browse/CAMEL-14989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-14989:
---
Component/s: camel-mongodb
> [camel-mongodb] Missing ObjectId converter
> --
>
> Key: CAMEL-14989
> URL: https://issues.apache.org/jira/browse/CAMEL-14989
> Project: Camel
> Issue Type: Improvement
> Components: camel-mongodb
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Major
>
> When we use default __id_ document parameter, Mongo assume it's an _ObjectId_
> type. If we include a converter we simplify the creation of any route by just
> adding:
> {code}
>.convertBodyTo(ObjectId.class)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14983) Replace commons Base64 for JDK Base64
[ https://issues.apache.org/jira/browse/CAMEL-14983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14983: --- Fix Version/s: 3.3.0 > Replace commons Base64 for JDK Base64 > - > > Key: CAMEL-14983 > URL: https://issues.apache.org/jira/browse/CAMEL-14983 > Project: Camel > Issue Type: Improvement > Components: camel-jira >Reporter: Claudio Miranda >Priority: Minor > Fix For: 3.3.0 > > > Jira component uses a repackaged commons-codec package to use the Base64 > class. > We should the java.util.Base64 class instead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14983) Replace commons Base64 for JDK Base64
[ https://issues.apache.org/jira/browse/CAMEL-14983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14983: --- Component/s: camel-jira > Replace commons Base64 for JDK Base64 > - > > Key: CAMEL-14983 > URL: https://issues.apache.org/jira/browse/CAMEL-14983 > Project: Camel > Issue Type: Improvement > Components: camel-jira >Reporter: Claudio Miranda >Priority: Minor > > Jira component uses a repackaged commons-codec package to use the Base64 > class. > We should the java.util.Base64 class instead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14958) Suggestion on search bar within smaller screen width.
[ https://issues.apache.org/jira/browse/CAMEL-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14958: --- Component/s: website > Suggestion on search bar within smaller screen width. > - > > Key: CAMEL-14958 > URL: https://issues.apache.org/jira/browse/CAMEL-14958 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aemie >Priority: Minor > > Within the small width screen, the setting is to only display the social icon > button as of now. However, I thought it would be a good idea to include the > search icon alongside the social button icons. On click of the social button > icons, we could include animation, for instance, a fade-in effect of the > search bar occupying the entire navbar. The user can do the search as > required. On the left side of the search bar, there will be back arrow, which > on click would give us the original navbar look with a fade-out effect. > > For clarification, this link [Search Bar expansion > effect|https://codepen.io/aemiej/pen/LYpZJdY] will show you what I am trying > to suggest. > > Before I start working on this, I would like an opinion about this idea. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14946) Allow overriding of buildah image with "kamel install" switches
[ https://issues.apache.org/jira/browse/CAMEL-14946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089279#comment-17089279 ] Dmitry Volodin commented on CAMEL-14946: [~dtremblay], camel-k has own issue tracker on GitHub [https://github.com/apache/camel-k/issues] Please submit it there > Allow overriding of buildah image with "kamel install" switches > --- > > Key: CAMEL-14946 > URL: https://issues.apache.org/jira/browse/CAMEL-14946 > Project: Camel > Issue Type: Bug > Components: camel-k >Affects Versions: 1.0.0 > Environment: Running in a corporate network, where Kubernetes cluster > doesn't have access to DockerHub (or quay.io in this case). > * Kubernetes 1.11.5 > * Docker-ce 18.0 > * Local registry is set to an internal insecure registry > * Kamel CLI version 1.0.0-RC2 > >Reporter: Daniel Tremblay >Priority: Minor > > Add a new kamel install switch to allow overriding the buildah image, e.g. > "*--buildah-image*" > This switch would work in a similar fashion to "--base-image" and > "--operator-image". > Whenever a new "kamel run" command gets used, the overriden buildah image > would get used. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14932) Camel Splunk HEC component
[ https://issues.apache.org/jira/browse/CAMEL-14932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14932: --- Affects Version/s: (was: 3.2.0) 3.3.0 > Camel Splunk HEC component > --- > > Key: CAMEL-14932 > URL: https://issues.apache.org/jira/browse/CAMEL-14932 > Project: Camel > Issue Type: New Feature > Components: camel-splunk-hec >Affects Versions: 3.3.0 >Reporter: Antoine Toulme >Priority: Minor > Fix For: 3.3.0 > > > Create a new component specifically for Splunk HEC (HTTP Event Collector). > The existing camel-splunk component is a powerhouse that allows to send and > draw data from a Splunk instance. However for most use cases, HEC is used in > enterprises to send data to Splunk. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14932) Camel Splunk HEC component
[ https://issues.apache.org/jira/browse/CAMEL-14932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14932: --- Fix Version/s: 3.3.0 > Camel Splunk HEC component > --- > > Key: CAMEL-14932 > URL: https://issues.apache.org/jira/browse/CAMEL-14932 > Project: Camel > Issue Type: New Feature > Components: camel-splunk-hec >Affects Versions: 3.2.0 >Reporter: Antoine Toulme >Priority: Minor > Fix For: 3.3.0 > > > Create a new component specifically for Splunk HEC (HTTP Event Collector). > The existing camel-splunk component is a powerhouse that allows to send and > draw data from a Splunk instance. However for most use cases, HEC is used in > enterprises to send data to Splunk. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14932) Camel Splunk HEC component
[ https://issues.apache.org/jira/browse/CAMEL-14932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14932: --- Component/s: camel-splunk-hec > Camel Splunk HEC component > --- > > Key: CAMEL-14932 > URL: https://issues.apache.org/jira/browse/CAMEL-14932 > Project: Camel > Issue Type: New Feature > Components: camel-splunk-hec >Affects Versions: 3.2.0 >Reporter: Antoine Toulme >Priority: Minor > > Create a new component specifically for Splunk HEC (HTTP Event Collector). > The existing camel-splunk component is a powerhouse that allows to send and > draw data from a Splunk instance. However for most use cases, HEC is used in > enterprises to send data to Splunk. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14915) Trying to create directory (FtpOperations.buildDirectory) without starting directory in ftps URI
[
https://issues.apache.org/jira/browse/CAMEL-14915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-14915:
---
Fix Version/s: 2.25.2
> Trying to create directory (FtpOperations.buildDirectory) without starting
> directory in ftps URI
>
>
> Key: CAMEL-14915
> URL: https://issues.apache.org/jira/browse/CAMEL-14915
> Project: Camel
> Issue Type: Bug
> Components: camel-ftp
>Affects Versions: 2.24.0
> Environment: mac/linux
>Reporter: Jin Feng
>Priority: Major
> Fix For: 2.25.2, 3.x
>
>
> Hi,
> I setup a route using this FTPS URI:
> {noformat}
> ftps://filetransfer.bpost.be/?bridgeErrorHandler=true=6=60=true=true=..=%23gfpIdempotentRepository=true=%2Ftmp%2F895c3952-e3f7-401f-b38f-055fcdf44301=0=archive=true=xx
> {noformat}
> You can see we didn't specify starting directory which we assume it would be
> defaulted to "/", but actually inside the code it gets defaulted to "" empty.
> Upon debugging, I see this behavior from camel
> [FtpConsumer.doStart()|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpConsumer.java#L77]:
> {code:java}
> try {
> connectIfNecessary();
>
> operations.buildDirectory(endpoint.getConfiguration().getDirectory(), true);
> } catch (GenericFileOperationFailedException e) {
> // log a WARN as we want to start the consumer.
> LOG.warn("Error auto creating directory: " +
> endpoint.getConfiguration().getDirectory() + " due " + e.getMessage() + ".
> This exception is ignored.", e);
> }
> {code}
> Now my ftp URI doesn't have starting directory, (which is optional according
> to [https://camel.apache.org/components/latest/ftps-component.html]), so the
> `getDirector()` here returns "" empty string. And then inside
> [FtpOperations.buildDirectory()|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpOperations.java#L359]:
> {code:java}
> try {
> // maybe the full directory already exists
> success = client.changeWorkingDirectory(directory);
> if (!success) {
> log.trace("Trying to build remote directory: {}",
> directory);
> success = client.makeDirectory(directory);
> if (!success) {
> // we are here if the server side doesn't create
> // intermediate folders so create the folder one by
> one
> success = buildDirectoryChunks(directory);
> }
> }
> return success;
> } finally {
> {code}
> It tries first to enter the "" directory, which failed. Then it tried to
> makeDirectory(""), which failed as well, after a very long timeout.
>
> Of course we can use "autoCreate=false" to turn this behavior off. But my
> question is why do we want to try to autoCreate a directory when the
> directory string is actually "" empty?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14915) Trying to create directory (FtpOperations.buildDirectory) without starting directory in ftps URI
[
https://issues.apache.org/jira/browse/CAMEL-14915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086408#comment-17086408
]
Dmitry Volodin commented on CAMEL-14915:
[~jinfengnarvar], yes, looks like you are right.
We should set 'directory' to \ if it's not set explicitly
> Trying to create directory (FtpOperations.buildDirectory) without starting
> directory in ftps URI
>
>
> Key: CAMEL-14915
> URL: https://issues.apache.org/jira/browse/CAMEL-14915
> Project: Camel
> Issue Type: Bug
> Components: camel-ftp
>Affects Versions: 2.24.0
> Environment: mac/linux
>Reporter: Jin Feng
>Priority: Major
> Fix For: 3.x
>
>
> Hi,
> I setup a route using this FTPS URI:
> {noformat}
> ftps://filetransfer.bpost.be/?bridgeErrorHandler=true=6=60=true=true=..=%23gfpIdempotentRepository=true=%2Ftmp%2F895c3952-e3f7-401f-b38f-055fcdf44301=0=archive=true=xx
> {noformat}
> You can see we didn't specify starting directory which we assume it would be
> defaulted to "/", but actually inside the code it gets defaulted to "" empty.
> Upon debugging, I see this behavior from camel
> [FtpConsumer.doStart()|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpConsumer.java#L77]:
> {code:java}
> try {
> connectIfNecessary();
>
> operations.buildDirectory(endpoint.getConfiguration().getDirectory(), true);
> } catch (GenericFileOperationFailedException e) {
> // log a WARN as we want to start the consumer.
> LOG.warn("Error auto creating directory: " +
> endpoint.getConfiguration().getDirectory() + " due " + e.getMessage() + ".
> This exception is ignored.", e);
> }
> {code}
> Now my ftp URI doesn't have starting directory, (which is optional according
> to [https://camel.apache.org/components/latest/ftps-component.html]), so the
> `getDirector()` here returns "" empty string. And then inside
> [FtpOperations.buildDirectory()|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpOperations.java#L359]:
> {code:java}
> try {
> // maybe the full directory already exists
> success = client.changeWorkingDirectory(directory);
> if (!success) {
> log.trace("Trying to build remote directory: {}",
> directory);
> success = client.makeDirectory(directory);
> if (!success) {
> // we are here if the server side doesn't create
> // intermediate folders so create the folder one by
> one
> success = buildDirectoryChunks(directory);
> }
> }
> return success;
> } finally {
> {code}
> It tries first to enter the "" directory, which failed. Then it tried to
> makeDirectory(""), which failed as well, after a very long timeout.
>
> Of course we can use "autoCreate=false" to turn this behavior off. But my
> question is why do we want to try to autoCreate a directory when the
> directory string is actually "" empty?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14915) Trying to create directory (FtpOperations.buildDirectory) without starting directory in ftps URI
[
https://issues.apache.org/jira/browse/CAMEL-14915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-14915:
---
Summary: Trying to create directory (FtpOperations.buildDirectory) without
starting directory in ftps URI (was: Trying to create directory
(FtpOperations.buildDirectory) when FTPS route without starting directory in
ftps URI)
> Trying to create directory (FtpOperations.buildDirectory) without starting
> directory in ftps URI
>
>
> Key: CAMEL-14915
> URL: https://issues.apache.org/jira/browse/CAMEL-14915
> Project: Camel
> Issue Type: Bug
> Components: camel-ftp
>Affects Versions: 2.24.0
> Environment: mac/linux
>Reporter: Jin Feng
>Priority: Major
> Fix For: 3.x
>
>
> Hi,
> I setup a route using this FTPS URI:
> {noformat}
> ftps://filetransfer.bpost.be/?bridgeErrorHandler=true=6=60=true=true=..=%23gfpIdempotentRepository=true=%2Ftmp%2F895c3952-e3f7-401f-b38f-055fcdf44301=0=archive=true=xx
> {noformat}
> You can see we didn't specify starting directory which we assume it would be
> defaulted to "/", but actually inside the code it gets defaulted to "" empty.
> Upon debugging, I see this behavior from camel
> [FtpConsumer.doStart()|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpConsumer.java#L77]:
> {code:java}
> try {
> connectIfNecessary();
>
> operations.buildDirectory(endpoint.getConfiguration().getDirectory(), true);
> } catch (GenericFileOperationFailedException e) {
> // log a WARN as we want to start the consumer.
> LOG.warn("Error auto creating directory: " +
> endpoint.getConfiguration().getDirectory() + " due " + e.getMessage() + ".
> This exception is ignored.", e);
> }
> {code}
> Now my ftp URI doesn't have starting directory, (which is optional according
> to [https://camel.apache.org/components/latest/ftps-component.html]), so the
> `getDirector()` here returns "" empty string. And then inside
> [FtpOperations.buildDirectory()|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpOperations.java#L359]:
> {code:java}
> try {
> // maybe the full directory already exists
> success = client.changeWorkingDirectory(directory);
> if (!success) {
> log.trace("Trying to build remote directory: {}",
> directory);
> success = client.makeDirectory(directory);
> if (!success) {
> // we are here if the server side doesn't create
> // intermediate folders so create the folder one by
> one
> success = buildDirectoryChunks(directory);
> }
> }
> return success;
> } finally {
> {code}
> It tries first to enter the "" directory, which failed. Then it tried to
> makeDirectory(""), which failed as well, after a very long timeout.
>
> Of course we can use "autoCreate=false" to turn this behavior off. But my
> question is why do we want to try to autoCreate a directory when the
> directory string is actually "" empty?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14915) Trying to create directory (FtpOperations.buildDirectory) when FTPS route without starting directory in ftps URI
[
https://issues.apache.org/jira/browse/CAMEL-14915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-14915:
---
Summary: Trying to create directory (FtpOperations.buildDirectory) when
FTPS route without starting directory in ftps URI (was: Why we're trying to
create directory (FtpOperations.buildDirectory) when we have an FTPS route with
no starting directory in camel ftps URI)
> Trying to create directory (FtpOperations.buildDirectory) when FTPS route
> without starting directory in ftps URI
>
>
> Key: CAMEL-14915
> URL: https://issues.apache.org/jira/browse/CAMEL-14915
> Project: Camel
> Issue Type: Bug
> Components: camel-ftp
>Affects Versions: 2.24.0
> Environment: mac/linux
>Reporter: Jin Feng
>Priority: Major
> Fix For: 3.x
>
>
> Hi,
> I setup a route using this FTPS URI:
> {noformat}
> ftps://filetransfer.bpost.be/?bridgeErrorHandler=true=6=60=true=true=..=%23gfpIdempotentRepository=true=%2Ftmp%2F895c3952-e3f7-401f-b38f-055fcdf44301=0=archive=true=xx
> {noformat}
> You can see we didn't specify starting directory which we assume it would be
> defaulted to "/", but actually inside the code it gets defaulted to "" empty.
> Upon debugging, I see this behavior from camel
> [FtpConsumer.doStart()|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpConsumer.java#L77]:
> {code:java}
> try {
> connectIfNecessary();
>
> operations.buildDirectory(endpoint.getConfiguration().getDirectory(), true);
> } catch (GenericFileOperationFailedException e) {
> // log a WARN as we want to start the consumer.
> LOG.warn("Error auto creating directory: " +
> endpoint.getConfiguration().getDirectory() + " due " + e.getMessage() + ".
> This exception is ignored.", e);
> }
> {code}
> Now my ftp URI doesn't have starting directory, (which is optional according
> to [https://camel.apache.org/components/latest/ftps-component.html]), so the
> `getDirector()` here returns "" empty string. And then inside
> [FtpOperations.buildDirectory()|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpOperations.java#L359]:
> {code:java}
> try {
> // maybe the full directory already exists
> success = client.changeWorkingDirectory(directory);
> if (!success) {
> log.trace("Trying to build remote directory: {}",
> directory);
> success = client.makeDirectory(directory);
> if (!success) {
> // we are here if the server side doesn't create
> // intermediate folders so create the folder one by
> one
> success = buildDirectoryChunks(directory);
> }
> }
> return success;
> } finally {
> {code}
> It tries first to enter the "" directory, which failed. Then it tried to
> makeDirectory(""), which failed as well, after a very long timeout.
>
> Of course we can use "autoCreate=false" to turn this behavior off. But my
> question is why do we want to try to autoCreate a directory when the
> directory string is actually "" empty?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14920) documentation - Split the 3.x upgrade page into sub pages
[ https://issues.apache.org/jira/browse/CAMEL-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14920: --- Component/s: documentation > documentation - Split the 3.x upgrade page into sub pages > - > > Key: CAMEL-14920 > URL: https://issues.apache.org/jira/browse/CAMEL-14920 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > > Today we have a single long page > https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html > Instead we should have sub pages with > 1) > https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html > with some general information, and mention that to follow all the guides when > upgrading, eg 3.0 to 3.2, then you should do 3.0 -> 3.1 and 3.1 -> 3.2. > And a bullet list with the sub pages > - upgrade camel 3.0 to 3.1 > - upgrade camel 3.1 to 3.2 > - upgrade camel 3.2 to 3.3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14881) Add comment 'autogenerated' to the docs/components adoc files
[ https://issues.apache.org/jira/browse/CAMEL-14881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083869#comment-17083869 ] Dmitry Volodin edited comment on CAMEL-14881 at 4/15/20, 7:30 AM: -- Yes, agree with you, [~djencks] Thanks a lot. But would be nice to have an original task name in sub-tasks was (Author: dmvolod): Yes, agree with you, [~djencks] Thanks a lot. > Add comment 'autogenerated' to the docs/components adoc files > -- > > Key: CAMEL-14881 > URL: https://issues.apache.org/jira/browse/CAMEL-14881 > Project: Camel > Issue Type: Improvement > Components: documentation >Reporter: Dmitry Volodin >Assignee: David Jencks >Priority: Minor > Labels: help-wanted > > Adding following comment on the top of the all auto-generated adoc files > inside docs/components to notate users don't edit this files > // AUTOGENERATED, PLEASE DON'T EDIT THIS FILE!!! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14881) Add comment 'autogenerated' to the docs/components adoc files
[ https://issues.apache.org/jira/browse/CAMEL-14881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083869#comment-17083869 ] Dmitry Volodin commented on CAMEL-14881: Yes, agree with you, [~djencks] Thanks a lot. > Add comment 'autogenerated' to the docs/components adoc files > -- > > Key: CAMEL-14881 > URL: https://issues.apache.org/jira/browse/CAMEL-14881 > Project: Camel > Issue Type: Improvement > Components: documentation >Reporter: Dmitry Volodin >Assignee: David Jencks >Priority: Minor > Labels: help-wanted > > Adding following comment on the top of the all auto-generated adoc files > inside docs/components to notate users don't edit this files > // AUTOGENERATED, PLEASE DON'T EDIT THIS FILE!!! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14893) camel-grpc - Should handle if exchange failed as onError
[ https://issues.apache.org/jira/browse/CAMEL-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14893: --- Summary: camel-grpc - Should handle if exchange failed as onError (was: camel-grps - Should handle if exchange failed as onError) > camel-grpc - Should handle if exchange failed as onError > > > Key: CAMEL-14893 > URL: https://issues.apache.org/jira/browse/CAMEL-14893 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Affects Versions: 3.2.0 > Environment: * java 8 > * spring boot 2.2.4.RELEASE > * camel-grpc 3.3.0-SNAPSHOT >Reporter: son, kyoungduk >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.3.0, 2.25.2 > > Attachments: handling-onerror.txt > > Time Spent: 20m > Remaining Estimate: 0h > > If the processor associated with the grpc endpoint throws an exception, the > caller will not receive an exception response. > When an exception is thrown by the processor, the exception message is > returned to the caller using onError. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14893) Handling onError
[ https://issues.apache.org/jira/browse/CAMEL-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin resolved CAMEL-14893. Resolution: Fixed Thanks, [~kyoungduk] Fixed > Handling onError > > > Key: CAMEL-14893 > URL: https://issues.apache.org/jira/browse/CAMEL-14893 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Affects Versions: 3.2.0 > Environment: * java 8 > * spring boot 2.2.4.RELEASE > * camel-grpc 3.3.0-SNAPSHOT >Reporter: son, kyoungduk >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.3.0 > > Attachments: handling-onerror.txt > > > If the processor associated with the grpc endpoint throws an exception, the > caller will not receive an exception response. > When an exception is thrown by the processor, the exception message is > returned to the caller using onError. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14893) Handling onError
[ https://issues.apache.org/jira/browse/CAMEL-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083248#comment-17083248 ] Dmitry Volodin commented on CAMEL-14893: Also note, that this occurs only in in synchronous mode. > Handling onError > > > Key: CAMEL-14893 > URL: https://issues.apache.org/jira/browse/CAMEL-14893 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Affects Versions: 3.2.0 > Environment: * java 8 > * spring boot 2.2.4.RELEASE > * camel-grpc 3.3.0-SNAPSHOT >Reporter: son, kyoungduk >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.3.0 > > Attachments: handling-onerror.txt > > > If the processor associated with the grpc endpoint throws an exception, the > caller will not receive an exception response. > When an exception is thrown by the processor, the exception message is > returned to the caller using onError. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14893) Handling onError
[ https://issues.apache.org/jira/browse/CAMEL-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14893: --- Affects Version/s: (was: 3.3.0) 3.2.0 > Handling onError > > > Key: CAMEL-14893 > URL: https://issues.apache.org/jira/browse/CAMEL-14893 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Affects Versions: 3.2.0 > Environment: * java 8 > * spring boot 2.2.4.RELEASE > * camel-grpc 3.3.0-SNAPSHOT >Reporter: son, kyoungduk >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.3.0 > > Attachments: handling-onerror.txt > > > If the processor associated with the grpc endpoint throws an exception, the > caller will not receive an exception response. > When an exception is thrown by the processor, the exception message is > returned to the caller using onError. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14893) Handling onError
[ https://issues.apache.org/jira/browse/CAMEL-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083159#comment-17083159 ] Dmitry Volodin commented on CAMEL-14893: Thanks, [~kyoungduk] I will also add a test case for this issue. > Handling onError > > > Key: CAMEL-14893 > URL: https://issues.apache.org/jira/browse/CAMEL-14893 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Affects Versions: 3.2.0 > Environment: * java 8 > * spring boot 2.2.4.RELEASE > * camel-grpc 3.3.0-SNAPSHOT >Reporter: son, kyoungduk >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.3.0 > > Attachments: handling-onerror.txt > > > If the processor associated with the grpc endpoint throws an exception, the > caller will not receive an exception response. > When an exception is thrown by the processor, the exception message is > returned to the caller using onError. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14893) Handling onError
[ https://issues.apache.org/jira/browse/CAMEL-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-14893: -- Assignee: Dmitry Volodin > Handling onError > > > Key: CAMEL-14893 > URL: https://issues.apache.org/jira/browse/CAMEL-14893 > Project: Camel > Issue Type: Improvement > Components: camel-grpc >Affects Versions: 3.3.0 > Environment: * java 8 > * spring boot 2.2.4.RELEASE > * camel-grpc 3.3.0-SNAPSHOT >Reporter: son, kyoungduk >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.3.0 > > Attachments: handling-onerror.txt > > > If the processor associated with the grpc endpoint throws an exception, the > caller will not receive an exception response. > When an exception is thrown by the processor, the exception message is > returned to the caller using onError. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14881) Add comment 'autogenerated' to the docs/components adoc files
[ https://issues.apache.org/jira/browse/CAMEL-14881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082868#comment-17082868 ] Dmitry Volodin commented on CAMEL-14881: Yes, [~djencks] , sure. > Add comment 'autogenerated' to the docs/components adoc files > -- > > Key: CAMEL-14881 > URL: https://issues.apache.org/jira/browse/CAMEL-14881 > Project: Camel > Issue Type: Improvement > Components: documentation >Reporter: Dmitry Volodin >Priority: Minor > Labels: help-wanted > > Adding following comment on the top of the all auto-generated adoc files > inside docs/components to notate users don't edit this files > // AUTOGENERATED, PLEASE DON'T EDIT THIS FILE!!! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14881) Add comment 'autogenerated' to the docs/components adoc files
[ https://issues.apache.org/jira/browse/CAMEL-14881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082101#comment-17082101 ] Dmitry Volodin commented on CAMEL-14881: [~djencks], I know that original docs not auto-generated at all, but I was taking about files in docs/components which are copied from the components itself. Many people tried to edit them and on the next Regen stage they are rewriting from the origin. > Add comment 'autogenerated' to the docs/components adoc files > -- > > Key: CAMEL-14881 > URL: https://issues.apache.org/jira/browse/CAMEL-14881 > Project: Camel > Issue Type: Improvement > Components: documentation >Reporter: Dmitry Volodin >Priority: Minor > Labels: help-wanted > > Adding following comment on the top of the all auto-generated adoc files > inside docs/components to notate users don't edit this files > // AUTOGENERATED, PLEASE DON'T EDIT THIS FILE!!! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14881) Add comment 'autogenerated' to the docs/components adoc files
[ https://issues.apache.org/jira/browse/CAMEL-14881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082093#comment-17082093 ] Dmitry Volodin commented on CAMEL-14881: [~arunmannuru], yes, sure, but would be nice to hear other opinions related to this case. [~zregvart], [~djencks] what do you think about it? > Add comment 'autogenerated' to the docs/components adoc files > -- > > Key: CAMEL-14881 > URL: https://issues.apache.org/jira/browse/CAMEL-14881 > Project: Camel > Issue Type: Improvement > Components: documentation >Reporter: Dmitry Volodin >Priority: Minor > Labels: help-wanted > > Adding following comment on the top of the all auto-generated adoc files > inside docs/components to notate users don't edit this files > // AUTOGENERATED, PLEASE DON'T EDIT THIS FILE!!! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14881) Add comment 'autogenerated' to the docs/components adoc files
Dmitry Volodin created CAMEL-14881: -- Summary: Add comment 'autogenerated' to the docs/components adoc files Key: CAMEL-14881 URL: https://issues.apache.org/jira/browse/CAMEL-14881 Project: Camel Issue Type: Improvement Components: documentation Reporter: Dmitry Volodin Adding following comment on the top of the all auto-generated adoc files inside docs/components to notate users don't edit this files // AUTOGENERATED, PLEASE DON'T EDIT THIS FILE!!! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14822) Make the CouchDB component work with CouchDB releases > 2.2
[ https://issues.apache.org/jira/browse/CAMEL-14822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079556#comment-17079556 ] Dmitry Volodin commented on CAMEL-14822: Thanks, [~aldettinger] java-cloudant more prefer library, as Erktop didn't released since 2017 > Make the CouchDB component work with CouchDB releases > 2.2 > --- > > Key: CAMEL-14822 > URL: https://issues.apache.org/jira/browse/CAMEL-14822 > Project: Camel > Issue Type: Improvement > Components: camel-couchdb >Affects Versions: 3.1.0 >Reporter: Luca Morandini >Assignee: Alex Dettinger >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Camel is using an old version of LightCouch that does now work properly with > CouchDB versions higher than 2.2. > There is a LightCouch fork (https://github.com/IndabaConsultores/LightCouch) > that works with later CouchDB versions: could Camel use this fork? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14873) Micrometer JMX not published
[ https://issues.apache.org/jira/browse/CAMEL-14873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079272#comment-17079272 ] Dmitry Volodin commented on CAMEL-14873: The micrometer JMX docs says the same you are expecting, but it doesn't update since version 1.0.0 [https://github.com/micrometer-metrics/micrometer-docs/blob/master/src/docs/implementations/jmx.adoc] Looks like they are updating the JMX structure > Micrometer JMX not published > > > Key: CAMEL-14873 > URL: https://issues.apache.org/jira/browse/CAMEL-14873 > Project: Camel > Issue Type: Bug > Components: camel-micrometer >Affects Versions: 3.1.0, 3.2.0 > Environment: Spring Boot 2.1.9-2.2.6 > Camel 3.1.0-3.2.0 > MacOS > IntelliJ IDEA 2019.3.4 >Reporter: Mikael Andersson Wigander >Priority: Major > Attachments: Java_Monitoring___Management_Console.png > > > When using Camel Micrometer component and want them exposed in JMX they are > not, > counter, timer and histo. > Available in JMX from Micrometer are gauge, timer and meter. > Tried to downgrade micrometer but Camel insist bringing in 1.3.6 > Lastest working version tested Camel 2.25.0 > Using the declaration as in documentation including bean and micrometer JMX > dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-12260) Default value for String field results in null for CSV / Bindy
[ https://issues.apache.org/jira/browse/CAMEL-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079001#comment-17079001 ] Dmitry Volodin commented on CAMEL-12260: The minimal Camel 2.x version we are maintaining is 2.25.x. You are welcome to provide PR on top of master and backport it to the 2.25.1. > Default value for String field results in null for CSV / Bindy > -- > > Key: CAMEL-12260 > URL: https://issues.apache.org/jira/browse/CAMEL-12260 > Project: Camel > Issue Type: Bug > Components: camel-bindy >Affects Versions: 2.20.2 >Reporter: Pauli Borodulin >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 2.21.0 > > > **CAMEL-5018 added "support the set the default value on the field of bindy > CVS", which is nice, but the default value is useless for Strings, because > BindyCSVFactory turns the empty value to null even when defaultValue = "", see > [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyCsvFactory.java#L230] > and > [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyAbstractFactory.java#L234] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14873) Micrometer JMX not published
[ https://issues.apache.org/jira/browse/CAMEL-14873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14873: --- Component/s: camel-micrometer > Micrometer JMX not published > > > Key: CAMEL-14873 > URL: https://issues.apache.org/jira/browse/CAMEL-14873 > Project: Camel > Issue Type: Bug > Components: camel-micrometer >Affects Versions: 3.1.0, 3.2.0 > Environment: Spring Boot 2.1.9-2.2.6 > Camel 3.1.0-3.2.0 > MacOS > IntelliJ IDEA 2019.3.4 >Reporter: Mikael Andersson Wigander >Priority: Major > > When using Camel Micrometer component and want them exposed in JMX they are > not, > counter, timer and histo. > Available in JMX from Micrometer are gauge, timer and meter. > Tried to downgrade micrometer but Camel insist bringing in 1.3.6 > Lastest working version tested Camel 2.25.0 > Using the declaration as in documentation including bean and micrometer JMX > dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14873) Micrometer JMX not published
[ https://issues.apache.org/jira/browse/CAMEL-14873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14873: --- Priority: Major (was: Blocker) > Micrometer JMX not published > > > Key: CAMEL-14873 > URL: https://issues.apache.org/jira/browse/CAMEL-14873 > Project: Camel > Issue Type: Bug >Affects Versions: 3.1.0, 3.2.0 > Environment: Spring Boot 2.1.9-2.2.6 > Camel 3.1.0-3.2.0 > MacOS > IntelliJ IDEA 2019.3.4 >Reporter: Mikael Andersson Wigander >Priority: Major > > When using Camel Micrometer component and want them exposed in JMX they are > not, > counter, timer and histo. > Available in JMX from Micrometer are gauge, timer and meter. > Tried to downgrade micrometer but Camel insist bringing in 1.3.6 > Lastest working version tested Camel 2.25.0 > Using the declaration as in documentation including bean and micrometer JMX > dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14873) Micrometer JMX not published
[ https://issues.apache.org/jira/browse/CAMEL-14873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078932#comment-17078932 ] Dmitry Volodin commented on CAMEL-14873: [~hakuseki] , please check required steps from the [https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html] The JMX default behaviour was changed between 2.x and 3.x > Micrometer JMX not published > > > Key: CAMEL-14873 > URL: https://issues.apache.org/jira/browse/CAMEL-14873 > Project: Camel > Issue Type: Bug >Affects Versions: 3.1.0, 3.2.0 > Environment: Spring Boot 2.1.9-2.2.6 > Camel 3.1.0-3.2.0 > MacOS > IntelliJ IDEA 2019.3.4 >Reporter: Mikael Andersson Wigander >Priority: Blocker > > When using Camel Micrometer component and want them exposed in JMX they are > not, > counter, timer and histo. > Available in JMX from Micrometer are gauge, timer and meter. > Tried to downgrade micrometer but Camel insist bringing in 1.3.6 > Lastest working version tested Camel 2.25.0 > Using the declaration as in documentation including bean and micrometer JMX > dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14854) Camel Irc components Fails to rejoin the channels
[
https://issues.apache.org/jira/browse/CAMEL-14854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-14854:
---
Affects Version/s: 3.0.0
> Camel Irc components Fails to rejoin the channels
> -
>
> Key: CAMEL-14854
> URL: https://issues.apache.org/jira/browse/CAMEL-14854
> Project: Camel
> Issue Type: Bug
> Components: camel-irc
>Affects Versions: 3.0.0
>Reporter: Tarun Mahajan
>Priority: Minor
> Labels: help-wanted
> Fix For: 3.x
>
>
> Camel IRC fails to rejoin the channel. We have a module where we are sending
> updates via camel irc and it stores the producers and connection in cache,
> but if due to some reason connection get reset or irc server get restarted
> then all the messages starts to fail as we are not retrying on making new
> connection.
>
> Here is the piece of code where we are checking if connection.isactive or
> not. If not we should try to establish a connection, due to this all messages
> are going to dlq.
> IrcProducer.java
> if (!connection.isConnected()) {
> throw new RuntimeCamelException("Lost connection to " +
> connection.getHost());
> }
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14855) making nav panel explore context content more visible
[ https://issues.apache.org/jira/browse/CAMEL-14855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14855: --- Component/s: website > making nav panel explore context content more visible > - > > Key: CAMEL-14855 > URL: https://issues.apache.org/jira/browse/CAMEL-14855 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Solange Iyubu >Priority: Major > Attachments: nav1.JPG > > > panel explore context is hardly distanguished from nav panel menu -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (CAMEL-14856) making nav panel explore context content more visible
[ https://issues.apache.org/jira/browse/CAMEL-14856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin closed CAMEL-14856. -- Resolution: Duplicate > making nav panel explore context content more visible > - > > Key: CAMEL-14856 > URL: https://issues.apache.org/jira/browse/CAMEL-14856 > Project: Camel > Issue Type: Improvement >Reporter: Solange Iyubu >Priority: Major > Attachments: nav1.JPG > > > nav panel explore context content more visible is hardily distinguished from > nav panel menu -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (CAMEL-14855) making nav panel explore context content more visible
[ https://issues.apache.org/jira/browse/CAMEL-14855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin closed CAMEL-14855. -- Resolution: Duplicate > making nav panel explore context content more visible > - > > Key: CAMEL-14855 > URL: https://issues.apache.org/jira/browse/CAMEL-14855 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Solange Iyubu >Priority: Major > Attachments: nav1.JPG > > > panel explore context is hardly distanguished from nav panel menu -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (CAMEL-14858) making nav panel explore context content more visible
[ https://issues.apache.org/jira/browse/CAMEL-14858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin closed CAMEL-14858. -- Resolution: Duplicate Close as duplicating CAMEL-14857 > making nav panel explore context content more visible > - > > Key: CAMEL-14858 > URL: https://issues.apache.org/jira/browse/CAMEL-14858 > Project: Camel > Issue Type: Improvement >Reporter: Solange Iyubu >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14857) making nav panel explore context content more visible
[ https://issues.apache.org/jira/browse/CAMEL-14857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076956#comment-17076956 ] Dmitry Volodin commented on CAMEL-14857: [~siyubu], please don't forget to mark related component as website > making nav panel explore context content more visible > - > > Key: CAMEL-14857 > URL: https://issues.apache.org/jira/browse/CAMEL-14857 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Solange Iyubu >Priority: Major > Attachments: nav1.JPG, nav3.JPG > > > nav panel explore is hardly distinguishable from nav panel menu -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14857) making nav panel explore context content more visible
[ https://issues.apache.org/jira/browse/CAMEL-14857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14857: --- Component/s: website > making nav panel explore context content more visible > - > > Key: CAMEL-14857 > URL: https://issues.apache.org/jira/browse/CAMEL-14857 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Solange Iyubu >Priority: Major > Attachments: nav1.JPG, nav3.JPG > > > nav panel explore is hardly distinguishable from nav panel menu -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14429) The KEYS link should have KEYS as the text
[ https://issues.apache.org/jira/browse/CAMEL-14429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14429: --- Component/s: website > The KEYS link should have KEYS as the text > -- > > Key: CAMEL-14429 > URL: https://issues.apache.org/jira/browse/CAMEL-14429 > Project: Camel > Issue Type: Task > Components: website >Reporter: Sebb >Priority: Minor > Fix For: 3.x > > > The link to the KEYS file should have 'KEYS' as the text on the download page > to make it easy to find. > Also the link should be at the top level of the project distribution area, > i.e. > https://www.apache.org/dist/camel/KEYS > not > https://www.apache.org/dist/camel/apache-camel/KEYS -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14836) Improvement in the nav-bar menu appearance
[ https://issues.apache.org/jira/browse/CAMEL-14836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14836: --- Component/s: website > Improvement in the nav-bar menu appearance > -- > > Key: CAMEL-14836 > URL: https://issues.apache.org/jira/browse/CAMEL-14836 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aemie >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14833) camel-tika: enhance TikaProducer to use different tika parser instead of AutodetectParser
[ https://issues.apache.org/jira/browse/CAMEL-14833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14833: --- Component/s: camel-tika > camel-tika: enhance TikaProducer to use different tika parser instead of > AutodetectParser > - > > Key: CAMEL-14833 > URL: https://issues.apache.org/jira/browse/CAMEL-14833 > Project: Camel > Issue Type: Improvement > Components: camel-tika >Affects Versions: 3.2.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Minor > > There is a hardcoded creation of AutodetectParser (see > https://github.com/apache/camel/blob/master/components/camel-tika/src/main/java/org/apache/camel/component/tika/TikaProducer.java#L66) > It would make component easily extensible, if there would be some way of > providing parser into TikaProducer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14812) camel-karaf - We should not maintain versions in its root pom.xml
[ https://issues.apache.org/jira/browse/CAMEL-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14812: --- Component/s: karaf > camel-karaf - We should not maintain versions in its root pom.xml > - > > Key: CAMEL-14812 > URL: https://issues.apache.org/jira/browse/CAMEL-14812 > Project: Camel > Issue Type: Improvement > Components: karaf >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.3.0 > > > We should not duplicate versions in parent/pom.xml and then also in > camel-karaf root pom. > camel-karaf should use the versions from camel/parent instead and then if > needed overlay with its own bundle versions. > Today we have duplicates and this means we would get out of sync -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14827) Site Documentation Improvement within Camel
[ https://issues.apache.org/jira/browse/CAMEL-14827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14827: --- Component/s: documentation > Site Documentation Improvement within Camel > > > Key: CAMEL-14827 > URL: https://issues.apache.org/jira/browse/CAMEL-14827 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Aemie >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Within the camel repository, I have observed that the code snippets aren't > properly indentation and structured well. This is present for various > documentation pages. This needs to be improved. > > RESOLVED DOCUMENTATION PAGES > # Caffeine Cache Component > # Cbor Dataformat > # Chunk Component > # HL7 Terser Language > # OGNL Language -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14832) Data format for SWIFT financial message conversion support
Dmitry Volodin created CAMEL-14832:
--
Summary: Data format for SWIFT financial message conversion support
Key: CAMEL-14832
URL: https://issues.apache.org/jira/browse/CAMEL-14832
Project: Camel
Issue Type: New Feature
Reporter: Dmitry Volodin
Fix For: 3.x
Able to support SWIFT financial message conversion with {color:#24292e}Prowide
Core{color} library
This library has Apache License 2.0
[https://github.com/prowide/prowide-core]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14822) Make the CouchDB component work with CouchDB releases > 2.2
[ https://issues.apache.org/jira/browse/CAMEL-14822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14822: --- Issue Type: Improvement (was: Bug) > Make the CouchDB component work with CouchDB releases > 2.2 > --- > > Key: CAMEL-14822 > URL: https://issues.apache.org/jira/browse/CAMEL-14822 > Project: Camel > Issue Type: Improvement > Components: camel-couchdb >Affects Versions: 3.1.0 >Reporter: Luca Morandini >Priority: Major > > Camel is using an old version of LightCouch that does now work properly with > CouchDB versions higher than 2.2. > There is a LightCouch fork (https://github.com/IndabaConsultores/LightCouch) > that works with later CouchDB versions: could Camel use this fork? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14822) Make the CouchDB component work with CouchDB releases > 2.2
[ https://issues.apache.org/jira/browse/CAMEL-14822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073503#comment-17073503 ] Dmitry Volodin commented on CAMEL-14822: [~lmorandini], [~acosentino] maybe [https://github.com/cloudant/java-cloudant] much preferred Java API as it's more actively developing? > Make the CouchDB component work with CouchDB releases > 2.2 > --- > > Key: CAMEL-14822 > URL: https://issues.apache.org/jira/browse/CAMEL-14822 > Project: Camel > Issue Type: Bug > Components: camel-couchdb >Affects Versions: 3.1.0 >Reporter: Luca Morandini >Priority: Major > > Camel is using an old version of LightCouch that does now work properly with > CouchDB versions higher than 2.2. > There is a LightCouch fork (https://github.com/IndabaConsultores/LightCouch) > that works with later CouchDB versions: could Camel use this fork? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14512) Allow reference to custom ClientInterceptor or Producer to customize authentication
[
https://issues.apache.org/jira/browse/CAMEL-14512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-14512:
---
Fix Version/s: 3.3.0
> Allow reference to custom ClientInterceptor or Producer to customize
> authentication
> ---
>
> Key: CAMEL-14512
> URL: https://issues.apache.org/jira/browse/CAMEL-14512
> Project: Camel
> Issue Type: Wish
> Components: camel-grpc
> Environment: * Java 11
> * SpringBoot 2.1.5.RELEASE
> * Camel 3.0.0-M2
> * Camel-Grpc-Starter 3.0.0-M2
>Reporter: Philipp
>Assignee: Dmitry Volodin
>Priority: Minor
> Fix For: 3.3.0
>
>
> The [GRPC
> component|https://github.com/apache/camel/blob/master/components/camel-grpc/src/main/docs/grpc-component.adoc]
> does currently not offer the possibility to intercept the connection
> establishment against the gRPC server out of the box.
> This prevents to add custom authentication to the channel/connection setup.
> And since the gRPC component does not offer this custom implementation out of
> the box, the currently only solution is:
> * Implement a custom {{GrpcComponent}}
> * Implement a custom {{GrpcEndpoint}}
> * Implement a custom {{GrpcProducer}} or {{DefaultAsyncProducer}}
> ** Override the {{doStart()}} method
> ** Instantiate the {{Channel}}
> ** Add a custom {{ClientInterceptor}} and override the {{interceptCall()}}
> method
> ** Add headers to the metadata of the prepared call
> Even though there are the properties {{authenticationType=JWT}},
> {{jwtSecret}}, {{jwtIssuer}} and so on, these arguments only allow constant
> strings. Therefore, no retrieval of OAuth tokens (for example) during the
> runtime is possible, but everything would have to be hard-coded.
> The [AHC-WS
> component|https://github.com/apache/camel/blob/master/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc]
> in contrast, offers this possibility by implementing a custom
> {{AsyncHttpClient}} and pointing to it via the
> {{camel.component.ahc-ws.client}} property in the {{application.yml}}. Like
> this, the connection setup of the websocket can easily be intercepted by
> overriding {{DefaultAsyncHttpClient.prepareGet()}} where OAuth tokens (for
> example) can be passed and added to the handshake.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-13530) Upgrade Milo to 0.3.8
[ https://issues.apache.org/jira/browse/CAMEL-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-13530: --- Fix Version/s: (was: 3.2.0) 3.3.0 > Upgrade Milo to 0.3.8 > - > > Key: CAMEL-13530 > URL: https://issues.apache.org/jira/browse/CAMEL-13530 > Project: Camel > Issue Type: Task > Components: camel-milo >Reporter: Andrea Cosentino >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.3.0 > > > Some breaking changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13530) Upgrade Milo to 0.3.8
[ https://issues.apache.org/jira/browse/CAMEL-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071568#comment-17071568 ] Dmitry Volodin commented on CAMEL-13530: Claus, i will move to 3.3.0 > Upgrade Milo to 0.3.8 > - > > Key: CAMEL-13530 > URL: https://issues.apache.org/jira/browse/CAMEL-13530 > Project: Camel > Issue Type: Task > Components: camel-milo >Reporter: Andrea Cosentino >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.2.0 > > > Some breaking changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14467) camel-jcache - Dynamically bypass the cache for lookups
[ https://issues.apache.org/jira/browse/CAMEL-14467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14467: --- Fix Version/s: 3.x > camel-jcache - Dynamically bypass the cache for lookups > --- > > Key: CAMEL-14467 > URL: https://issues.apache.org/jira/browse/CAMEL-14467 > Project: Camel > Issue Type: New Feature > Components: camel-jcache >Affects Versions: 3.0.1 >Reporter: Jens Kleine-Herzbruch >Assignee: Dmitry Volodin >Priority: Major > Fix For: 3.x > > Attachments: bypass.diff > > > Currently, the JCachePolicy can only enabled or disable the cache completely > at startup. > > It would be useful to be able to enable or disable caching per request, > though. This change adds a new property "bypassExpression". If this > expression is set and returns true, the cache is ignored for lookup, the > underlying route is executed as normal, and the returned value is inserted in > the cache for future lookups. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-10652) Create a component for Kafka-Stream
[ https://issues.apache.org/jira/browse/CAMEL-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070887#comment-17070887 ] Dmitry Volodin edited comment on CAMEL-10652 at 3/30/20, 11:11 AM: --- Hi [~hien711] you can choose another issue marked with gsoc2020 label or ask community for selecting some another issues for you. We have a set of free issues for selection. was (Author: dmvolod): Hi [~hien711] you can choose another issue marked with gsoc2020 label or ask community for selecting some another issues for you. > Create a component for Kafka-Stream > --- > > Key: CAMEL-10652 > URL: https://issues.apache.org/jira/browse/CAMEL-10652 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: Andrea Cosentino >Priority: Minor > Labels: gsoc2020 > Fix For: Future > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-10652) Create a component for Kafka-Stream
[ https://issues.apache.org/jira/browse/CAMEL-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070887#comment-17070887 ] Dmitry Volodin commented on CAMEL-10652: Hi [~hien711] you can choose another issue marked with gsoc2020 label or ask community for selecting some another issues for you. > Create a component for Kafka-Stream > --- > > Key: CAMEL-10652 > URL: https://issues.apache.org/jira/browse/CAMEL-10652 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: Andrea Cosentino >Priority: Minor > Labels: gsoc2020 > Fix For: Future > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14793) Decrease default consumer request timeout to 30s
[ https://issues.apache.org/jira/browse/CAMEL-14793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14793: --- Fix Version/s: 3.2.0 > Decrease default consumer request timeout to 30s > - > > Key: CAMEL-14793 > URL: https://issues.apache.org/jira/browse/CAMEL-14793 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Affects Versions: 3.1.0 >Reporter: Marat Gubaidullin >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Camel-kafka default Producer parameter request.timeout.ms = 305000, however > in Kafka documentation it is 3. Also it was changed in > https://issues.apache.org/jira/browse/KAFKA-7050 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-13530) Upgrade Milo to 0.3.8
[ https://issues.apache.org/jira/browse/CAMEL-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-13530: -- Assignee: Dmitry Volodin > Upgrade Milo to 0.3.8 > - > > Key: CAMEL-13530 > URL: https://issues.apache.org/jira/browse/CAMEL-13530 > Project: Camel > Issue Type: Task > Components: camel-milo >Reporter: Andrea Cosentino >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.2.0 > > > Some breaking changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14495) OPC UA Client samplingInterval parameter seems not take any effect
[
https://issues.apache.org/jira/browse/CAMEL-14495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin resolved CAMEL-14495.
Resolution: Fixed
> OPC UA Client samplingInterval parameter seems not take any effect
> --
>
> Key: CAMEL-14495
> URL: https://issues.apache.org/jira/browse/CAMEL-14495
> Project: Camel
> Issue Type: Improvement
> Components: camel-milo
>Affects Versions: 2.25.0
>Reporter: Hobbert
>Assignee: Dmitry Volodin
>Priority: Minor
> Labels: help-wanted
> Fix For: 3.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When I set the *samplingInterval* parameter on a Milo OPC UA Client route,
> the interval not changes on the real OPC application! Remains 1000 mili
> seconds even after configuring!! Can anyone confirm that??
> Heres my route
> http://camel.apache.org/schema/spring; >
>
> uri="milo-client:tcp://192.168.0.2:4840?samplingInterval=50=RAW(ns=4;i=12)"/>
>
> ${in.body}
>
>
>
> Thanks
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-14467) camel-jcache - Dynamically bypass the cache for lookups
[ https://issues.apache.org/jira/browse/CAMEL-14467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-14467: -- Assignee: Dmitry Volodin > camel-jcache - Dynamically bypass the cache for lookups > --- > > Key: CAMEL-14467 > URL: https://issues.apache.org/jira/browse/CAMEL-14467 > Project: Camel > Issue Type: New Feature > Components: camel-jcache >Affects Versions: 3.0.1 >Reporter: Jens Kleine-Herzbruch >Assignee: Dmitry Volodin >Priority: Major > Attachments: bypass.diff > > > Currently, the JCachePolicy can only enabled or disable the cache completely > at startup. > > It would be useful to be able to enable or disable caching per request, > though. This change adds a new property "bypassExpression". If this > expression is set and returns true, the cache is ignored for lookup, the > underlying route is executed as normal, and the returned value is inserted in > the cache for future lookups. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14512) Allow reference to custom ClientInterceptor or Producer to customize authentication
[
https://issues.apache.org/jira/browse/CAMEL-14512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-14512:
---
Component/s: (was: camel-spring-boot-starters)
(was: camel-spring-boot)
(was: camel-spring)
> Allow reference to custom ClientInterceptor or Producer to customize
> authentication
> ---
>
> Key: CAMEL-14512
> URL: https://issues.apache.org/jira/browse/CAMEL-14512
> Project: Camel
> Issue Type: Wish
> Components: camel-grpc
> Environment: * Java 11
> * SpringBoot 2.1.5.RELEASE
> * Camel 3.0.0-M2
> * Camel-Grpc-Starter 3.0.0-M2
>Reporter: Philipp
>Priority: Minor
>
> The [GRPC
> component|https://github.com/apache/camel/blob/master/components/camel-grpc/src/main/docs/grpc-component.adoc]
> does currently not offer the possibility to intercept the connection
> establishment against the gRPC server out of the box.
> This prevents to add custom authentication to the channel/connection setup.
> And since the gRPC component does not offer this custom implementation out of
> the box, the currently only solution is:
> * Implement a custom {{GrpcComponent}}
> * Implement a custom {{GrpcEndpoint}}
> * Implement a custom {{GrpcProducer}} or {{DefaultAsyncProducer}}
> ** Override the {{doStart()}} method
> ** Instantiate the {{Channel}}
> ** Add a custom {{ClientInterceptor}} and override the {{interceptCall()}}
> method
> ** Add headers to the metadata of the prepared call
> Even though there are the properties {{authenticationType=JWT}},
> {{jwtSecret}}, {{jwtIssuer}} and so on, these arguments only allow constant
> strings. Therefore, no retrieval of OAuth tokens (for example) during the
> runtime is possible, but everything would have to be hard-coded.
> The [AHC-WS
> component|https://github.com/apache/camel/blob/master/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc]
> in contrast, offers this possibility by implementing a custom
> {{AsyncHttpClient}} and pointing to it via the
> {{camel.component.ahc-ws.client}} property in the {{application.yml}}. Like
> this, the connection setup of the websocket can easily be intercepted by
> overriding {{DefaultAsyncHttpClient.prepareGet()}} where OAuth tokens (for
> example) can be passed and added to the handshake.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-14512) Allow reference to custom ClientInterceptor or Producer to customize authentication
[
https://issues.apache.org/jira/browse/CAMEL-14512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-14512:
--
Assignee: Dmitry Volodin
> Allow reference to custom ClientInterceptor or Producer to customize
> authentication
> ---
>
> Key: CAMEL-14512
> URL: https://issues.apache.org/jira/browse/CAMEL-14512
> Project: Camel
> Issue Type: Wish
> Components: camel-grpc
> Environment: * Java 11
> * SpringBoot 2.1.5.RELEASE
> * Camel 3.0.0-M2
> * Camel-Grpc-Starter 3.0.0-M2
>Reporter: Philipp
>Assignee: Dmitry Volodin
>Priority: Minor
>
> The [GRPC
> component|https://github.com/apache/camel/blob/master/components/camel-grpc/src/main/docs/grpc-component.adoc]
> does currently not offer the possibility to intercept the connection
> establishment against the gRPC server out of the box.
> This prevents to add custom authentication to the channel/connection setup.
> And since the gRPC component does not offer this custom implementation out of
> the box, the currently only solution is:
> * Implement a custom {{GrpcComponent}}
> * Implement a custom {{GrpcEndpoint}}
> * Implement a custom {{GrpcProducer}} or {{DefaultAsyncProducer}}
> ** Override the {{doStart()}} method
> ** Instantiate the {{Channel}}
> ** Add a custom {{ClientInterceptor}} and override the {{interceptCall()}}
> method
> ** Add headers to the metadata of the prepared call
> Even though there are the properties {{authenticationType=JWT}},
> {{jwtSecret}}, {{jwtIssuer}} and so on, these arguments only allow constant
> strings. Therefore, no retrieval of OAuth tokens (for example) during the
> runtime is possible, but everything would have to be hard-coded.
> The [AHC-WS
> component|https://github.com/apache/camel/blob/master/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc]
> in contrast, offers this possibility by implementing a custom
> {{AsyncHttpClient}} and pointing to it via the
> {{camel.component.ahc-ws.client}} property in the {{application.yml}}. Like
> this, the connection setup of the websocket can easily be intercepted by
> overriding {{DefaultAsyncHttpClient.prepareGet()}} where OAuth tokens (for
> example) can be passed and added to the handshake.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-13530) Upgrade Milo to 0.3.8
[ https://issues.apache.org/jira/browse/CAMEL-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-13530: --- Summary: Upgrade Milo to 0.3.8 (was: Upgrade Milo to 0.3.0) > Upgrade Milo to 0.3.8 > - > > Key: CAMEL-13530 > URL: https://issues.apache.org/jira/browse/CAMEL-13530 > Project: Camel > Issue Type: Task > Components: camel-milo >Reporter: Andrea Cosentino >Priority: Minor > Fix For: 3.x > > > Some breaking changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14495) OPC UA Client samplingInterval parameter seems not take any effect
[
https://issues.apache.org/jira/browse/CAMEL-14495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-14495:
--
Assignee: Dmitry Volodin
> OPC UA Client samplingInterval parameter seems not take any effect
> --
>
> Key: CAMEL-14495
> URL: https://issues.apache.org/jira/browse/CAMEL-14495
> Project: Camel
> Issue Type: Improvement
> Components: camel-milo
>Affects Versions: 2.25.0
>Reporter: Hobbert
>Assignee: Dmitry Volodin
>Priority: Minor
> Labels: help-wanted
> Fix For: 3.2.0
>
>
> When I set the *samplingInterval* parameter on a Milo OPC UA Client route,
> the interval not changes on the real OPC application! Remains 1000 mili
> seconds even after configuring!! Can anyone confirm that??
> Heres my route
> http://camel.apache.org/schema/spring; >
>
> uri="milo-client:tcp://192.168.0.2:4840?samplingInterval=50=RAW(ns=4;i=12)"/>
>
> ${in.body}
>
>
>
> Thanks
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14495) OPC UA Client samplingInterval parameter seems not take any effect
[
https://issues.apache.org/jira/browse/CAMEL-14495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066533#comment-17066533
]
Dmitry Volodin commented on CAMEL-14495:
[~evergreen] do you need to configure hardcoded requestedPublishingInterval?
samplingInterval and requestedPublishingInterval are different parameters:
[https://stackoverflow.com/questions/41183394/what-does-the-requestedpublishinginterval-in-milo-mean]
> OPC UA Client samplingInterval parameter seems not take any effect
> --
>
> Key: CAMEL-14495
> URL: https://issues.apache.org/jira/browse/CAMEL-14495
> Project: Camel
> Issue Type: Improvement
> Components: camel-milo
>Affects Versions: 2.25.0
>Reporter: Hobbert
>Priority: Minor
> Labels: help-wanted
> Fix For: 3.2.0
>
>
> When I set the *samplingInterval* parameter on a Milo OPC UA Client route,
> the interval not changes on the real OPC application! Remains 1000 mili
> seconds even after configuring!! Can anyone confirm that??
> Heres my route
> http://camel.apache.org/schema/spring; >
>
> uri="milo-client:tcp://192.168.0.2:4840?samplingInterval=50=RAW(ns=4;i=12)"/>
>
> ${in.body}
>
>
>
> Thanks
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-12863) Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
[
https://issues.apache.org/jira/browse/CAMEL-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin resolved CAMEL-12863.
Resolution: Fixed
> Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
>
>
> Key: CAMEL-12863
> URL: https://issues.apache.org/jira/browse/CAMEL-12863
> Project: Camel
> Issue Type: New Feature
> Components: tooling
>Affects Versions: 2.22.1
>Reporter: Jochen Cordes
>Assignee: Dmitry Volodin
>Priority: Major
> Fix For: 3.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> For dealing with "legacy" date-formats (like -MM-dd) add the ability to
> pass configOptions to the swagger-codegen-plugin, f.e. dateLibrary.
>
> ...
> legacy
> ...
>
>
> The default date-object generated by the swagger-codegen-plugin (LocalTime)
> leads to parsing errors ("Expected BEGIN_OBJECT but was STRING"). Another
> option would be to enhance the GsonDataFormat
> (org.apache.camel.component.gson.GsonDataFormat), so that it also allows for
> registering TypeAdapters
> [https://www.javadoc.io/doc/com.google.code.gson/gson/latest/com.google.gson/com/google/gson/TypeAdapter.html]).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-12863) Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
[
https://issues.apache.org/jira/browse/CAMEL-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-12863:
---
Labels: (was: help-wanted)
> Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
>
>
> Key: CAMEL-12863
> URL: https://issues.apache.org/jira/browse/CAMEL-12863
> Project: Camel
> Issue Type: New Feature
> Components: tooling
>Affects Versions: 2.22.1
>Reporter: Jochen Cordes
>Assignee: Dmitry Volodin
>Priority: Major
> Fix For: 3.2.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For dealing with "legacy" date-formats (like -MM-dd) add the ability to
> pass configOptions to the swagger-codegen-plugin, f.e. dateLibrary.
>
> ...
> legacy
> ...
>
>
> The default date-object generated by the swagger-codegen-plugin (LocalTime)
> leads to parsing errors ("Expected BEGIN_OBJECT but was STRING"). Another
> option would be to enhance the GsonDataFormat
> (org.apache.camel.component.gson.GsonDataFormat), so that it also allows for
> registering TypeAdapters
> [https://www.javadoc.io/doc/com.google.code.gson/gson/latest/com.google.gson/com/google/gson/TypeAdapter.html]).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-12863) Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
[
https://issues.apache.org/jira/browse/CAMEL-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-12863:
---
Fix Version/s: (was: Future)
3.2.0
> Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
>
>
> Key: CAMEL-12863
> URL: https://issues.apache.org/jira/browse/CAMEL-12863
> Project: Camel
> Issue Type: New Feature
> Components: tooling
>Affects Versions: 2.22.1
>Reporter: Jochen Cordes
>Assignee: Dmitry Volodin
>Priority: Major
> Labels: help-wanted
> Fix For: 3.2.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For dealing with "legacy" date-formats (like -MM-dd) add the ability to
> pass configOptions to the swagger-codegen-plugin, f.e. dateLibrary.
>
> ...
> legacy
> ...
>
>
> The default date-object generated by the swagger-codegen-plugin (LocalTime)
> leads to parsing errors ("Expected BEGIN_OBJECT but was STRING"). Another
> option would be to enhance the GsonDataFormat
> (org.apache.camel.component.gson.GsonDataFormat), so that it also allows for
> registering TypeAdapters
> [https://www.javadoc.io/doc/com.google.code.gson/gson/latest/com.google.gson/com/google/gson/TypeAdapter.html]).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-12863) Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
[
https://issues.apache.org/jira/browse/CAMEL-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066462#comment-17066462
]
Dmitry Volodin commented on CAMEL-12863:
Yes, configOptions is part of the swagger-codegen-maven-plugin.
[https://github.com/swagger-api/swagger-codegen/tree/master/modules/swagger-codegen-maven-plugin]
> Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
>
>
> Key: CAMEL-12863
> URL: https://issues.apache.org/jira/browse/CAMEL-12863
> Project: Camel
> Issue Type: New Feature
> Components: tooling
>Affects Versions: 2.22.1
>Reporter: Jochen Cordes
>Assignee: Dmitry Volodin
>Priority: Major
> Labels: help-wanted
> Fix For: Future
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For dealing with "legacy" date-formats (like -MM-dd) add the ability to
> pass configOptions to the swagger-codegen-plugin, f.e. dateLibrary.
>
> ...
> legacy
> ...
>
>
> The default date-object generated by the swagger-codegen-plugin (LocalTime)
> leads to parsing errors ("Expected BEGIN_OBJECT but was STRING"). Another
> option would be to enhance the GsonDataFormat
> (org.apache.camel.component.gson.GsonDataFormat), so that it also allows for
> registering TypeAdapters
> [https://www.javadoc.io/doc/com.google.code.gson/gson/latest/com.google.gson/com/google/gson/TypeAdapter.html]).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14781) Support page missing toolbar breadcrumbs
[ https://issues.apache.org/jira/browse/CAMEL-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14781: --- Component/s: (was: camel-web) website > Support page missing toolbar breadcrumbs > > > Key: CAMEL-14781 > URL: https://issues.apache.org/jira/browse/CAMEL-14781 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Solange Iyubu >Priority: Major > > While navigating on apache website I saw pages that don't have toolbars > breadcrumps such as support page from community. I am going to work on it -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-12863) Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
[
https://issues.apache.org/jira/browse/CAMEL-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-12863:
---
Description:
For dealing with "legacy" date-formats (like -MM-dd) add the ability to
pass configOptions to the swagger-codegen-plugin, f.e. dateLibrary.
...
legacy
...
The default date-object generated by the swagger-codegen-plugin (LocalTime)
leads to parsing errors ("Expected BEGIN_OBJECT but was STRING"). Another
option would be to enhance the GsonDataFormat
(org.apache.camel.component.gson.GsonDataFormat), so that it also allows for
registering TypeAdapters
[https://www.javadoc.io/doc/com.google.code.gson/gson/latest/com.google.gson/com/google/gson/TypeAdapter.html]).
was:
For dealing with "legcy" date-formats (like -MM-dd) add the ability to pass
configOptions to the swagger-codegen-plugin, f.e. dateLibrary.
...
legacy
...
The default date-object generated by the swagger-codegen-plugin (LocalTime)
leads to parsing errors ("Expected BEGIN_OBJECT but was STRING"). Another
option would be to enhance the GsonDataFormat
(org.apache.camel.component.gson.GsonDataFormat), so that it also allows for
registering TypeAdapters
(https://google.github.io/gson/apidocs/com/google/gson/TypeAdapter.html).
> Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
>
>
> Key: CAMEL-12863
> URL: https://issues.apache.org/jira/browse/CAMEL-12863
> Project: Camel
> Issue Type: New Feature
> Components: tooling
>Affects Versions: 2.22.1
>Reporter: Jochen Cordes
>Priority: Major
> Labels: help-wanted
> Fix For: Future
>
>
> For dealing with "legacy" date-formats (like -MM-dd) add the ability to
> pass configOptions to the swagger-codegen-plugin, f.e. dateLibrary.
>
> ...
> legacy
> ...
>
>
> The default date-object generated by the swagger-codegen-plugin (LocalTime)
> leads to parsing errors ("Expected BEGIN_OBJECT but was STRING"). Another
> option would be to enhance the GsonDataFormat
> (org.apache.camel.component.gson.GsonDataFormat), so that it also allows for
> registering TypeAdapters
> [https://www.javadoc.io/doc/com.google.code.gson/gson/latest/com.google.gson/com/google/gson/TypeAdapter.html]).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-12863) Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
[
https://issues.apache.org/jira/browse/CAMEL-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-12863:
--
Assignee: Dmitry Volodin
> Add configOptions to camel-restdsl-swagger-plugin for swagger-codegen-plugin
>
>
> Key: CAMEL-12863
> URL: https://issues.apache.org/jira/browse/CAMEL-12863
> Project: Camel
> Issue Type: New Feature
> Components: tooling
>Affects Versions: 2.22.1
>Reporter: Jochen Cordes
>Assignee: Dmitry Volodin
>Priority: Major
> Labels: help-wanted
> Fix For: Future
>
>
> For dealing with "legacy" date-formats (like -MM-dd) add the ability to
> pass configOptions to the swagger-codegen-plugin, f.e. dateLibrary.
>
> ...
> legacy
> ...
>
>
> The default date-object generated by the swagger-codegen-plugin (LocalTime)
> leads to parsing errors ("Expected BEGIN_OBJECT but was STRING"). Another
> option would be to enhance the GsonDataFormat
> (org.apache.camel.component.gson.GsonDataFormat), so that it also allows for
> registering TypeAdapters
> [https://www.javadoc.io/doc/com.google.code.gson/gson/latest/com.google.gson/com/google/gson/TypeAdapter.html]).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14710) Camel-Jcache: Tests are failing
[ https://issues.apache.org/jira/browse/CAMEL-14710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin resolved CAMEL-14710. Resolution: Fixed > Camel-Jcache: Tests are failing > --- > > Key: CAMEL-14710 > URL: https://issues.apache.org/jira/browse/CAMEL-14710 > Project: Camel > Issue Type: Test > Components: camel-jcache >Reporter: Andrea Cosentino >Assignee: Dmitry Volodin >Priority: Major > Fix For: 3.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > > It should be related to hazelcast update. [~Madhawa Gunasekara], please have > a look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14710) Camel-Jcache: Tests are failing
[ https://issues.apache.org/jira/browse/CAMEL-14710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-14710: -- Assignee: Dmitry Volodin > Camel-Jcache: Tests are failing > --- > > Key: CAMEL-14710 > URL: https://issues.apache.org/jira/browse/CAMEL-14710 > Project: Camel > Issue Type: Test > Components: camel-jcache >Reporter: Andrea Cosentino >Assignee: Dmitry Volodin >Priority: Major > Fix For: 3.2.0 > > > It should be related to hazelcast update. [~Madhawa Gunasekara], please have > a look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14417) [camel-jslt] Create spring-boot starter for camel-jslt
[ https://issues.apache.org/jira/browse/CAMEL-14417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14417: --- Issue Type: New Feature (was: Bug) > [camel-jslt] Create spring-boot starter for camel-jslt > -- > > Key: CAMEL-14417 > URL: https://issues.apache.org/jira/browse/CAMEL-14417 > Project: Camel > Issue Type: New Feature > Components: camel-jolt >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Component using JSLT transformation was created - > https://issues.apache.org/jira/browse/CAMEL-13699 > Starter has to be created also (once 3.1.0 version of component is released) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14687) Cannot build camel behind firewall
[
https://issues.apache.org/jira/browse/CAMEL-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064194#comment-17064194
]
Dmitry Volodin commented on CAMEL-14687:
Hello, [~tcunning] !
You are welcome to provide PR
[https://github.com/apache/camel/blob/master/CONTRIBUTING.md]
> Cannot build camel behind firewall
> --
>
> Key: CAMEL-14687
> URL: https://issues.apache.org/jira/browse/CAMEL-14687
> Project: Camel
> Issue Type: Improvement
> Components: build system
>Reporter: Thomas Cunningham
>Priority: Major
> Fix For: 3.x
>
>
> I'm having issues building camel behind a firewall because of
> camel-javadoc-plugin. It seems to be mostly copied from
> maven-javadoc-plugin 3.1.0 or 3.1.1, which stripped out proxy_user/password
> support https://issues.apache.org/jira/browse/MJAVADOC-565 - it's an issue
> because of the , and I end up with an error when javadoc tries to
> fetch them :
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.1.1:jar (attach-javadocs) on
> project camel-util: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - Error fetching URL:
> http://download.oracle.com/javase/7/docs/api/
> [ERROR] javadoc: error - Error fetching URL:
> http://download.oracle.com/javaee/7/api/
>
> I'd like to contribute a patch to set
> ${camel.javadoc.isOffline} in the
> maven/camel-javadoc-plugin, so that camel can be built behind a firewall.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14751) add icons and rearrange the camel front page functionality section
[ https://issues.apache.org/jira/browse/CAMEL-14751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14751: --- Component/s: (was: camel-web) website > add icons and rearrange the camel front page functionality section > -- > > Key: CAMEL-14751 > URL: https://issues.apache.org/jira/browse/CAMEL-14751 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.0.0 >Reporter: gunkev >Priority: Trivial > Labels: improvement > Attachments: Screenshot from 2020-03-18 20-25-25.png > > Original Estimate: 1h > Remaining Estimate: 1h > > I order to make he front page of camel website look more appeal and > understandable some illustrations or icons should be added in order to > reflect the subject matter of the functionalities section -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14743) camel-elytron: refactor component to use new SPI interface from camel-undertow
[ https://issues.apache.org/jira/browse/CAMEL-14743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14743: --- Issue Type: Task (was: Bug) > camel-elytron: refactor component to use new SPI interface from camel-undertow > -- > > Key: CAMEL-14743 > URL: https://issues.apache.org/jira/browse/CAMEL-14743 > Project: Camel > Issue Type: Task > Components: camel-undertow >Affects Versions: 3.2.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > > As a part of the fix of https://issues.apache.org/jira/browse/CAMEL-14208 > there is a new SPI APi for security providers. Component camel-elytron should > be refactored to use that api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14748) Unmarshal ZIP w/ error handling in Camel 3.x
[
https://issues.apache.org/jira/browse/CAMEL-14748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063206#comment-17063206
]
Dmitry Volodin commented on CAMEL-14748:
Oh, [~omarsmak] looks like corrupted zip file is any non-zip file, for example
text, data, etc.
> Unmarshal ZIP w/ error handling in Camel 3.x
>
>
> Key: CAMEL-14748
> URL: https://issues.apache.org/jira/browse/CAMEL-14748
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> I've following route
>
>
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;>
> http://camel.apache.org/schema/blueprint;>
>
>
>
>
>
>
>
>
>
> {code}
>
> When I'm sending a corrupted ZIP file to this route I'd expect a Camel
> runtime error. This won't happen, I'm only getting an empty body.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14746) camel-rest-swagger java.lang.IllegalArgumentException when Swagger specification don't have "scheme" object and get this specification by "file;" resource
[
https://issues.apache.org/jira/browse/CAMEL-14746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin resolved CAMEL-14746.
Resolution: Fixed
{color:#172b4d}Yes, the supported components (http, netty, etc.) are able to
set auth options.{color}
{color:#172b4d}Please ask questions on gitter channel first. {color}
> camel-rest-swagger java.lang.IllegalArgumentException when Swagger
> specification don't have "scheme" object and get this specification by
> "file;" resource
> --
>
> Key: CAMEL-14746
> URL: https://issues.apache.org/jira/browse/CAMEL-14746
> Project: Camel
> Issue Type: Bug
> Components: camel-rest-swagger
>Affects Versions: 2.25.0
>Reporter: Mikhail Lukyanov
>Assignee: Dmitry Volodin
>Priority: Minor
> Fix For: 3.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *camelContext*
>
> __
> _http://www.springframework.org/schema/beans"_
> _xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"_
> _xsi:schemaLocation="http://camel.apache.org/schema/spring
> [http://camel.apache.org/schema/spring/camel-spring.xsd]
> [http://www.springframework.org/schema/beans]
> [http://www.springframework.org/schema/beans/spring-beans.xsd];>_
> _ xmlns="http://camel.apache.org/schema/spring; >_
> __
> __
> _ uri="swagger*:file*:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json#downloadUsingGET"/>_
> __
> __
> __
> _ class="org.apache.camel.component.rest.swagger.RestSwaggerComponent">_
> __
> __
> __
>
> *Swagger.json*
>
> _{_
> _"swagger": "2.0",_
> _"info": {_
> _"description": "Api Documentation",_
> _"version": "1.0",_
> _"title": "Api Documentation",_
> _"termsOfService": "urn:tos",_
> _"contact": {},_
> _"license": {_
> _"name": "Apache 2.0",_
> _"url": "http://www.apache.org/licenses/LICENSE-2.0"_
> _}_
> _},_
> _"host": "localhost:8182",_
> _"basePath": "/manager",_
> _"tags": [_
> _{_
> _"name": "Logs",_
> _"description": "API for logs"_
> _}_
> _],_
> _"paths": {_
> _"/api/log/download": {_
> _"get": {_
> _"tags": [_
> _"Работа с логами"_
> _],_
> _"summary": "Export",_
> _"operationId": "downloadUsingGET",_
> _"produces": [_
> _"*/*"_
> _],_
> _"responses": {_
> _"200": {_
> _"description": "OK"_
> _},_
> _"401": {_
> _"description": "Unauthorized"_
> _},_
> _"403": {_
> "description": "Forbidden"
> },
> "404":
> { "description": "Not Found" }
> },
> "deprecated": false
> }
> }
> }
> }
>
> *Error*
>
> {color:#de350b}Caused by: org.apache.camel.FailedToCreateProducerException:
> Failed to create Producer for endpoint:
> swagger://[file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET|file:///C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET].
> Reason: java.lang.IllegalArgumentException: The endpoint is not of type:
> class org.apache.camel.component.http.HttpEndpoint but is:
> org.apache.camel.component.file.FileEndpointCaused by:
> org.apache.camel.FailedToCreateProducerException: Failed to create Producer
> for endpoint:
> swagger://[file:/C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET|file:///C:/Users/wunsh/IdeaProjects/camel/components/camel-rest-swagger/src/test/resources/swagger1.json%23downloadUsingGET].
> Reason: java.lang.IllegalArgumentException: The endpoint is not of type:
> class org.apache.camel.component.http.HttpEndpoint but is:
> org.apache.camel.component.file.FileEndpoint{color}
>
> {color:#172b4d}When I get the same swagger specification through the resource
> "http:" everything is ok{color}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
