[jira] [Commented] (CAMEL-17518) BeanInstantiationException for CamelContext
[ https://issues.apache.org/jira/browse/CAMEL-17518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479156#comment-17479156 ] Andrea Cosentino commented on CAMEL-17518: -- Please: * Report what is the Camel version you're using * Report the route you're using * Report configuration * Maybe provide a little reproducer or at least a snippet of the code you're using > BeanInstantiationException for CamelContext > --- > > Key: CAMEL-17518 > URL: https://issues.apache.org/jira/browse/CAMEL-17518 > Project: Camel > Issue Type: Bug > Environment: Spring boot, gradle >Reporter: Bhamini Bhat >Priority: Major > > Error creating bean with name 'camelContext': Instantiation of bean failed; > nested exception is org.springframework.beans.BeanInstantiationException: > Failed to instantiate [org.apache.camel.CamelContext]: Specified class is an > interface. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17519) Make Camel MainSupport internalBeforeStart method protected
James Netherton created CAMEL-17519: --- Summary: Make Camel MainSupport internalBeforeStart method protected Key: CAMEL-17519 URL: https://issues.apache.org/jira/browse/CAMEL-17519 Project: Camel Issue Type: Improvement Components: camel-main Affects Versions: 3.14.0 Reporter: James Netherton Assignee: James Netherton Fix For: 3.14.1, 3.15.0 It would enable some main configuration options to be picked up by Camel Quarkus. See issue reported here: https://github.com/apache/camel-quarkus/issues/3394 Maybe also split the logic in internalBeforeStart into protected methods so that stuff can also be overridden if needed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17520) Cannot use square brackets in HTTP parameters
Pasquale Congiusti created CAMEL-17520:
--
Summary: Cannot use square brackets in HTTP parameters
Key: CAMEL-17520
URL: https://issues.apache.org/jira/browse/CAMEL-17520
Project: Camel
Issue Type: Bug
Affects Versions: 3.12.0
Reporter: Pasquale Congiusti
It was reported on mailing list, there is some problem when trying to use
square brackets as part of the URI params. I've run some expertiment with the
RAW() function, but this is only applied to the value parameter, not the
variable name (ie, _param=RAW(value)_).
As a reproducer, we may run this route (ie, via Camel K):
{code}
// camel-k: language=java
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.model.rest.RestParamType;
import org.apache.camel.Exchange;
public class Test extends RouteBuilder {
@Override
public void configure() throws Exception {
rest()
.get("/hello")
.param().name("test[bogus]").type(RestParamType.query).defaultValue("false").description("Just
for testing").endParam()
.to("direct:hello");
from("direct:hello")
.setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
.setBody().simple("${headers.test[bogus]}");
// Write your routes here, for example:
from("timer:java?period=3000")
.to("http://localhost:8080/hello?test[bogus]=true";)
.log("${body}");
}
}
{code}
It will end up with error:
{code}
[1] Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
resolve endpoint: http://localhost:8080/hello?test%5Bbogus%5D=true due to:
Error binding property (test[bogus]=true) with name: test[bogus] on bean:
http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
[1] at
org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:963)
[1] at
org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:845)
[1] at
org.apache.camel.support.CamelContextHelper.resolveEndpoint(CamelContextHelper.java:123)
[1] at
org.apache.camel.reifier.SendReifier.resolveEndpoint(SendReifier.java:43)
[1] at
org.apache.camel.reifier.SendReifier.createProcessor(SendReifier.java:36)
[1] at
org.apache.camel.reifier.ProcessorReifier.makeProcessor(ProcessorReifier.java:838)
[1] at
org.apache.camel.reifier.ProcessorReifier.addRoutes(ProcessorReifier.java:579)
[1] at
org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:236)
[1] ... 31 more
[1] Caused by: org.apache.camel.PropertyBindingException: Error binding
property (test[bogus]=true) with name: test[bogus] on bean:
http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
[1] at
org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:476)
[1] at
org.apache.camel.support.PropertyBindingSupport.doBuildPropertyOgnlPath(PropertyBindingSupport.java:326)
[1] at
org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:210)
[1] at
org.apache.camel.support.PropertyBindingSupport.access$100(PropertyBindingSupport.java:88)
[1] at
org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:1789)
[1] at
org.apache.camel.support.DefaultEndpoint.setProperties(DefaultEndpoint.java:413)
[1] at
org.apache.camel.support.DefaultEndpoint.configureProperties(DefaultEndpoint.java:388)
[1] at
org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:425)
[1] at
org.apache.camel.component.http.HttpComponent.createEndpoint(HttpComponent.java:377)
[1] at
org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:171)
[1] at
org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:929)
[1] ... 38 more
[1] Caused by: java.lang.IllegalArgumentException: Cannot set property:
test[bogus] as a Map because target bean has no setter method for the Map
[1] at
org.apache.camel.support.PropertyBindingSupport.setPropertyCollectionViaReflection(PropertyBindingSupport.java:523)
[1] at
org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:453)
[1] ... 48 more
{code}
Trying to apply the RAW() function on the parameter (ie,
?RAW(test[bogus])=true) does not convert the parameter, but create a new one
called _RAW(test[bogus])_
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17520) Cannot use square brackets in HTTP parameters
[
https://issues.apache.org/jira/browse/CAMEL-17520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17520:
Component/s: camel-core
> Cannot use square brackets in HTTP parameters
> -
>
> Key: CAMEL-17520
> URL: https://issues.apache.org/jira/browse/CAMEL-17520
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 3.12.0
>Reporter: Pasquale Congiusti
>Priority: Minor
>
> It was reported on mailing list, there is some problem when trying to use
> square brackets as part of the URI params. I've run some expertiment with the
> RAW() function, but this is only applied to the value parameter, not the
> variable name (ie, _param=RAW(value)_).
> As a reproducer, we may run this route (ie, via Camel K):
> {code}
> // camel-k: language=java
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.model.rest.RestParamType;
> import org.apache.camel.Exchange;
> public class Test extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> rest()
> .get("/hello")
>
> .param().name("test[bogus]").type(RestParamType.query).defaultValue("false").description("Just
> for testing").endParam()
> .to("direct:hello");
> from("direct:hello")
> .setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
> .setBody().simple("${headers.test[bogus]}");
> // Write your routes here, for example:
> from("timer:java?period=3000")
> .to("http://localhost:8080/hello?test[bogus]=true";)
> .log("${body}");
> }
> }
> {code}
> It will end up with error:
> {code}
> [1] Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint: http://localhost:8080/hello?test%5Bbogus%5D=true due to:
> Error binding property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:963)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:845)
> [1] at
> org.apache.camel.support.CamelContextHelper.resolveEndpoint(CamelContextHelper.java:123)
> [1] at
> org.apache.camel.reifier.SendReifier.resolveEndpoint(SendReifier.java:43)
> [1] at
> org.apache.camel.reifier.SendReifier.createProcessor(SendReifier.java:36)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.makeProcessor(ProcessorReifier.java:838)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.addRoutes(ProcessorReifier.java:579)
> [1] at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:236)
> [1] ... 31 more
> [1] Caused by: org.apache.camel.PropertyBindingException: Error binding
> property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:476)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBuildPropertyOgnlPath(PropertyBindingSupport.java:326)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:210)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.access$100(PropertyBindingSupport.java:88)
> [1] at
> org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:1789)
> [1] at
> org.apache.camel.support.DefaultEndpoint.setProperties(DefaultEndpoint.java:413)
> [1] at
> org.apache.camel.support.DefaultEndpoint.configureProperties(DefaultEndpoint.java:388)
> [1] at
> org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:425)
> [1] at
> org.apache.camel.component.http.HttpComponent.createEndpoint(HttpComponent.java:377)
> [1] at
> org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:171)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:929)
> [1] ... 38 more
> [1] Caused by: java.lang.IllegalArgumentException: Cannot set property:
> test[bogus] as a Map because target bean has no setter method for the Map
> [1] at
> org.apache.camel.support.PropertyBindingSupport.setPropertyCollectionViaReflection(PropertyBindingSupport.java:523)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:453)
> [1] ... 48 more
> {code}
> Trying to apply the RAW() function on the parameter (ie,
> ?RAW(test[bogus])=true) does not convert the parameter, but create a new one
> called _RAW(test[bogus])_
--
This message was sent by Atlassian
[jira] [Updated] (CAMEL-17520) Cannot use square brackets in HTTP parameters
[
https://issues.apache.org/jira/browse/CAMEL-17520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17520:
Priority: Minor (was: Major)
> Cannot use square brackets in HTTP parameters
> -
>
> Key: CAMEL-17520
> URL: https://issues.apache.org/jira/browse/CAMEL-17520
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.12.0
>Reporter: Pasquale Congiusti
>Priority: Minor
>
> It was reported on mailing list, there is some problem when trying to use
> square brackets as part of the URI params. I've run some expertiment with the
> RAW() function, but this is only applied to the value parameter, not the
> variable name (ie, _param=RAW(value)_).
> As a reproducer, we may run this route (ie, via Camel K):
> {code}
> // camel-k: language=java
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.model.rest.RestParamType;
> import org.apache.camel.Exchange;
> public class Test extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> rest()
> .get("/hello")
>
> .param().name("test[bogus]").type(RestParamType.query).defaultValue("false").description("Just
> for testing").endParam()
> .to("direct:hello");
> from("direct:hello")
> .setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
> .setBody().simple("${headers.test[bogus]}");
> // Write your routes here, for example:
> from("timer:java?period=3000")
> .to("http://localhost:8080/hello?test[bogus]=true";)
> .log("${body}");
> }
> }
> {code}
> It will end up with error:
> {code}
> [1] Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint: http://localhost:8080/hello?test%5Bbogus%5D=true due to:
> Error binding property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:963)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:845)
> [1] at
> org.apache.camel.support.CamelContextHelper.resolveEndpoint(CamelContextHelper.java:123)
> [1] at
> org.apache.camel.reifier.SendReifier.resolveEndpoint(SendReifier.java:43)
> [1] at
> org.apache.camel.reifier.SendReifier.createProcessor(SendReifier.java:36)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.makeProcessor(ProcessorReifier.java:838)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.addRoutes(ProcessorReifier.java:579)
> [1] at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:236)
> [1] ... 31 more
> [1] Caused by: org.apache.camel.PropertyBindingException: Error binding
> property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:476)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBuildPropertyOgnlPath(PropertyBindingSupport.java:326)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:210)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.access$100(PropertyBindingSupport.java:88)
> [1] at
> org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:1789)
> [1] at
> org.apache.camel.support.DefaultEndpoint.setProperties(DefaultEndpoint.java:413)
> [1] at
> org.apache.camel.support.DefaultEndpoint.configureProperties(DefaultEndpoint.java:388)
> [1] at
> org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:425)
> [1] at
> org.apache.camel.component.http.HttpComponent.createEndpoint(HttpComponent.java:377)
> [1] at
> org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:171)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:929)
> [1] ... 38 more
> [1] Caused by: java.lang.IllegalArgumentException: Cannot set property:
> test[bogus] as a Map because target bean has no setter method for the Map
> [1] at
> org.apache.camel.support.PropertyBindingSupport.setPropertyCollectionViaReflection(PropertyBindingSupport.java:523)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:453)
> [1] ... 48 more
> {code}
> Trying to apply the RAW() function on the parameter (ie,
> ?RAW(test[bogus])=true) does not convert the parameter, but create a new one
> called _RAW(test[bogus])_
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17521) camel-http - httpClient parameters are not filtered out
Claus Ibsen created CAMEL-17521: --- Summary: camel-http - httpClient parameters are not filtered out Key: CAMEL-17521 URL: https://issues.apache.org/jira/browse/CAMEL-17521 Project: Camel Issue Type: Bug Components: camel-http Affects Versions: 3.14.0, 3.11.5 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.14.1, 3.15.0, 3.11.6 When using httpClient.SocketTimeout=55 then that gets included in the HTTP GET url that the client is sending to the server. Reported on chat at https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/http.20query.20parameter/near/268668471 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17521) camel-http - httpClient parameters are not filtered out
[ https://issues.apache.org/jira/browse/CAMEL-17521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479285#comment-17479285 ] Claus Ibsen commented on CAMEL-17521: - Okay false alarm, cannot reproduce this. > camel-http - httpClient parameters are not filtered out > --- > > Key: CAMEL-17521 > URL: https://issues.apache.org/jira/browse/CAMEL-17521 > Project: Camel > Issue Type: Bug > Components: camel-http >Affects Versions: 3.11.5, 3.14.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.14.1, 3.15.0, 3.11.6 > > > When using httpClient.SocketTimeout=55 then that gets included in the > HTTP GET url that the client is sending to the server. > Reported on chat at > https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/http.20query.20parameter/near/268668471 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17391) org.elasticsearch.client.sniff.Sniffer : error while sniffing nodes
[
https://issues.apache.org/jira/browse/CAMEL-17391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-17391.
-
Resolution: Fixed
> org.elasticsearch.client.sniff.Sniffer : error while sniffing nodes
> ---
>
> Key: CAMEL-17391
> URL: https://issues.apache.org/jira/browse/CAMEL-17391
> Project: Camel
> Issue Type: Task
> Components: camel-elasticsearch-rest
>Affects Versions: 3.14.0
> Environment: OS: Windows 8 / Windows 10
> Java: OpenJDK 11 (OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.10+9))
> Camel: 3.14.0 (Same behavior on 3.11.X)
>Reporter: Raymond
>Priority: Minor
> Fix For: 3.15.0
>
>
> I have a Spring Boot 2.5.8 application that run Camel. When I add the
> following dependency
>
> {{org.apache.camelcamel-elasticsearch-rest3.14.0}}
> Then on startup of the application I get the following error:
> 2021-12-24 16:09:34.018 ERROR 3532 --- [nt_sniffer[T#1]]
> org.elasticsearch.client.sniff.Sniffer : error while sniffing
> nodes
> java.net.ConnectException: Timeout connecting to [localhost/127.0.0.1:9200]
> at
> org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:880)
> at
> org.elasticsearch.client.RestClient.performRequest(RestClient.java:283)
> at
> org.elasticsearch.client.RestClient.performRequest(RestClient.java:270)
> at
> org.elasticsearch.client.sniff.ElasticsearchNodesSniffer.sniff(ElasticsearchNodesSniffer.java:105)
> at org.elasticsearch.client.sniff.Sniffer.sniff(Sniffer.java:208)
> at org.elasticsearch.client.sniff.Sniffer$Task.run(Sniffer.java:138)
> at org.elasticsearch.client.sniff.Sniffer$1.run(Sniffer.java:81)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecuto
> r.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.net.ConnectException: Timeout connecting to
> [localhost/127.0.0.1:9200]
> at
> org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:169)
> at
> org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:632)
> at
> org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:
> 898)
> at
> org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:198)
> at
> org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:2
> 13)
> at
> org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:158
> )
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:351)
> at
> org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager
> .java:221)
> at
> org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
> ... 1 common frames omitted
> After removing the error I not there anymore. In the documentation the
> component option "{*}enableSniffer{*}" is false by default. It seems that
> somehow it is set to true. (But seems not by my code).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17503) camel-ahc-ws - Unable to reconnect to Server after server reboot
[ https://issues.apache.org/jira/browse/CAMEL-17503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17503: Fix Version/s: 3.14.1 3.15.0 3.11.6 > camel-ahc-ws - Unable to reconnect to Server after server reboot > > > Key: CAMEL-17503 > URL: https://issues.apache.org/jira/browse/CAMEL-17503 > Project: Camel > Issue Type: Bug > Components: camel-ahc-ws >Affects Versions: 3.12.0 >Reporter: CG Poh >Priority: Minor > Fix For: 3.14.1, 3.15.0, 3.11.6 > > > Camel AHC-WS client unable to reconnect to Server whenever the server > reboots. The reConnect() in WsEndpoint.java get called but is not calling the > connect() function. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17391) org.elasticsearch.client.sniff.Sniffer : error while sniffing nodes
[
https://issues.apache.org/jira/browse/CAMEL-17391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17391:
Issue Type: Task (was: Bug)
> org.elasticsearch.client.sniff.Sniffer : error while sniffing nodes
> ---
>
> Key: CAMEL-17391
> URL: https://issues.apache.org/jira/browse/CAMEL-17391
> Project: Camel
> Issue Type: Task
> Components: camel-elasticsearch-rest
>Affects Versions: 3.14.0
> Environment: OS: Windows 8 / Windows 10
> Java: OpenJDK 11 (OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.10+9))
> Camel: 3.14.0 (Same behavior on 3.11.X)
>Reporter: Raymond
>Priority: Minor
> Fix For: 3.15.0
>
>
> I have a Spring Boot 2.5.8 application that run Camel. When I add the
> following dependency
>
> {{org.apache.camelcamel-elasticsearch-rest3.14.0}}
> Then on startup of the application I get the following error:
> 2021-12-24 16:09:34.018 ERROR 3532 --- [nt_sniffer[T#1]]
> org.elasticsearch.client.sniff.Sniffer : error while sniffing
> nodes
> java.net.ConnectException: Timeout connecting to [localhost/127.0.0.1:9200]
> at
> org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:880)
> at
> org.elasticsearch.client.RestClient.performRequest(RestClient.java:283)
> at
> org.elasticsearch.client.RestClient.performRequest(RestClient.java:270)
> at
> org.elasticsearch.client.sniff.ElasticsearchNodesSniffer.sniff(ElasticsearchNodesSniffer.java:105)
> at org.elasticsearch.client.sniff.Sniffer.sniff(Sniffer.java:208)
> at org.elasticsearch.client.sniff.Sniffer$Task.run(Sniffer.java:138)
> at org.elasticsearch.client.sniff.Sniffer$1.run(Sniffer.java:81)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecuto
> r.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.net.ConnectException: Timeout connecting to
> [localhost/127.0.0.1:9200]
> at
> org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:169)
> at
> org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:632)
> at
> org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:
> 898)
> at
> org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:198)
> at
> org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:2
> 13)
> at
> org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:158
> )
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:351)
> at
> org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager
> .java:221)
> at
> org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
> ... 1 common frames omitted
> After removing the error I not there anymore. In the documentation the
> component option "{*}enableSniffer{*}" is false by default. It seems that
> somehow it is set to true. (But seems not by my code).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (CAMEL-17519) Make Camel MainSupport internalBeforeStart method protected
[ https://issues.apache.org/jira/browse/CAMEL-17519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton resolved CAMEL-17519. - Fix Version/s: (was: 3.14.1) Resolution: Fixed > Make Camel MainSupport internalBeforeStart method protected > --- > > Key: CAMEL-17519 > URL: https://issues.apache.org/jira/browse/CAMEL-17519 > Project: Camel > Issue Type: Improvement > Components: camel-main >Affects Versions: 3.14.0 >Reporter: James Netherton >Assignee: James Netherton >Priority: Minor > Fix For: 3.15.0 > > > It would enable some main configuration options to be picked up by Camel > Quarkus. See issue reported here: > https://github.com/apache/camel-quarkus/issues/3394 > Maybe also split the logic in internalBeforeStart into protected methods so > that stuff can also be overridden if needed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17161) Support for Azure Copy Blob Operation in Camel component
[ https://issues.apache.org/jira/browse/CAMEL-17161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479314#comment-17479314 ] Reneesh commented on CAMEL-17161: - Code samples for this feature can be found in the below link [https://camel.apache.org/components/3.14.x/azure-storage-blob-component.html] > Support for Azure Copy Blob Operation in Camel component > > > Key: CAMEL-17161 > URL: https://issues.apache.org/jira/browse/CAMEL-17161 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Reneesh >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.14.0 > > > *Problem:* > For copying a blob file from one Azure blob storage to another Azure blob > storage, we have to get the blob file and upload it to another location using > the camel route. In some cases we have to convert the body to byte[] in order > to avoid the Stream error included below and I believe this would result in > causing memory issues while handling large size files based on this approach. > Stack overflow Reference : > [https://stackoverflow.com/questions/69767784/apache-camel-azure-blob-to-azure-blob-route-file-transfer-feasibility] > > *Proposal :* > Microsoft Azure supports copy blob operation which is useful to copy blobs > from one storage to another without loading the file content. As per the > latest version of azure blob component of Camel, its not available in the > supported BlobOperation. > Raising this ticket to include this COPY BLOB operation in the subsequent > release from your side. > Ref : [https://docs.microsoft.com/en-us/rest/api/storageservices/copy-blob] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17522) camel-spring-boot - Upgrade to spring boot 2.5.9
Claus Ibsen created CAMEL-17522: --- Summary: camel-spring-boot - Upgrade to spring boot 2.5.9 Key: CAMEL-17522 URL: https://issues.apache.org/jira/browse/CAMEL-17522 Project: Camel Issue Type: Dependency upgrade Components: camel-spring-boot Affects Versions: 3.11.5 Reporter: Claus Ibsen Fix For: 3.11.6 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17503) camel-ahc-ws - Unable to reconnect to Server after server reboot
[ https://issues.apache.org/jira/browse/CAMEL-17503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17503. - Resolution: Fixed Thanks for the PR > camel-ahc-ws - Unable to reconnect to Server after server reboot > > > Key: CAMEL-17503 > URL: https://issues.apache.org/jira/browse/CAMEL-17503 > Project: Camel > Issue Type: Bug > Components: camel-ahc-ws >Affects Versions: 3.12.0 >Reporter: CG Poh >Priority: Minor > Fix For: 3.14.1, 3.15.0, 3.11.6 > > > Camel AHC-WS client unable to reconnect to Server whenever the server > reboots. The reConnect() in WsEndpoint.java get called but is not calling the > connect() function. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17512) Make tracing SpanDecorators work better with toD
[ https://issues.apache.org/jira/browse/CAMEL-17512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479442#comment-17479442 ] Claus Ibsen commented on CAMEL-17512: - Cannot reproduce this, when using toD and a JMS endpoint I see the resolved URI, eg jms:queue:blah > Make tracing SpanDecorators work better with toD > > > Key: CAMEL-17512 > URL: https://issues.apache.org/jira/browse/CAMEL-17512 > Project: Camel > Issue Type: Improvement > Components: camel-opentelemetry, camel-tracing >Reporter: James Netherton >Priority: Minor > > Originally reported here: > https://github.com/apache/camel-quarkus/issues/3461 > If toD is used in routes, then the tracing SpanDecorator does not resolve the > placeholder values (not sure if it's possible?). So when the recorded spans > are viewed in a UI, it looks bit weird and confusing because it's not obvious > where the trace events originated from. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17520) Cannot use square brackets in HTTP parameters
[
https://issues.apache.org/jira/browse/CAMEL-17520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-17520:
---
Assignee: Claus Ibsen
> Cannot use square brackets in HTTP parameters
> -
>
> Key: CAMEL-17520
> URL: https://issues.apache.org/jira/browse/CAMEL-17520
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 3.12.0
>Reporter: Pasquale Congiusti
>Assignee: Claus Ibsen
>Priority: Minor
>
> It was reported on mailing list, there is some problem when trying to use
> square brackets as part of the URI params. I've run some expertiment with the
> RAW() function, but this is only applied to the value parameter, not the
> variable name (ie, _param=RAW(value)_).
> As a reproducer, we may run this route (ie, via Camel K):
> {code}
> // camel-k: language=java
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.model.rest.RestParamType;
> import org.apache.camel.Exchange;
> public class Test extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> rest()
> .get("/hello")
>
> .param().name("test[bogus]").type(RestParamType.query).defaultValue("false").description("Just
> for testing").endParam()
> .to("direct:hello");
> from("direct:hello")
> .setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
> .setBody().simple("${headers.test[bogus]}");
> // Write your routes here, for example:
> from("timer:java?period=3000")
> .to("http://localhost:8080/hello?test[bogus]=true";)
> .log("${body}");
> }
> }
> {code}
> It will end up with error:
> {code}
> [1] Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint: http://localhost:8080/hello?test%5Bbogus%5D=true due to:
> Error binding property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:963)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:845)
> [1] at
> org.apache.camel.support.CamelContextHelper.resolveEndpoint(CamelContextHelper.java:123)
> [1] at
> org.apache.camel.reifier.SendReifier.resolveEndpoint(SendReifier.java:43)
> [1] at
> org.apache.camel.reifier.SendReifier.createProcessor(SendReifier.java:36)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.makeProcessor(ProcessorReifier.java:838)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.addRoutes(ProcessorReifier.java:579)
> [1] at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:236)
> [1] ... 31 more
> [1] Caused by: org.apache.camel.PropertyBindingException: Error binding
> property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:476)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBuildPropertyOgnlPath(PropertyBindingSupport.java:326)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:210)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.access$100(PropertyBindingSupport.java:88)
> [1] at
> org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:1789)
> [1] at
> org.apache.camel.support.DefaultEndpoint.setProperties(DefaultEndpoint.java:413)
> [1] at
> org.apache.camel.support.DefaultEndpoint.configureProperties(DefaultEndpoint.java:388)
> [1] at
> org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:425)
> [1] at
> org.apache.camel.component.http.HttpComponent.createEndpoint(HttpComponent.java:377)
> [1] at
> org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:171)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:929)
> [1] ... 38 more
> [1] Caused by: java.lang.IllegalArgumentException: Cannot set property:
> test[bogus] as a Map because target bean has no setter method for the Map
> [1] at
> org.apache.camel.support.PropertyBindingSupport.setPropertyCollectionViaReflection(PropertyBindingSupport.java:523)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:453)
> [1] ... 48 more
> {code}
> Trying to apply the RAW() function on the parameter (ie,
> ?RAW(test[bogus])=true) does not convert the parameter, but create a new one
> called _RAW(test[bogus])_
[jira] [Updated] (CAMEL-17520) Cannot use square brackets in HTTP parameters
[
https://issues.apache.org/jira/browse/CAMEL-17520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17520:
Fix Version/s: 3.14.1
3.15.0
> Cannot use square brackets in HTTP parameters
> -
>
> Key: CAMEL-17520
> URL: https://issues.apache.org/jira/browse/CAMEL-17520
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 3.12.0
>Reporter: Pasquale Congiusti
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.14.1, 3.15.0
>
>
> It was reported on mailing list, there is some problem when trying to use
> square brackets as part of the URI params. I've run some expertiment with the
> RAW() function, but this is only applied to the value parameter, not the
> variable name (ie, _param=RAW(value)_).
> As a reproducer, we may run this route (ie, via Camel K):
> {code}
> // camel-k: language=java
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.model.rest.RestParamType;
> import org.apache.camel.Exchange;
> public class Test extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> rest()
> .get("/hello")
>
> .param().name("test[bogus]").type(RestParamType.query).defaultValue("false").description("Just
> for testing").endParam()
> .to("direct:hello");
> from("direct:hello")
> .setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
> .setBody().simple("${headers.test[bogus]}");
> // Write your routes here, for example:
> from("timer:java?period=3000")
> .to("http://localhost:8080/hello?test[bogus]=true";)
> .log("${body}");
> }
> }
> {code}
> It will end up with error:
> {code}
> [1] Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint: http://localhost:8080/hello?test%5Bbogus%5D=true due to:
> Error binding property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:963)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:845)
> [1] at
> org.apache.camel.support.CamelContextHelper.resolveEndpoint(CamelContextHelper.java:123)
> [1] at
> org.apache.camel.reifier.SendReifier.resolveEndpoint(SendReifier.java:43)
> [1] at
> org.apache.camel.reifier.SendReifier.createProcessor(SendReifier.java:36)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.makeProcessor(ProcessorReifier.java:838)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.addRoutes(ProcessorReifier.java:579)
> [1] at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:236)
> [1] ... 31 more
> [1] Caused by: org.apache.camel.PropertyBindingException: Error binding
> property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:476)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBuildPropertyOgnlPath(PropertyBindingSupport.java:326)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:210)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.access$100(PropertyBindingSupport.java:88)
> [1] at
> org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:1789)
> [1] at
> org.apache.camel.support.DefaultEndpoint.setProperties(DefaultEndpoint.java:413)
> [1] at
> org.apache.camel.support.DefaultEndpoint.configureProperties(DefaultEndpoint.java:388)
> [1] at
> org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:425)
> [1] at
> org.apache.camel.component.http.HttpComponent.createEndpoint(HttpComponent.java:377)
> [1] at
> org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:171)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:929)
> [1] ... 38 more
> [1] Caused by: java.lang.IllegalArgumentException: Cannot set property:
> test[bogus] as a Map because target bean has no setter method for the Map
> [1] at
> org.apache.camel.support.PropertyBindingSupport.setPropertyCollectionViaReflection(PropertyBindingSupport.java:523)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:453)
> [1] ... 48 more
> {code}
> Trying to apply the RAW() function on the parameter (ie,
> ?RAW(test[bogus])=true) does not convert the par
[jira] [Commented] (CAMEL-17520) Cannot use square brackets in HTTP parameters
[
https://issues.apache.org/jira/browse/CAMEL-17520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479457#comment-17479457
]
Claus Ibsen commented on CAMEL-17520:
-
Yeah so its because that filter parameter is not a known option on the endpoint
- what we need to make sure in the core was that we know its lenient properties
on HTTP endpoints and therefore should ignore that there is not a option called
test on the endpoint.
I have a pending fix
> Cannot use square brackets in HTTP parameters
> -
>
> Key: CAMEL-17520
> URL: https://issues.apache.org/jira/browse/CAMEL-17520
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 3.12.0
>Reporter: Pasquale Congiusti
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.14.1, 3.15.0
>
>
> It was reported on mailing list, there is some problem when trying to use
> square brackets as part of the URI params. I've run some expertiment with the
> RAW() function, but this is only applied to the value parameter, not the
> variable name (ie, _param=RAW(value)_).
> As a reproducer, we may run this route (ie, via Camel K):
> {code}
> // camel-k: language=java
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.model.rest.RestParamType;
> import org.apache.camel.Exchange;
> public class Test extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> rest()
> .get("/hello")
>
> .param().name("test[bogus]").type(RestParamType.query).defaultValue("false").description("Just
> for testing").endParam()
> .to("direct:hello");
> from("direct:hello")
> .setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
> .setBody().simple("${headers.test[bogus]}");
> // Write your routes here, for example:
> from("timer:java?period=3000")
> .to("http://localhost:8080/hello?test[bogus]=true";)
> .log("${body}");
> }
> }
> {code}
> It will end up with error:
> {code}
> [1] Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint: http://localhost:8080/hello?test%5Bbogus%5D=true due to:
> Error binding property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:963)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:845)
> [1] at
> org.apache.camel.support.CamelContextHelper.resolveEndpoint(CamelContextHelper.java:123)
> [1] at
> org.apache.camel.reifier.SendReifier.resolveEndpoint(SendReifier.java:43)
> [1] at
> org.apache.camel.reifier.SendReifier.createProcessor(SendReifier.java:36)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.makeProcessor(ProcessorReifier.java:838)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.addRoutes(ProcessorReifier.java:579)
> [1] at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:236)
> [1] ... 31 more
> [1] Caused by: org.apache.camel.PropertyBindingException: Error binding
> property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:476)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBuildPropertyOgnlPath(PropertyBindingSupport.java:326)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:210)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.access$100(PropertyBindingSupport.java:88)
> [1] at
> org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:1789)
> [1] at
> org.apache.camel.support.DefaultEndpoint.setProperties(DefaultEndpoint.java:413)
> [1] at
> org.apache.camel.support.DefaultEndpoint.configureProperties(DefaultEndpoint.java:388)
> [1] at
> org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:425)
> [1] at
> org.apache.camel.component.http.HttpComponent.createEndpoint(HttpComponent.java:377)
> [1] at
> org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:171)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:929)
> [1] ... 38 more
> [1] Caused by: java.lang.IllegalArgumentException: Cannot set property:
> test[bogus] as a Map because target bean has no setter method for the Map
> [1] at
> org.apache.camel.support.PropertyBindingSupport.setPropertyCollectionViaRefle
[jira] [Updated] (CAMEL-17519) Make Camel MainSupport internalBeforeStart method protected
[ https://issues.apache.org/jira/browse/CAMEL-17519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton updated CAMEL-17519: Fix Version/s: 3.14.1 3.11.6 > Make Camel MainSupport internalBeforeStart method protected > --- > > Key: CAMEL-17519 > URL: https://issues.apache.org/jira/browse/CAMEL-17519 > Project: Camel > Issue Type: Improvement > Components: camel-main >Affects Versions: 3.14.0 >Reporter: James Netherton >Assignee: James Netherton >Priority: Minor > Fix For: 3.14.1, 3.15.0, 3.11.6 > > > It would enable some main configuration options to be picked up by Camel > Quarkus. See issue reported here: > https://github.com/apache/camel-quarkus/issues/3394 > Maybe also split the logic in internalBeforeStart into protected methods so > that stuff can also be overridden if needed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17512) Make tracing SpanDecorators work better with toD
[ https://issues.apache.org/jira/browse/CAMEL-17512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479467#comment-17479467 ] James Netherton commented on CAMEL-17512: - I'll check on the Camel Quarkus side and try to craft a unit test to replicate if it is broken. > Make tracing SpanDecorators work better with toD > > > Key: CAMEL-17512 > URL: https://issues.apache.org/jira/browse/CAMEL-17512 > Project: Camel > Issue Type: Improvement > Components: camel-opentelemetry, camel-tracing >Reporter: James Netherton >Priority: Minor > > Originally reported here: > https://github.com/apache/camel-quarkus/issues/3461 > If toD is used in routes, then the tracing SpanDecorator does not resolve the > placeholder values (not sure if it's possible?). So when the recorded spans > are viewed in a UI, it looks bit weird and confusing because it's not obvious > where the trace events originated from. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17523) camel-spring-boot-examples：rest-jpa is broken
Freeman Yue Fang created CAMEL-17523: Summary: camel-spring-boot-examples：rest-jpa is broken Key: CAMEL-17523 URL: https://issues.apache.org/jira/browse/CAMEL-17523 Project: Camel Issue Type: Bug Components: examples Reporter: Freeman Yue Fang Fix For: 3.15.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17523) camel-spring-boot-examples：rest-jpa is broken
[ https://issues.apache.org/jira/browse/CAMEL-17523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang reassigned CAMEL-17523: Assignee: Freeman Yue Fang > camel-spring-boot-examples：rest-jpa is broken > -- > > Key: CAMEL-17523 > URL: https://issues.apache.org/jira/browse/CAMEL-17523 > Project: Camel > Issue Type: Bug > Components: examples >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.15.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17523) camel-spring-boot-examples：rest-jpa is broken
[ https://issues.apache.org/jira/browse/CAMEL-17523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479496#comment-17479496 ] Freeman Yue Fang commented on CAMEL-17523: -- This [PR|https://github.com/apache/camel-spring-boot-examples/pull/45] fixed this up > camel-spring-boot-examples：rest-jpa is broken > -- > > Key: CAMEL-17523 > URL: https://issues.apache.org/jira/browse/CAMEL-17523 > Project: Camel > Issue Type: Bug > Components: examples >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.15.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17524) Camel schematron
Ryan Yeats created CAMEL-17524: -- Summary: Camel schematron Key: CAMEL-17524 URL: https://issues.apache.org/jira/browse/CAMEL-17524 Project: Camel Issue Type: Bug Reporter: Ryan Yeats -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17524) Camel loading of resources using ClassResolver API doesn't work in OSGi enviroments
[ https://issues.apache.org/jira/browse/CAMEL-17524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Yeats updated CAMEL-17524: --- Affects Version/s: 3.14.0 Description: https://issues.apache.org/jira/browse/CAMEL-17116 changed how resources were loaded in several components the problem being that now they don't use the classloader of the class making the resource calls in OSGi environments. Its a simple change to call the method loadResourceAsStream(String name, ClassLoader loader) and passing in the calling classes class loader instead of loadResourceAsStream(String name). Summary: Camel loading of resources using ClassResolver API doesn't work in OSGi enviroments (was: Camel schematron) > Camel loading of resources using ClassResolver API doesn't work in OSGi > enviroments > --- > > Key: CAMEL-17524 > URL: https://issues.apache.org/jira/browse/CAMEL-17524 > Project: Camel > Issue Type: Bug >Affects Versions: 3.14.0 >Reporter: Ryan Yeats >Priority: Major > > https://issues.apache.org/jira/browse/CAMEL-17116 changed how resources were > loaded in several components the problem being that now they don't use the > classloader of the class making the resource calls in OSGi environments. Its > a simple change to call the method loadResourceAsStream(String name, > ClassLoader loader) and passing in the calling classes class loader instead > of loadResourceAsStream(String name). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17523) camel-spring-boot-examples：rest-jpa is broken
[ https://issues.apache.org/jira/browse/CAMEL-17523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang resolved CAMEL-17523. -- Resolution: Fixed > camel-spring-boot-examples：rest-jpa is broken > -- > > Key: CAMEL-17523 > URL: https://issues.apache.org/jira/browse/CAMEL-17523 > Project: Camel > Issue Type: Bug > Components: examples >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.15.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (CAMEL-17491) camel-openapi-java - Operation paths are incorrect if contextPath is set
[
https://issues.apache.org/jira/browse/CAMEL-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-17491 started by Karen Lease.
---
> camel-openapi-java - Operation paths are incorrect if contextPath is set
>
>
> Key: CAMEL-17491
> URL: https://issues.apache.org/jira/browse/CAMEL-17491
> Project: Camel
> Issue Type: Bug
> Components: camel-openapi-java
>Affects Versions: 3.13.0, 3.14.0
>Reporter: James Netherton
>Assignee: Karen Lease
>Priority: Major
> Fix For: 3.15.0
>
>
> Consider this REST configuration:
> {code}
> restConfiguration()
> .host("localhost")
> .apiHost("localhost")
> .contextPath("/api")
> .port(8080)
> .apiContextPath("/api-docs");
> rest("/service")
> .get("/testing").description("Test Service")
> .outType(String.class)
> .route().setBody().constant("Hello World");
> {code}
> The 'paths' object in the generated OpenAPI document is incorrect. It should
> not have the '/api' context path prefix.
> {code}
> {
> "openapi" : "3.0.2",
> "info" : { },
> "servers" : [ {
> "url" : "/api"
> } ],
> "paths" : {
> "/api/service/testing" : {
> "get" : {
> "tags" : [ "/service" ],
> "responses" : {
> "200" : { }
> },
> "operationId" : "verb1",
> "summary" : "Test Service"
> }
> }
> },
> "components" : { },
> "tags" : [ {
> "name" : "/service"
> } ]
> }
> {code}
> The OpenAPI spec states:
> "Unless specified otherwise, all properties that are URLs MAY be relative
> references as defined by RFC3986. Relative references are resolved using the
> URLs defined in the Server Object as a Base URI.".
> If you try to execute the service in the Swagger UI, then it tries to hit
> http://localhost:8080/api/api/service/testing (duplicate /api/api in the
> path).
> Maybe the code we had before CAMEL-17063 was implemented was more correct?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17491) camel-openapi-java - Operation paths are incorrect if contextPath is set
[
https://issues.apache.org/jira/browse/CAMEL-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479605#comment-17479605
]
Karen Lease commented on CAMEL-17491:
-
I created a PR for the change in camel-openapi-java. For the moment I didn't
change the springdoc component.
> camel-openapi-java - Operation paths are incorrect if contextPath is set
>
>
> Key: CAMEL-17491
> URL: https://issues.apache.org/jira/browse/CAMEL-17491
> Project: Camel
> Issue Type: Bug
> Components: camel-openapi-java
>Affects Versions: 3.13.0, 3.14.0
>Reporter: James Netherton
>Assignee: Karen Lease
>Priority: Major
> Fix For: 3.15.0
>
>
> Consider this REST configuration:
> {code}
> restConfiguration()
> .host("localhost")
> .apiHost("localhost")
> .contextPath("/api")
> .port(8080)
> .apiContextPath("/api-docs");
> rest("/service")
> .get("/testing").description("Test Service")
> .outType(String.class)
> .route().setBody().constant("Hello World");
> {code}
> The 'paths' object in the generated OpenAPI document is incorrect. It should
> not have the '/api' context path prefix.
> {code}
> {
> "openapi" : "3.0.2",
> "info" : { },
> "servers" : [ {
> "url" : "/api"
> } ],
> "paths" : {
> "/api/service/testing" : {
> "get" : {
> "tags" : [ "/service" ],
> "responses" : {
> "200" : { }
> },
> "operationId" : "verb1",
> "summary" : "Test Service"
> }
> }
> },
> "components" : { },
> "tags" : [ {
> "name" : "/service"
> } ]
> }
> {code}
> The OpenAPI spec states:
> "Unless specified otherwise, all properties that are URLs MAY be relative
> references as defined by RFC3986. Relative references are resolved using the
> URLs defined in the Server Object as a Base URI.".
> If you try to execute the service in the Swagger UI, then it tries to hit
> http://localhost:8080/api/api/service/testing (duplicate /api/api in the
> path).
> Maybe the code we had before CAMEL-17063 was implemented was more correct?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17525) camel-stub - StubEndpoint should be lenient properties
Claus Ibsen created CAMEL-17525: --- Summary: camel-stub - StubEndpoint should be lenient properties Key: CAMEL-17525 URL: https://issues.apache.org/jira/browse/CAMEL-17525 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Fix For: 3.15.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17520) Cannot use square brackets in HTTP parameters
[
https://issues.apache.org/jira/browse/CAMEL-17520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-17520.
-
Resolution: Fixed
> Cannot use square brackets in HTTP parameters
> -
>
> Key: CAMEL-17520
> URL: https://issues.apache.org/jira/browse/CAMEL-17520
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 3.12.0
>Reporter: Pasquale Congiusti
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.14.1, 3.15.0
>
>
> It was reported on mailing list, there is some problem when trying to use
> square brackets as part of the URI params. I've run some expertiment with the
> RAW() function, but this is only applied to the value parameter, not the
> variable name (ie, _param=RAW(value)_).
> As a reproducer, we may run this route (ie, via Camel K):
> {code}
> // camel-k: language=java
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.model.rest.RestParamType;
> import org.apache.camel.Exchange;
> public class Test extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> rest()
> .get("/hello")
>
> .param().name("test[bogus]").type(RestParamType.query).defaultValue("false").description("Just
> for testing").endParam()
> .to("direct:hello");
> from("direct:hello")
> .setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
> .setBody().simple("${headers.test[bogus]}");
> // Write your routes here, for example:
> from("timer:java?period=3000")
> .to("http://localhost:8080/hello?test[bogus]=true";)
> .log("${body}");
> }
> }
> {code}
> It will end up with error:
> {code}
> [1] Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint: http://localhost:8080/hello?test%5Bbogus%5D=true due to:
> Error binding property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:963)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:845)
> [1] at
> org.apache.camel.support.CamelContextHelper.resolveEndpoint(CamelContextHelper.java:123)
> [1] at
> org.apache.camel.reifier.SendReifier.resolveEndpoint(SendReifier.java:43)
> [1] at
> org.apache.camel.reifier.SendReifier.createProcessor(SendReifier.java:36)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.makeProcessor(ProcessorReifier.java:838)
> [1] at
> org.apache.camel.reifier.ProcessorReifier.addRoutes(ProcessorReifier.java:579)
> [1] at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:236)
> [1] ... 31 more
> [1] Caused by: org.apache.camel.PropertyBindingException: Error binding
> property (test[bogus]=true) with name: test[bogus] on bean:
> http://localhost:8080/hello?test%5Bbogus%5D=true with value: true
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:476)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBuildPropertyOgnlPath(PropertyBindingSupport.java:326)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doBindProperties(PropertyBindingSupport.java:210)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.access$100(PropertyBindingSupport.java:88)
> [1] at
> org.apache.camel.support.PropertyBindingSupport$Builder.bind(PropertyBindingSupport.java:1789)
> [1] at
> org.apache.camel.support.DefaultEndpoint.setProperties(DefaultEndpoint.java:413)
> [1] at
> org.apache.camel.support.DefaultEndpoint.configureProperties(DefaultEndpoint.java:388)
> [1] at
> org.apache.camel.support.DefaultComponent.setProperties(DefaultComponent.java:425)
> [1] at
> org.apache.camel.component.http.HttpComponent.createEndpoint(HttpComponent.java:377)
> [1] at
> org.apache.camel.support.DefaultComponent.createEndpoint(DefaultComponent.java:171)
> [1] at
> org.apache.camel.impl.engine.AbstractCamelContext.doGetEndpoint(AbstractCamelContext.java:929)
> [1] ... 38 more
> [1] Caused by: java.lang.IllegalArgumentException: Cannot set property:
> test[bogus] as a Map because target bean has no setter method for the Map
> [1] at
> org.apache.camel.support.PropertyBindingSupport.setPropertyCollectionViaReflection(PropertyBindingSupport.java:523)
> [1] at
> org.apache.camel.support.PropertyBindingSupport.doSetPropertyValue(PropertyBindingSupport.java:453)
> [1] ... 48 more
> {code}
> Trying to apply the RAW() function on the parameter (ie,
> ?RAW(test[bogus])=true) does not convert the parameter, but create a new one
[jira] [Commented] (CAMEL-17512) Make tracing SpanDecorators work better with toD
[ https://issues.apache.org/jira/browse/CAMEL-17512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479622#comment-17479622 ] Claus Ibsen commented on CAMEL-17512: - Thanks, I was just doing a basic unit test in camel-opentelemetry, but debugging then I noticed that both the pre and post span had the resolved endpoint from toD > Make tracing SpanDecorators work better with toD > > > Key: CAMEL-17512 > URL: https://issues.apache.org/jira/browse/CAMEL-17512 > Project: Camel > Issue Type: Improvement > Components: camel-opentelemetry, camel-tracing >Reporter: James Netherton >Priority: Minor > > Originally reported here: > https://github.com/apache/camel-quarkus/issues/3461 > If toD is used in routes, then the tracing SpanDecorator does not resolve the > placeholder values (not sure if it's possible?). So when the recorded spans > are viewed in a UI, it looks bit weird and confusing because it's not obvious > where the trace events originated from. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17526) camel-fhir: the serverUrl configuration on camel-fhir endpoint shouldn't be ignored
Freeman Yue Fang created CAMEL-17526: Summary: camel-fhir: the serverUrl configuration on camel-fhir endpoint shouldn't be ignored Key: CAMEL-17526 URL: https://issues.apache.org/jira/browse/CAMEL-17526 Project: Camel Issue Type: Bug Components: camel-fhir Reporter: Freeman Yue Fang Currently it always uses the serverUrl configration from camel-fhir component level, if it's null from component level, then even we configure it correctly on the endpoint level, it is still ignored. Our current ITests don't catch this error because always set serverUrl on the camel-fhir component AbstractFhirTestSupport -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17526) camel-fhir: the serverUrl configuration on camel-fhir endpoint shouldn't be ignored
[ https://issues.apache.org/jira/browse/CAMEL-17526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang reassigned CAMEL-17526: Assignee: Freeman Yue Fang > camel-fhir: the serverUrl configuration on camel-fhir endpoint shouldn't be > ignored > --- > > Key: CAMEL-17526 > URL: https://issues.apache.org/jira/browse/CAMEL-17526 > Project: Camel > Issue Type: Bug > Components: camel-fhir >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > > Currently it always uses the serverUrl configration from camel-fhir component > level, if it's null from component level, then even we configure it correctly > on the endpoint level, it is still ignored. > Our current ITests don't catch this error because always set serverUrl on the > camel-fhir component AbstractFhirTestSupport -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17526) camel-fhir: the serverUrl configuration on camel-fhir endpoint shouldn't be ignored
[ https://issues.apache.org/jira/browse/CAMEL-17526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479625#comment-17479625 ] Freeman Yue Fang commented on CAMEL-17526: -- This [PR|https://github.com/apache/camel/pull/6796/commits/9bfac71d49ddb6825af6a68a52270a6280e8086f] addressed it. Also revised FhirCreateIT test to expose this problem > camel-fhir: the serverUrl configuration on camel-fhir endpoint shouldn't be > ignored > --- > > Key: CAMEL-17526 > URL: https://issues.apache.org/jira/browse/CAMEL-17526 > Project: Camel > Issue Type: Bug > Components: camel-fhir >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > > Currently it always uses the serverUrl configration from camel-fhir component > level, if it's null from component level, then even we configure it correctly > on the endpoint level, it is still ignored. > Our current ITests don't catch this error because always set serverUrl on the > camel-fhir component AbstractFhirTestSupport -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17527) Polish the grammar of SyncPropertiesMojo's documentation
skepticoitus interuptus created CAMEL-17527:
---
Summary: Polish the grammar of SyncPropertiesMojo's documentation
Key: CAMEL-17527
URL: https://issues.apache.org/jira/browse/CAMEL-17527
Project: Camel
Issue Type: Improvement
Components: tooling
Reporter: skepticoitus interuptus
Fix For: 3.15.0
The following command:
{code:java}
mvn help:describe -Dplugin=org.apache.camel:sync-properties-maven-plugin
-Ddetail{code}
...displays the following description of _[the
org.apache.camel:sync-properties-maven-plugin|https://bit.ly/syncPropsMojo]_
({_}emphasis mine{_}):
{code:java}
...
Name: Camel :: Maven Plugins :: Sync Properties
Description: Maven plugin to help generating Sync Properties between POMs
...
sync-properties:sync-properties
Description: Copy the properties *in* a POM *in* a different POM for
syncing purpose.
...{code}
Consider Camel's _source-to-sink_ metaphor. Think about how that metaphor
relates the concepts of "{*}_in_{*}" and "{_}out{_}" to the Camel DSL's
"{_}[{*}from{*}()|https://bit.ly/inFrom]{_}"; and
"[_to()_|https://bit.ly/outTo]"; semantics.
Applying those _source-to-sink_ ("{_}out{_}" and "{*}_in_{*}", "{*}_from_{*}"
and "{_}to{_}") semantics to the original description of [_the
SyncPropertiesMojo_|https://bit.ly/syncPropsMojo], and substituting the word
"{*}_in_{*}" with the word it semantically corresponds to in the _Camel
source-to-sink_ metaphor, you would get:
{quote}
_Copy the properties *from* a POM *from* a different POM..._
{quote}
Would it not, therefore, be both more grammatically correct ({_}in the English
language{_}) and clearer *_semantically_* to instead say:
{quote}_Copy the properties *from* a POM *to* a different POM..._
{quote}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17527) Polish the grammar of SyncPropertiesMojo's documentation
[
https://issues.apache.org/jira/browse/CAMEL-17527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479654#comment-17479654
]
Andrea Cosentino commented on CAMEL-17527:
--
It makes totally sense. For this kind of task a PR is enough no need for an
issue.
> Polish the grammar of SyncPropertiesMojo's documentation
>
>
> Key: CAMEL-17527
> URL: https://issues.apache.org/jira/browse/CAMEL-17527
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Reporter: skepticoitus interuptus
>Priority: Minor
> Fix For: 3.15.0
>
>
> The following command:
> {code:java}
> mvn help:describe -Dplugin=org.apache.camel:sync-properties-maven-plugin
> -Ddetail{code}
> ...displays the following description of _[the
> org.apache.camel:sync-properties-maven-plugin|https://bit.ly/syncPropsMojo]_
> ({_}emphasis mine{_}):
> {code:java}
> ...
> Name: Camel :: Maven Plugins :: Sync Properties
> Description: Maven plugin to help generating Sync Properties between POMs
>
> ...
> sync-properties:sync-properties
> Description: Copy the properties *in* a POM *in* a different POM for
> syncing purpose.
> ...{code}
> Consider Camel's _source-to-sink_ metaphor. Think about how that metaphor
> relates the concepts of "{*}_in_{*}" and "{_}out{_}" to the Camel DSL's
> "{_}[{*}from{*}()|https://bit.ly/inFrom]{_}"; and
> "[_to()_|https://bit.ly/outTo]"; semantics.
> Applying those _source-to-sink_ ("{_}out{_}" and "{*}_in_{*}", "{*}_from_{*}"
> and "{_}to{_}") semantics to the original description of [_the
> SyncPropertiesMojo_|https://bit.ly/syncPropsMojo], and substituting the word
> "{*}_in_{*}" with the word it semantically corresponds to in the _Camel
> source-to-sink_ metaphor, you would get:
> {quote}
> _Copy the properties *from* a POM *from* a different POM..._
> {quote}
> Would it not, therefore, be both more grammatically correct ({_}in the
> English language{_}) and clearer *_semantically_* to instead say:
> {quote}_Copy the properties *from* a POM *to* a different POM..._
> {quote}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
