[jira] [Updated] (CAMEL-13159) Rename camel-website to website
[
https://issues.apache.org/jira/browse/CAMEL-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tadayoshi Sato updated CAMEL-13159:
---
Description:
Following the recent directory layout convention such as CAMEL-13040, we should
also move {{camel-website}} to simply {{website}}, so that there are no
directories prefixing {{camel-*}} that appear in the top level of the project.
We need to be careful not to break the generation of the new website with this
change though.
was:
Following the recent directly layout convention such as CAMEL-13040, we should
also move {{camel-website}} to simply {{website}}, so that there are no
directories prefixing {{camel-*}} that appear in the top level of the project.
We need to be careful not to break the generation of the new website with this
change though.
> Rename camel-website to website
> ---
>
> Key: CAMEL-13159
> URL: https://issues.apache.org/jira/browse/CAMEL-13159
> Project: Camel
> Issue Type: Task
> Components: build system, documentation
>Affects Versions: 3.0.0
>Reporter: Tadayoshi Sato
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: 3.0.0
>
>
> Following the recent directory layout convention such as CAMEL-13040, we
> should also move {{camel-website}} to simply {{website}}, so that there are
> no directories prefixing {{camel-*}} that appear in the top level of the
> project.
> We need to be careful not to break the generation of the new website with
> this change though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-13159) Rename camel-website to website
[
https://issues.apache.org/jira/browse/CAMEL-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-13159:
---
Assignee: Zoran Regvart
> Rename camel-website to website
> ---
>
> Key: CAMEL-13159
> URL: https://issues.apache.org/jira/browse/CAMEL-13159
> Project: Camel
> Issue Type: Task
> Components: build system, documentation
>Affects Versions: 3.0.0
>Reporter: Tadayoshi Sato
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: 3.0.0
>
>
> Following the recent directly layout convention such as CAMEL-13040, we
> should also move {{camel-website}} to simply {{website}}, so that there are
> no directories prefixing {{camel-*}} that appear in the top level of the
> project.
> We need to be careful not to break the generation of the new website with
> this change though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13162) Unknown parameter issue on weaving from-with on a REST-DSL route
[
https://issues.apache.org/jira/browse/CAMEL-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13162:
Priority: Minor (was: Critical)
> Unknown parameter issue on weaving from-with on a REST-DSL route
>
>
> Key: CAMEL-13162
> URL: https://issues.apache.org/jira/browse/CAMEL-13162
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.23.0, 2.23.1
>Reporter: Roman Vottner
>Assignee: Dmitry Volodin
>Priority: Minor
>
> On attempting to weave a REST-DSL route and replace the route with something
> different, i.e. {color:#d04437}direct:start{color} seems to be fine in
> regards to the produced debug XML ...
> XML before weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
> uri="rest://post:/heartbeat:/%7Bsender%7D?description=Test+descriptionrouteId=apiHeartbeat"/>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> XML after weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> ... though on sending a message via a producerTemplate will result in the
> following exception:
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> apiHeartbeat: Route(apiHeartbeat)[[From[direct://start?routeId=apiHeartbea...
> because of Failed to resolve endpoint: direct://start?routeId=apiHeartbeat
> due to: Failed to resolve endpoint: direct://start?routeId=apiHeartbeat due
> to: There are 1 parameters that couldn't be set on the endpoint. Check the
> uri if the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[{routeId=apiHeartbeat}]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:217)
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1140)
> at
> org.apache.camel.model.RouteDefinition.adviceWith(RouteDefinition.java:318)
> at
> at.erpel.messaginghub.services.unit.routes.api.CamelRouteAdviceTest.testRouteWeaving(CamelRouteAdviceTest.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:74)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:84)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
> at
> org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
>
[jira] [Updated] (CAMEL-13159) Rename camel-website to website
[
https://issues.apache.org/jira/browse/CAMEL-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13159:
Component/s: documentation
build system
> Rename camel-website to website
> ---
>
> Key: CAMEL-13159
> URL: https://issues.apache.org/jira/browse/CAMEL-13159
> Project: Camel
> Issue Type: Task
> Components: build system, documentation
>Affects Versions: 3.0.0
>Reporter: Tadayoshi Sato
>Priority: Minor
> Fix For: 3.0.0
>
>
> Following the recent directly layout convention such as CAMEL-13040, we
> should also move {{camel-website}} to simply {{website}}, so that there are
> no directories prefixing {{camel-*}} that appear in the top level of the
> project.
> We need to be careful not to break the generation of the new website with
> this change though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13159) Rename camel-website to website
[
https://issues.apache.org/jira/browse/CAMEL-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13159:
Fix Version/s: 3.0.0
> Rename camel-website to website
> ---
>
> Key: CAMEL-13159
> URL: https://issues.apache.org/jira/browse/CAMEL-13159
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Tadayoshi Sato
>Priority: Minor
> Fix For: 3.0.0
>
>
> Following the recent directly layout convention such as CAMEL-13040, we
> should also move {{camel-website}} to simply {{website}}, so that there are
> no directories prefixing {{camel-*}} that appear in the top level of the
> project.
> We need to be careful not to break the generation of the new website with
> this change though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-13162) Unknown parameter issue on weaving from-with on a REST-DSL route
[
https://issues.apache.org/jira/browse/CAMEL-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-13162:
--
Assignee: Dmitry Volodin
> Unknown parameter issue on weaving from-with on a REST-DSL route
>
>
> Key: CAMEL-13162
> URL: https://issues.apache.org/jira/browse/CAMEL-13162
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.23.0, 2.23.1
>Reporter: Roman Vottner
>Assignee: Dmitry Volodin
>Priority: Critical
>
> On attempting to weave a REST-DSL route and replace the route with something
> different, i.e. {color:#d04437}direct:start{color} seems to be fine in
> regards to the produced debug XML ...
> XML before weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
> uri="rest://post:/heartbeat:/%7Bsender%7D?description=Test+descriptionrouteId=apiHeartbeat"/>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> XML after weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> ... though on sending a message via a producerTemplate will result in the
> following exception:
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> apiHeartbeat: Route(apiHeartbeat)[[From[direct://start?routeId=apiHeartbea...
> because of Failed to resolve endpoint: direct://start?routeId=apiHeartbeat
> due to: Failed to resolve endpoint: direct://start?routeId=apiHeartbeat due
> to: There are 1 parameters that couldn't be set on the endpoint. Check the
> uri if the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[{routeId=apiHeartbeat}]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:217)
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1140)
> at
> org.apache.camel.model.RouteDefinition.adviceWith(RouteDefinition.java:318)
> at
> at.erpel.messaginghub.services.unit.routes.api.CamelRouteAdviceTest.testRouteWeaving(CamelRouteAdviceTest.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:74)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:84)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
> at
> org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
>
[jira] [Comment Edited] (CAMEL-13162) Unknown parameter issue on weaving from-with on a REST-DSL route
[
https://issues.apache.org/jira/browse/CAMEL-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761023#comment-16761023
]
Dmitry Volodin edited comment on CAMEL-13162 at 2/5/19 4:56 PM:
Yes, could be, as CAMEL-12943 is also regression of CAMEL-12908
Thanks for reporting, I will look at this issue.
was (Author: dmvolod):
Yes, could be, as CAMEL-12943 is also regression of CAMEL-12908
Thanks for reporting, I will at this issue.
> Unknown parameter issue on weaving from-with on a REST-DSL route
>
>
> Key: CAMEL-13162
> URL: https://issues.apache.org/jira/browse/CAMEL-13162
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.23.0, 2.23.1
>Reporter: Roman Vottner
>Priority: Critical
>
> On attempting to weave a REST-DSL route and replace the route with something
> different, i.e. {color:#d04437}direct:start{color} seems to be fine in
> regards to the produced debug XML ...
> XML before weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
> uri="rest://post:/heartbeat:/%7Bsender%7D?description=Test+descriptionrouteId=apiHeartbeat"/>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> XML after weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> ... though on sending a message via a producerTemplate will result in the
> following exception:
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> apiHeartbeat: Route(apiHeartbeat)[[From[direct://start?routeId=apiHeartbea...
> because of Failed to resolve endpoint: direct://start?routeId=apiHeartbeat
> due to: Failed to resolve endpoint: direct://start?routeId=apiHeartbeat due
> to: There are 1 parameters that couldn't be set on the endpoint. Check the
> uri if the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[{routeId=apiHeartbeat}]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:217)
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1140)
> at
> org.apache.camel.model.RouteDefinition.adviceWith(RouteDefinition.java:318)
> at
> at.erpel.messaginghub.services.unit.routes.api.CamelRouteAdviceTest.testRouteWeaving(CamelRouteAdviceTest.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:74)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:84)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
> at
> org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
>
[jira] [Commented] (CAMEL-13162) Unknown parameter issue on weaving from-with on a REST-DSL route
[
https://issues.apache.org/jira/browse/CAMEL-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761023#comment-16761023
]
Dmitry Volodin commented on CAMEL-13162:
Yes, could be, as CAMEL-12943 is also regression of CAMEL-12908
Thanks for reporting, I will at this issue.
> Unknown parameter issue on weaving from-with on a REST-DSL route
>
>
> Key: CAMEL-13162
> URL: https://issues.apache.org/jira/browse/CAMEL-13162
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.23.0, 2.23.1
>Reporter: Roman Vottner
>Priority: Critical
>
> On attempting to weave a REST-DSL route and replace the route with something
> different, i.e. {color:#d04437}direct:start{color} seems to be fine in
> regards to the produced debug XML ...
> XML before weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
> uri="rest://post:/heartbeat:/%7Bsender%7D?description=Test+descriptionrouteId=apiHeartbeat"/>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> XML after weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> ... though on sending a message via a producerTemplate will result in the
> following exception:
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> apiHeartbeat: Route(apiHeartbeat)[[From[direct://start?routeId=apiHeartbea...
> because of Failed to resolve endpoint: direct://start?routeId=apiHeartbeat
> due to: Failed to resolve endpoint: direct://start?routeId=apiHeartbeat due
> to: There are 1 parameters that couldn't be set on the endpoint. Check the
> uri if the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[{routeId=apiHeartbeat}]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:217)
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1140)
> at
> org.apache.camel.model.RouteDefinition.adviceWith(RouteDefinition.java:318)
> at
> at.erpel.messaginghub.services.unit.routes.api.CamelRouteAdviceTest.testRouteWeaving(CamelRouteAdviceTest.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:74)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:84)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
> at
> org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
> at
[jira] [Comment Edited] (CAMEL-13162) Unknown parameter issue on weaving from-with on a REST-DSL route
[
https://issues.apache.org/jira/browse/CAMEL-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761011#comment-16761011
]
Roman Vottner edited comment on CAMEL-13162 at 2/5/19 4:47 PM:
---
Code runs with Camel 2.21.4 and 2.22.3 if I add a configuration such as
{code:java}
restConfiguration().component("servlet");{code}
before the rest route definition, though with 2.23.0 and 2.23.1 the same test
fails even with the restConfiguration in place.
It might be related to https://issues.apache.org/jira/browse/CAMEL-12943
was (Author: rovo):
Code runs with Camel 2.21.4 and 2.22.3 if I add a configuration such as
{code:java}
restConfiguration().component("servlet");{code}
before the rest route definition, though with 2.23.0 and 2.23.1 the same test
fails even with the restConfiguration in place.
> Unknown parameter issue on weaving from-with on a REST-DSL route
>
>
> Key: CAMEL-13162
> URL: https://issues.apache.org/jira/browse/CAMEL-13162
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.23.0, 2.23.1
>Reporter: Roman Vottner
>Priority: Critical
>
> On attempting to weave a REST-DSL route and replace the route with something
> different, i.e. {color:#d04437}direct:start{color} seems to be fine in
> regards to the produced debug XML ...
> XML before weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
> uri="rest://post:/heartbeat:/%7Bsender%7D?description=Test+descriptionrouteId=apiHeartbeat"/>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> XML after weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> ... though on sending a message via a producerTemplate will result in the
> following exception:
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> apiHeartbeat: Route(apiHeartbeat)[[From[direct://start?routeId=apiHeartbea...
> because of Failed to resolve endpoint: direct://start?routeId=apiHeartbeat
> due to: Failed to resolve endpoint: direct://start?routeId=apiHeartbeat due
> to: There are 1 parameters that couldn't be set on the endpoint. Check the
> uri if the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[{routeId=apiHeartbeat}]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:217)
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1140)
> at
> org.apache.camel.model.RouteDefinition.adviceWith(RouteDefinition.java:318)
> at
> at.erpel.messaginghub.services.unit.routes.api.CamelRouteAdviceTest.testRouteWeaving(CamelRouteAdviceTest.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:74)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:84)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
> at
> org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
[jira] [Commented] (CAMEL-13162) Unknown parameter issue on weaving from-with on a REST-DSL route
[
https://issues.apache.org/jira/browse/CAMEL-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761011#comment-16761011
]
Roman Vottner commented on CAMEL-13162:
---
Code runs with Camel 2.21.4 and 2.22.3 if I add a configuration such as
{code:java}
restConfiguration().component("servlet");{code}
before the rest route definition, though with 2.23.0 and 2.23.1 the same test
fails even with the restConfiguration in place.
> Unknown parameter issue on weaving from-with on a REST-DSL route
>
>
> Key: CAMEL-13162
> URL: https://issues.apache.org/jira/browse/CAMEL-13162
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.23.0, 2.23.1
>Reporter: Roman Vottner
>Priority: Critical
>
> On attempting to weave a REST-DSL route and replace the route with something
> different, i.e. {color:#d04437}direct:start{color} seems to be fine in
> regards to the produced debug XML ...
> XML before weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
> uri="rest://post:/heartbeat:/%7Bsender%7D?description=Test+descriptionrouteId=apiHeartbeat"/>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> XML after weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> ... though on sending a message via a producerTemplate will result in the
> following exception:
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> apiHeartbeat: Route(apiHeartbeat)[[From[direct://start?routeId=apiHeartbea...
> because of Failed to resolve endpoint: direct://start?routeId=apiHeartbeat
> due to: Failed to resolve endpoint: direct://start?routeId=apiHeartbeat due
> to: There are 1 parameters that couldn't be set on the endpoint. Check the
> uri if the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[{routeId=apiHeartbeat}]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:217)
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1140)
> at
> org.apache.camel.model.RouteDefinition.adviceWith(RouteDefinition.java:318)
> at
> at.erpel.messaginghub.services.unit.routes.api.CamelRouteAdviceTest.testRouteWeaving(CamelRouteAdviceTest.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:74)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:84)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
> at
> org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
> at
>
[jira] [Comment Edited] (CAMEL-13162) Unknown parameter issue on weaving from-with on a REST-DSL route
[
https://issues.apache.org/jira/browse/CAMEL-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760974#comment-16760974
]
Dmitry Volodin edited comment on CAMEL-13162 at 2/5/19 4:11 PM:
This could be regression of CAMEL-12908
Please check the issue with 2.21.x version if it will work, we will look at the
related fix.
was (Author: dmvolod):
This could be regression of CAMEL-12908
Please check the issue with 2.21.x version if it will work, we will look to the
related fix.
> Unknown parameter issue on weaving from-with on a REST-DSL route
>
>
> Key: CAMEL-13162
> URL: https://issues.apache.org/jira/browse/CAMEL-13162
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.23.0, 2.23.1
>Reporter: Roman Vottner
>Priority: Critical
>
> On attempting to weave a REST-DSL route and replace the route with something
> different, i.e. {color:#d04437}direct:start{color} seems to be fine in
> regards to the produced debug XML ...
> XML before weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
> uri="rest://post:/heartbeat:/%7Bsender%7D?description=Test+descriptionrouteId=apiHeartbeat"/>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> XML after weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> ... though on sending a message via a producerTemplate will result in the
> following exception:
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> apiHeartbeat: Route(apiHeartbeat)[[From[direct://start?routeId=apiHeartbea...
> because of Failed to resolve endpoint: direct://start?routeId=apiHeartbeat
> due to: Failed to resolve endpoint: direct://start?routeId=apiHeartbeat due
> to: There are 1 parameters that couldn't be set on the endpoint. Check the
> uri if the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[{routeId=apiHeartbeat}]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:217)
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1140)
> at
> org.apache.camel.model.RouteDefinition.adviceWith(RouteDefinition.java:318)
> at
> at.erpel.messaginghub.services.unit.routes.api.CamelRouteAdviceTest.testRouteWeaving(CamelRouteAdviceTest.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:74)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:84)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
> at
> org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
>
[jira] [Commented] (CAMEL-13162) Unknown parameter issue on weaving from-with on a REST-DSL route
[
https://issues.apache.org/jira/browse/CAMEL-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760974#comment-16760974
]
Dmitry Volodin commented on CAMEL-13162:
This could be regression of CAMEL-12908
Please check the issue with 2.21.x version if it will work, we will look to the
related fix.
> Unknown parameter issue on weaving from-with on a REST-DSL route
>
>
> Key: CAMEL-13162
> URL: https://issues.apache.org/jira/browse/CAMEL-13162
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 2.23.0, 2.23.1
>Reporter: Roman Vottner
>Priority: Critical
>
> On attempting to weave a REST-DSL route and replace the route with something
> different, i.e. {color:#d04437}direct:start{color} seems to be fine in
> regards to the produced debug XML ...
> XML before weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
> uri="rest://post:/heartbeat:/%7Bsender%7D?description=Test+descriptionrouteId=apiHeartbeat"/>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> XML after weaving:
> {code:java}
>
> http://camel.apache.org/schema/spring;
> customId="true"
> id="apiHeartbeat"
> rest="true">
>
> message="Received request with payload ${body} and headers:
> ${headers}"/>
>
> {code}
> ... though on sending a message via a producerTemplate will result in the
> following exception:
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> apiHeartbeat: Route(apiHeartbeat)[[From[direct://start?routeId=apiHeartbea...
> because of Failed to resolve endpoint: direct://start?routeId=apiHeartbeat
> due to: Failed to resolve endpoint: direct://start?routeId=apiHeartbeat due
> to: There are 1 parameters that couldn't be set on the endpoint. Check the
> uri if the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[{routeId=apiHeartbeat}]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:217)
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1140)
> at
> org.apache.camel.model.RouteDefinition.adviceWith(RouteDefinition.java:318)
> at
> at.erpel.messaginghub.services.unit.routes.api.CamelRouteAdviceTest.testRouteWeaving(CamelRouteAdviceTest.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:74)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:84)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
> at
> org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
>
[jira] [Created] (CAMEL-13162) Unknown parameter issue on weaving from-with on a REST-DSL route
Roman Vottner created CAMEL-13162:
-
Summary: Unknown parameter issue on weaving from-with on a
REST-DSL route
Key: CAMEL-13162
URL: https://issues.apache.org/jira/browse/CAMEL-13162
Project: Camel
Issue Type: Bug
Components: camel-test
Affects Versions: 2.23.1, 2.23.0
Reporter: Roman Vottner
On attempting to weave a REST-DSL route and replace the route with something
different, i.e. {color:#d04437}direct:start{color} seems to be fine in regards
to the produced debug XML ...
XML before weaving:
{code:java}
http://camel.apache.org/schema/spring;
customId="true"
id="apiHeartbeat"
rest="true">
{code}
XML after weaving:
{code:java}
http://camel.apache.org/schema/spring;
customId="true"
id="apiHeartbeat"
rest="true">
{code}
... though on sending a message via a producerTemplate will result in the
following exception:
{code:java}
org.apache.camel.FailedToCreateRouteException: Failed to create route
apiHeartbeat: Route(apiHeartbeat)[[From[direct://start?routeId=apiHeartbea...
because of Failed to resolve endpoint: direct://start?routeId=apiHeartbeat due
to: Failed to resolve endpoint: direct://start?routeId=apiHeartbeat due to:
There are 1 parameters that couldn't be set on the endpoint. Check the uri if
the parameters are spelt correctly and that they are properties of the
endpoint. Unknown parameters=[{routeId=apiHeartbeat}]
at
org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:217)
at
org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1140)
at
org.apache.camel.model.RouteDefinition.adviceWith(RouteDefinition.java:318)
at
at.erpel.messaginghub.services.unit.routes.api.CamelRouteAdviceTest.testRouteWeaving(CamelRouteAdviceTest.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:74)
at
org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:84)
at
org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
at
org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
at
org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:190)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint: direct://start?routeId=apiHeartbeat due to: Failed to resolve
endpoint: direct://start?routeId=apiHeartbeat
[jira] [Resolved] (CAMEL-13161) Camel-AWS: Create an AWS ECS component
[ https://issues.apache.org/jira/browse/CAMEL-13161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13161. -- Resolution: Fixed > Camel-AWS: Create an AWS ECS component > -- > > Key: CAMEL-13161 > URL: https://issues.apache.org/jira/browse/CAMEL-13161 > Project: Camel > Issue Type: Task > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13002) Fix Karaf features in Camel 3
[ https://issues.apache.org/jira/browse/CAMEL-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved CAMEL-13002. - Resolution: Fixed > Fix Karaf features in Camel 3 > - > > Key: CAMEL-13002 > URL: https://issues.apache.org/jira/browse/CAMEL-13002 > Project: Camel > Issue Type: Task > Components: karaf >Reporter: Andrea Cosentino >Assignee: Guillaume Nodet >Priority: Critical > Fix For: 3.0.0 > > > In 3.x branch, currently, the Karaf features are not working because of the > refactoring of Camel-core. We need to take a look. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13153) camel-mail - Strip newlines from exchange headers
[ https://issues.apache.org/jira/browse/CAMEL-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-13153. - Resolution: Fixed > camel-mail - Strip newlines from exchange headers > - > > Key: CAMEL-13153 > URL: https://issues.apache.org/jira/browse/CAMEL-13153 > Project: Camel > Issue Type: Task > Components: camel-mail >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.2, 2.24.0, 2.22.4 > > Time Spent: 20m > Remaining Estimate: 0h > > We should strip newlines from exchange headers that are written out by > camel-mail. > PR: https://github.com/apache/camel/pull/2743 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13161) Camel-AWS: Create an AWS ECS component
Andrea Cosentino created CAMEL-13161: Summary: Camel-AWS: Create an AWS ECS component Key: CAMEL-13161 URL: https://issues.apache.org/jira/browse/CAMEL-13161 Project: Camel Issue Type: Task Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13153) camel-mail - Strip newlines from exchange headers
[ https://issues.apache.org/jira/browse/CAMEL-13153?focusedWorklogId=194469=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-194469 ] ASF GitHub Bot logged work on CAMEL-13153: -- Author: ASF GitHub Bot Created on: 05/Feb/19 10:59 Start Date: 05/Feb/19 10:59 Worklog Time Spent: 10m Work Description: coheigea commented on pull request #2743: CAMEL-13153 - Strip newlines from exchange headers URL: https://github.com/apache/camel/pull/2743 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 194469) Time Spent: 20m (was: 10m) > camel-mail - Strip newlines from exchange headers > - > > Key: CAMEL-13153 > URL: https://issues.apache.org/jira/browse/CAMEL-13153 > Project: Camel > Issue Type: Task > Components: camel-mail >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.2, 2.24.0, 2.22.4 > > Time Spent: 20m > Remaining Estimate: 0h > > We should strip newlines from exchange headers that are written out by > camel-mail. > PR: https://github.com/apache/camel/pull/2743 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13160) Remove headers should be case in-sensitive by default
[ https://issues.apache.org/jira/browse/CAMEL-13160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13160. - Resolution: Fixed > Remove headers should be case in-sensitive by default > - > > Key: CAMEL-13160 > URL: https://issues.apache.org/jira/browse/CAMEL-13160 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > The PatternHelper.matchPattern is case sensitive when matching with wildcard > and regexp. For exact match then header keys are by default case insensitive > so remove foo will remove FOO Foo and foo headers. But remove pattern=foo* > will only remove lower-case foo headers. So we should make this case > insensitive for all kinds of patterns (exact, wildcard and regexp). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13160) Remove headers should be case in-sensitive by default
Claus Ibsen created CAMEL-13160: --- Summary: Remove headers should be case in-sensitive by default Key: CAMEL-13160 URL: https://issues.apache.org/jira/browse/CAMEL-13160 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.0.0 The PatternHelper.matchPattern is case sensitive when matching with wildcard and regexp. For exact match then header keys are by default case insensitive so remove foo will remove FOO Foo and foo headers. But remove pattern=foo* will only remove lower-case foo headers. So we should make this case insensitive for all kinds of patterns (exact, wildcard and regexp). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
