[jira] [Created] (CAMEL-13089) camel-rabbitmq cannot be used in Thorntail
Andreas Klemp created CAMEL-13089:
-
Summary: camel-rabbitmq cannot be used in Thorntail
Key: CAMEL-13089
URL: https://issues.apache.org/jira/browse/CAMEL-13089
Project: Camel
Issue Type: Bug
Components: camel-rabbitmq
Affects Versions: 2.19.0
Environment: Thorntail 2.1.0.Final
Reporter: Andreas Klemp
Already reported this in [https://issues.jboss.org/browse/THORN-2314] but they
claim to not support Camel in Thorntail.
As soon as I try to add Camel to my Thorntail 2.1.0.Final service via
camel-rabbitmq the service is not starting anymore. There are no useful hints,
documentation or help on the internet that I found.
{noformat}
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC01: Failed
to start service
jboss.deployment.unit."my-service-2.1-SNAPSHOT.war".WeldStartService:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."my-service-2.1-SNAPSHOT.war".WeldStartService: Failed to
start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.weld.exceptions.DeploymentException:
org.apache.commons.pool
at
org.jboss.weld.executor.AbstractExecutorServices.checkForExceptions(AbstractExecutorServices.java:66)
at
org.jboss.weld.executor.AbstractExecutorServices.invokeAllAndCheckForExceptions(AbstractExecutorServices.java:43)
at
org.jboss.weld.executor.AbstractExecutorServices.invokeAllAndCheckForExceptions(AbstractExecutorServices.java:51)
at
org.jboss.weld.bootstrap.ConcurrentBeanDeployer.addClasses(ConcurrentBeanDeployer.java:58)
at
org.jboss.weld.bootstrap.BeanDeployment.createClasses(BeanDeployment.java:224)
at
org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:398)
at
org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:76)
at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:94)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
... 3 more
Caused by: org.jboss.modules.ModuleLoadError: org.apache.commons.pool
at
org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74)
at org.jboss.modules.Module.getPathsUnchecked(Module.java:1560)
at org.jboss.modules.Module.loadModuleClass(Module.java:709)
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400)
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
at
org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:358)
at
org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:437)
at
org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:274)
at
org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77)
at org.jboss.modules.Module.loadModuleClass(Module.java:714)
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400)
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
at java.lang.Class.getDeclaredConstructors(Class.java:2020)
at
org.jboss.weld.annotated.slim.backed.SecurityActions.getDeclaredConstructors(SecurityActions.java:57)
at
org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedConstructors.computeValue(BackedAnnotatedType.java:164)
at
org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedConstructors.computeValue(BackedAnnotatedType.java:161)
at org.jboss.weld.util.LazyValueHolder.get(LazyValueHolder.java:49)
at
[jira] [Commented] (CAMEL-13040) camel3 - camel-core directory layout
[ https://issues.apache.org/jira/browse/CAMEL-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747702#comment-16747702 ] Andrea Cosentino commented on CAMEL-13040: -- What's the best approach here? Do we want to move again the component in the camel-core folder as separate component? Or do we want to customize the camel-core-starter? > camel3 - camel-core directory layout > > > Key: CAMEL-13040 > URL: https://issues.apache.org/jira/browse/CAMEL-13040 > Project: Camel > Issue Type: Task > Components: camel-core >Affects Versions: 3.0.0 >Reporter: Claus Ibsen >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.0.0 > > > I think we should move the splitted camel-core modules into a common parent > folder. > camel-core (POM folder) > + camel-api > + camel-core-impl > + camel-management-api > + camel-management-impl > + camel-util > Then we can have camel-core as a POM for all the sub modules that > collectively is "camel-core" as they are in 2.x. > And we can then continue to splitup the camel-core-impl into smaller pieces, > such as the DSL with a camel-dsl-java and camel-dsl-xml > Just mind that when we do this its harder to backport code fixes from 3.x to > 2.x as now the camel-core is not in the same directory location. But this > will eventually happen the more camel-core is splitted up into smaller > modules. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13084) javax.servlet.http.MappingMatch not found when starting camel-example-spring-boot
[
https://issues.apache.org/jira/browse/CAMEL-13084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13084:
Affects Version/s: 3.0.0
> javax.servlet.http.MappingMatch not found when starting
> camel-example-spring-boot
> -
>
> Key: CAMEL-13084
> URL: https://issues.apache.org/jira/browse/CAMEL-13084
> Project: Camel
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.23.0, 3.0.0, 2.23.1
>Reporter: Peter Palaga
>Priority: Major
>
> Steps to reproduce:
> {code}
> git checkout -b camel-2.x upstream/camel-2.x
> git show --summary
> # commit fb5278ea2860e05b833f8e32d4ec6c2dfcc73c94 (HEAD -> camel-2.x,
> upstream/camel-2.x)
> # Author: Claus Ibsen
> # Date: Sat Jan 19 09:57:17 2019 +0100
> #
> # Add missing docs for EIPs
> #
> cd examples/camel-example-spring-boot
> mvn clean package
> java -jar target/camel-example-spring-boot-*.jar
> # Expected: no error
> # Actual:
> # [...]
> # Error starting ApplicationContext. To display the conditions report re-run
> your application with 'debug' enabled.
> 2019-01-19 17:09:16.253 ERROR 21732 --- [ main]
> o.s.boot.SpringApplication : Application run failed
> org.springframework.context.ApplicationContextException: Unable to start web
> server; nested exception is java.lang.NoClassDefFoundError:
> javax/servlet/http/MappingMatch
> at
> org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:157)
> ~[spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:540)
> ~[spring-context-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
> at
> org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142)
> ~[spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
> [spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
> [spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:316)
> [spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1260)
> [spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1248)
> [spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at sample.camel.MyCamelApplication.main(MyCamelApplication.java:33)
> [classes!/:2.24.0-SNAPSHOT]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0_191]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0_191]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0_191]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_191]
> at
> org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
> [camel-example-spring-boot-2.24.0-SNAPSHOT.jar:2.24.0-SNAPSHOT]
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
> [camel-example-spring-boot-2.24.0-SNAPSHOT.jar:2.24.0-SNAPSHOT]
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
> [camel-example-spring-boot-2.24.0-SNAPSHOT.jar:2.24.0-SNAPSHOT]
> at
> org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
> [camel-example-spring-boot-2.24.0-SNAPSHOT.jar:2.24.0-SNAPSHOT]
> Caused by: java.lang.NoClassDefFoundError: javax/servlet/http/MappingMatch
> at
> io.undertow.servlet.handlers.ServletPathMatches.resolveServletForPath(ServletPathMatches.java:445)
> ~[undertow-servlet-2.0.16.Final.jar!/:2.0.16.Final]
> at
> io.undertow.servlet.handlers.ServletPathMatches.setupServletChains(ServletPathMatches.java:280)
> ~[undertow-servlet-2.0.16.Final.jar!/:2.0.16.Final]
> at
> io.undertow.servlet.handlers.ServletPathMatches.getData(ServletPathMatches.java:145)
> ~[undertow-servlet-2.0.16.Final.jar!/:2.0.16.Final]
> at
> io.undertow.servlet.handlers.ServletPathMatches.initData(ServletPathMatches.java:76)
> ~[undertow-servlet-2.0.16.Final.jar!/:2.0.16.Final]
> at
> io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:256)
> ~[undertow-servlet-2.0.16.Final.jar!/:2.0.16.Final]
> at
>
[jira] [Created] (CAMEL-13088) build system - Automate list of components in parent and apache-camel poms
Claus Ibsen created CAMEL-13088: --- Summary: build system - Automate list of components in parent and apache-camel poms Key: CAMEL-13088 URL: https://issues.apache.org/jira/browse/CAMEL-13088 Project: Camel Issue Type: Task Components: build system Reporter: Claus Ibsen Fix For: 3.0.0 We need to add manually all the camel JARs in the parent/pom and apache-camel poms and the include file as well. As we get more and more components and also -starter JARs we should automate this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13084) javax.servlet.http.MappingMatch not found when starting camel-example-spring-boot
[
https://issues.apache.org/jira/browse/CAMEL-13084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13084:
Fix Version/s: 2.24.0
2.23.2
3.0.0
> javax.servlet.http.MappingMatch not found when starting
> camel-example-spring-boot
> -
>
> Key: CAMEL-13084
> URL: https://issues.apache.org/jira/browse/CAMEL-13084
> Project: Camel
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.23.0, 3.0.0, 2.23.1
>Reporter: Peter Palaga
>Priority: Major
> Fix For: 3.0.0, 2.23.2, 2.24.0
>
>
> Steps to reproduce:
> {code}
> git checkout -b camel-2.x upstream/camel-2.x
> git show --summary
> # commit fb5278ea2860e05b833f8e32d4ec6c2dfcc73c94 (HEAD -> camel-2.x,
> upstream/camel-2.x)
> # Author: Claus Ibsen
> # Date: Sat Jan 19 09:57:17 2019 +0100
> #
> # Add missing docs for EIPs
> #
> cd examples/camel-example-spring-boot
> mvn clean package
> java -jar target/camel-example-spring-boot-*.jar
> # Expected: no error
> # Actual:
> # [...]
> # Error starting ApplicationContext. To display the conditions report re-run
> your application with 'debug' enabled.
> 2019-01-19 17:09:16.253 ERROR 21732 --- [ main]
> o.s.boot.SpringApplication : Application run failed
> org.springframework.context.ApplicationContextException: Unable to start web
> server; nested exception is java.lang.NoClassDefFoundError:
> javax/servlet/http/MappingMatch
> at
> org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:157)
> ~[spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:540)
> ~[spring-context-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
> at
> org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142)
> ~[spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
> [spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
> [spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:316)
> [spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1260)
> [spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1248)
> [spring-boot-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
> at sample.camel.MyCamelApplication.main(MyCamelApplication.java:33)
> [classes!/:2.24.0-SNAPSHOT]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0_191]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0_191]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0_191]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_191]
> at
> org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
> [camel-example-spring-boot-2.24.0-SNAPSHOT.jar:2.24.0-SNAPSHOT]
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
> [camel-example-spring-boot-2.24.0-SNAPSHOT.jar:2.24.0-SNAPSHOT]
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
> [camel-example-spring-boot-2.24.0-SNAPSHOT.jar:2.24.0-SNAPSHOT]
> at
> org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
> [camel-example-spring-boot-2.24.0-SNAPSHOT.jar:2.24.0-SNAPSHOT]
> Caused by: java.lang.NoClassDefFoundError: javax/servlet/http/MappingMatch
> at
> io.undertow.servlet.handlers.ServletPathMatches.resolveServletForPath(ServletPathMatches.java:445)
> ~[undertow-servlet-2.0.16.Final.jar!/:2.0.16.Final]
> at
> io.undertow.servlet.handlers.ServletPathMatches.setupServletChains(ServletPathMatches.java:280)
> ~[undertow-servlet-2.0.16.Final.jar!/:2.0.16.Final]
> at
> io.undertow.servlet.handlers.ServletPathMatches.getData(ServletPathMatches.java:145)
> ~[undertow-servlet-2.0.16.Final.jar!/:2.0.16.Final]
> at
> io.undertow.servlet.handlers.ServletPathMatches.initData(ServletPathMatches.java:76)
> ~[undertow-servlet-2.0.16.Final.jar!/:2.0.16.Final]
> at
> io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:256)
>
[jira] [Commented] (CAMEL-13086) Java DSL: Rename "endChoice" to "endWhen"
[
https://issues.apache.org/jira/browse/CAMEL-13086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747489#comment-16747489
]
Peter Keller commented on CAMEL-13086:
--
Yes, you are right. But {{choice}} is ended by {{end}}, and {{when}} by
{{endChoice}}. My suggestion is to end {{choice}} by {{endChoice}} and {{when}}
by {{endWhen}}.
> Java DSL: Rename "endChoice" to "endWhen"
> -
>
> Key: CAMEL-13086
> URL: https://issues.apache.org/jira/browse/CAMEL-13086
> Project: Camel
> Issue Type: Wish
> Components: camel-core
>Reporter: Peter Keller
>Priority: Major
> Fix For: 3.0.0
>
>
> Java DSL: Rename {{endChoice}} to {{endWhen}} as {{endChoice}} actually ends
> a {{when}} condition.
> I am aware that this will break current routes. Nevertheless I wanted to
> bring this issue to discussion as {{endChoice}} isn't obvious for beginners
> that learn the framework.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-11807) Upgrade to JUnit 5
[
https://issues.apache.org/jira/browse/CAMEL-11807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747485#comment-16747485
]
Peter Keller commented on CAMEL-11807:
--
Wouldn't it be sensible to have two separate issues:
1) Upgrade Camel unit tests to JUnit 5
2) Provide base test classes for consumers of the framework using JUnit 5 (e.g.
{{CamelSpringRunner}} and {{CamelSpringBootRunner}}).
> Upgrade to JUnit 5
> --
>
> Key: CAMEL-11807
> URL: https://issues.apache.org/jira/browse/CAMEL-11807
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0, Future
>
>
> See http://junit.org/junit5/
> Note: it provides a junit-vintage module so we should be able to migrate
> stuffs easily (!)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13087) Add more obvious exception handling for "multicast"
Peter Keller created CAMEL-13087:
Summary: Add more obvious exception handling for "multicast"
Key: CAMEL-13087
URL: https://issues.apache.org/jira/browse/CAMEL-13087
Project: Camel
Issue Type: Wish
Reporter: Peter Keller
Fix For: 3.0.0
Add more obvious exception handling for {{multicast}}.
E.g. see
*
https://stackoverflow.com/questions/35896325/camel-multicast-exception-propagation
*
https://stackoverflow.com/questions/51156635/apache-camel-how-to-catch-exception-with-multicast
*
https://stackoverflow.com/questions/40281605/camel-isnt-propagating-exceptions-when-they-are-thrown-inside-of-a-multicast-wh
*
https://stackoverflow.com/questions/7317776/apache-camel-multicast-exception-and-aggregation-strategy
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13086) Java DSL: Rename "endChoice" to "endWhen"
[
https://issues.apache.org/jira/browse/CAMEL-13086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747487#comment-16747487
]
Andrea Cosentino commented on CAMEL-13086:
--
There is choice() in the Java DSL
> Java DSL: Rename "endChoice" to "endWhen"
> -
>
> Key: CAMEL-13086
> URL: https://issues.apache.org/jira/browse/CAMEL-13086
> Project: Camel
> Issue Type: Wish
> Components: camel-core
>Reporter: Peter Keller
>Priority: Major
> Fix For: 3.0.0
>
>
> Java DSL: Rename {{endChoice}} to {{endWhen}} as {{endChoice}} actually ends
> a {{when}} condition.
> I am aware that this will break current routes. Nevertheless I wanted to
> bring this issue to discussion as {{endChoice}} isn't obvious for beginners
> that learn the framework.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13086) Java DSL: Rename "endChoice" to "endWhen"
Peter Keller created CAMEL-13086:
Summary: Java DSL: Rename "endChoice" to "endWhen"
Key: CAMEL-13086
URL: https://issues.apache.org/jira/browse/CAMEL-13086
Project: Camel
Issue Type: Wish
Components: camel-core
Reporter: Peter Keller
Fix For: 3.0.0
Java DSL: Rename {{endChoice}} to {{endWhen}} as {{endChoice}} actually ends a
{{when}} condition.
I am aware that this will break current routes. Nevertheless I wanted to bring
this issue to discussion as {{endChoice}} isn't obvious for beginners that
learn the framework.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13085) Java DSL: Add explicit endings such as “endSplit”, “endMulticast”, "endException"
[
https://issues.apache.org/jira/browse/CAMEL-13085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Keller updated CAMEL-13085:
-
Issue Type: Wish (was: Improvement)
> Java DSL: Add explicit endings such as “endSplit”, “endMulticast”,
> "endException"
> -
>
> Key: CAMEL-13085
> URL: https://issues.apache.org/jira/browse/CAMEL-13085
> Project: Camel
> Issue Type: Wish
> Components: camel-core
>Reporter: Peter Keller
>Priority: Major
> Fix For: 3.0.0
>
>
> For non-trivial complex routes it isn't obvious where structurel elements
> such as {{split}}, {{multicast}} or {{exception}} are ending. This is even
> true for non-novice user of the framework.
> Suggestion: Add explicit endings such as {{endSplit}}, {{endMulticast}},
> {{endException}} to the Java DSL. These ending may be optional so that no
> migration is needed from Camel 2 to Camel 3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13085) Java DSL: Add explicit endings such as “endSplit”, “endMulticast”, "endException"
Peter Keller created CAMEL-13085:
Summary: Java DSL: Add explicit endings such as “endSplit”,
“endMulticast”, "endException"
Key: CAMEL-13085
URL: https://issues.apache.org/jira/browse/CAMEL-13085
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Peter Keller
Fix For: 3.0.0
For non-trivial complex routes it isn't obvious where structurel elements such
as {{split}}, {{multicast}} or {{exception}} are ending. This is even true for
non-novice user of the framework.
Suggestion: Add explicit endings such as {{endSplit}}, {{endMulticast}},
{{endException}} to the Java DSL. These ending may be optional so that no
migration is needed from Camel 2 to Camel 3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12953) Camel grpc component doesn't transfer the Message headers
[ https://issues.apache.org/jira/browse/CAMEL-12953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-12953: --- Fix Version/s: 2.24.0 3.0.0 > Camel grpc component doesn't transfer the Message headers > - > > Key: CAMEL-12953 > URL: https://issues.apache.org/jira/browse/CAMEL-12953 > Project: Camel > Issue Type: New Feature > Components: camel-grpc >Affects Versions: 2.22.1 >Reporter: Vishal Vijayan >Assignee: Dmitry Volodin >Priority: Major > Fix For: 3.0.0, 2.24.0 > > > Headers that are added to the Message in the camel Exchange before making a > call to the camel-grpc component are not received at the grpc consumer. The > expectation is that these headers would be added to the grpcStub before > sending over the wire (like other components like http4 etc). > Our team has come up with a workaround for this but it is extremely > cumbersome. We had to extend the GrpcProducer to introduce a custom > GrpcExchangeForwarder that would copy header from exchange to the stub before > invoking the sync/async method. > At the consumer side we had to extend the GrpcConsumer to use a custom > ServerInterceptor to capture the grpc headers and custom MethodHandler to > transfer the grpc headers to the Camel exchange headers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12953) Camel grpc component doesn't transfer the Message headers
[ https://issues.apache.org/jira/browse/CAMEL-12953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-12953: -- Assignee: Dmitry Volodin > Camel grpc component doesn't transfer the Message headers > - > > Key: CAMEL-12953 > URL: https://issues.apache.org/jira/browse/CAMEL-12953 > Project: Camel > Issue Type: New Feature > Components: camel-grpc >Affects Versions: 2.22.1 >Reporter: Vishal Vijayan >Assignee: Dmitry Volodin >Priority: Major > > Headers that are added to the Message in the camel Exchange before making a > call to the camel-grpc component are not received at the grpc consumer. The > expectation is that these headers would be added to the grpcStub before > sending over the wire (like other components like http4 etc). > Our team has come up with a workaround for this but it is extremely > cumbersome. We had to extend the GrpcProducer to introduce a custom > GrpcExchangeForwarder that would copy header from exchange to the stub before > invoking the sync/async method. > At the consumer side we had to extend the GrpcConsumer to use a custom > ServerInterceptor to capture the grpc headers and custom MethodHandler to > transfer the grpc headers to the Camel exchange headers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
