[jira] [Assigned] (CAMEL-18346) Remove use of Xalan
[ https://issues.apache.org/jira/browse/CAMEL-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-18346: --- Assignee: Thomas Cunningham > Remove use of Xalan > --- > > Key: CAMEL-18346 > URL: https://issues.apache.org/jira/browse/CAMEL-18346 > Project: Camel > Issue Type: Task > Components: build system >Reporter: PJ Fanning >Assignee: Thomas Cunningham >Priority: Minor > Fix For: 3.19.0 > > > Xalan-J has an unfixed CVE. It is possible that this will be fixed in the > future but Xalan-J has had only one release since 2008 (in 2014). > https://www.cvedetails.com/cve/CVE-2022-34169/ > Java has built-in support for TransformerFactory and XPathFactory. This means > most apps that use Xalan-J can readily switch away. Saxon-HE is another well > maintained alternative. > Places where Camel still uses Xalan: > * > https://github.com/apache/camel/blob/9d6ad653b6faa16e3c09047da66cd3bca94783ee/components/camel-xmlsecurity/pom.xml > * > https://github.com/apache/camel/blob/9d6ad653b6faa16e3c09047da66cd3bca94783ee/tooling/maven/camel-eip-documentation-enricher-maven-plugin/pom.xml#L73 > There are profiles for testing in a number of poms: > eg > https://github.com/apache/camel/blob/main/core/camel-core-engine/pom.xml#L325 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18450) camel-jpa: improve to use transaction strategy in JpaMessageIdRepository
Zheng Feng created CAMEL-18450: -- Summary: camel-jpa: improve to use transaction strategy in JpaMessageIdRepository Key: CAMEL-18450 URL: https://issues.apache.org/jira/browse/CAMEL-18450 Project: Camel Issue Type: Improvement Components: camel-jpa Affects Versions: 3.18.1, 3.19.0 Reporter: Zheng Feng Assignee: Zheng Feng It needs to use transaction strategy in JpaMessageIdRepository when we have introduce it in CAMEL. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18346) Remove use of Xalan
[
https://issues.apache.org/jira/browse/CAMEL-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599095#comment-17599095
]
Thomas Cunningham commented on CAMEL-18346:
---
*Remaining xalan references after PR above* :
camel-atom, camel-fop, camel-spring-ws : all dependency exclusions, still needed
XMLConverter.java, XMLConverterHelper.java : I think these are the JDK classes
(com.sun.org.apache.xalan.internal) - I think these still apply.
{code:java}
components/camel-atom/pom.xml: xalan
components/camel-atom/pom.xml: xalan
components/camel-atom/pom.xml: xalan
components/camel-atom/pom.xml: xalan
components/camel-fop/pom.xml:
components/camel-fop/pom.xml: xalan
components/camel-fop/pom.xml: xalan
components/camel-spring-ws/pom.xml: xalan
components/camel-spring-ws/pom.xml:
xalan
components/camel-xmlsecurity/src/main/java/org/apache/camel/component/xmlsecurity/api/XmlSignatureHelper.java:
// previously we used javax.xml.transform.Transformer, however the JDK
xalan implementation did not work correctly with a specified encoding
components/camel-xslt-saxon/src/main/java/org/apache/camel/component/xslt/saxon/XsltSaxonBuilder.java:
// (see
com.sun.org.apache.xalan.internal.xsltc.trax.StAXStream2SAX).
components/camel-xslt-saxon/src/test/resources/org/apache/camel/component/xslt/transform_text.xsl:
xmlns:date="http://xml.apache.org/xalan/java/java.util.Date;
components/camel-xslt-saxon/src/test/resources/org/apache/camel/component/xslt/transform_text.xsl:
xmlns:rt="http://xml.apache.org/xalan/java/java.lang.Runtime;
components/camel-xslt-saxon/src/test/resources/org/apache/camel/component/xslt/transform_text.xsl:
xmlns:str="http://xml.apache.org/xalan/java/java.lang.String;
core/camel-core/src/test/resources/org/apache/camel/component/xslt/transformCallEcho.xsl:
xmlns:echo="xalan://org.apache.camel.component.xslt.MyEcho"
core/camel-core/src/test/resources/org/apache/camel/component/xslt/transform_text.xsl:
xmlns:date="http://xml.apache.org/xalan/java/java.util.Date;
core/camel-core/src/test/resources/org/apache/camel/component/xslt/transform_text.xsl:
xmlns:rt="http://xml.apache.org/xalan/java/java.lang.Runtime;
core/camel-xml-jaxp/src/main/java/org/apache/camel/converter/jaxp/XmlConverter.java:
=
"com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl";
core/camel-xml-jaxp/src/main/java/org/apache/camel/support/builder/xml/XMLConverterHelper.java:
=
"com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl";
❯ {code}
> Remove use of Xalan
> ---
>
> Key: CAMEL-18346
> URL: https://issues.apache.org/jira/browse/CAMEL-18346
> Project: Camel
> Issue Type: Task
> Components: build system
>Reporter: PJ Fanning
>Priority: Minor
> Fix For: 3.19.0
>
>
> Xalan-J has an unfixed CVE. It is possible that this will be fixed in the
> future but Xalan-J has had only one release since 2008 (in 2014).
> https://www.cvedetails.com/cve/CVE-2022-34169/
> Java has built-in support for TransformerFactory and XPathFactory. This means
> most apps that use Xalan-J can readily switch away. Saxon-HE is another well
> maintained alternative.
> Places where Camel still uses Xalan:
> *
> https://github.com/apache/camel/blob/9d6ad653b6faa16e3c09047da66cd3bca94783ee/components/camel-xmlsecurity/pom.xml
> *
> https://github.com/apache/camel/blob/9d6ad653b6faa16e3c09047da66cd3bca94783ee/tooling/maven/camel-eip-documentation-enricher-maven-plugin/pom.xml#L73
> There are profiles for testing in a number of poms:
> eg
> https://github.com/apache/camel/blob/main/core/camel-core-engine/pom.xml#L325
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18418) aws-s3-sink Kamelet returns 403
[
https://issues.apache.org/jira/browse/CAMEL-18418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599086#comment-17599086
]
Bruno Meseguer commented on CAMEL-18418:
This issue is important, it may affect other kamelets?
It doesn't seem to be S3 related... (sorry the title is unfortunate)
The default Kamelet's producer definition hits the problem, but the following
workaround works well:
{code:java}
# Temporary workaround that works is:
- to:
uri: "aws2-s3:{{bucketNameOrArn}}?\
accessKey={{?accessKey}}&\
secretKey={{?secretKey}}&\
region={{region}}&\
autoCreateBucket={{autoCreateBucket}}&\
uriEndpointOverride={{?uriEndpointOverride}}&\
overrideEndpoint={{?overrideEndpoint}}&\
keyName={{?keyName}}&\
useDefaultCredentialsProvider={{useDefaultCredentialsProvider}}"{code}
> aws-s3-sink Kamelet returns 403
> ---
>
> Key: CAMEL-18418
> URL: https://issues.apache.org/jira/browse/CAMEL-18418
> Project: Camel
> Issue Type: Bug
> Components: camel-kamelet
>Affects Versions: 3.18.0
> Environment: The problem has been reproduced using an OpenShift Data
> Foundation instance deployed in an OpenShift 4.10 environment.
> Find attached a compressed file containing the sample code to reproduce the
> problem. Note the same code using the Camel component instead of Kamelet
> works well.
>
>Reporter: Bruno Meseguer
>Priority: Major
> Attachments: issue.tar.gz
>
>
> The Kamelet `aws-s3-sink` returns 403 against a ceph based S3 service.
> It seems to be related to the accessKey and secretKey parameters resolution.
> A workaround that works is to edit the original Kamelet and hardcode the
> accessKey and secretKey in the aws2-s3 Camel component.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18346) Remove use of Xalan
[ https://issues.apache.org/jira/browse/CAMEL-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599085#comment-17599085 ] Thomas Cunningham commented on CAMEL-18346: --- https://github.com/apache/camel/pull/8254 > Remove use of Xalan > --- > > Key: CAMEL-18346 > URL: https://issues.apache.org/jira/browse/CAMEL-18346 > Project: Camel > Issue Type: Task > Components: build system >Reporter: PJ Fanning >Priority: Minor > Fix For: 3.19.0 > > > Xalan-J has an unfixed CVE. It is possible that this will be fixed in the > future but Xalan-J has had only one release since 2008 (in 2014). > https://www.cvedetails.com/cve/CVE-2022-34169/ > Java has built-in support for TransformerFactory and XPathFactory. This means > most apps that use Xalan-J can readily switch away. Saxon-HE is another well > maintained alternative. > Places where Camel still uses Xalan: > * > https://github.com/apache/camel/blob/9d6ad653b6faa16e3c09047da66cd3bca94783ee/components/camel-xmlsecurity/pom.xml > * > https://github.com/apache/camel/blob/9d6ad653b6faa16e3c09047da66cd3bca94783ee/tooling/maven/camel-eip-documentation-enricher-maven-plugin/pom.xml#L73 > There are profiles for testing in a number of poms: > eg > https://github.com/apache/camel/blob/main/core/camel-core-engine/pom.xml#L325 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18405) camel-karaf - Camel-file ResumeAware
[ https://issues.apache.org/jira/browse/CAMEL-18405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599066#comment-17599066 ] Claus Ibsen edited comment on CAMEL-18405 at 9/1/22 4:43 PM: - Wait for the release or use the dynamic thingy. Camel 3.19 has reworked the resume thingy so its loaded in a better way was (Author: davsclaus): Wait for the release > camel-karaf - Camel-file ResumeAware > > > Key: CAMEL-18405 > URL: https://issues.apache.org/jira/browse/CAMEL-18405 > Project: Camel > Issue Type: Bug >Affects Versions: 3.18.1 >Reporter: TARTIERE >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.18.2 > > > Unable to start application with routes listening for files. > java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: > org/apache/camel/resume/ResumeAware > at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?] > at java.util.concurrent.FutureTask.get(FutureTask.java:191) ~[?:?] > at > java.util.concurrent.AbstractExecutorService.doInvokeAny(AbstractExecutorService.java:199) > ~[?:?] > at > java.util.concurrent.AbstractExecutorService.invokeAny(AbstractExecutorService.java:230) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$4.call(ScheduledExecutorServiceWrapper.java:185) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$15.call(ScheduledExecutorServiceWrapper.java:446) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.RWLock.runReadOperation(RWLock.java:33) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.runUnlessShutdown(ScheduledExecutorServiceWrapper.java:443) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.invokeAny(ScheduledExecutorServiceWrapper.java:180) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListener(BlueprintEventDispatcher.java:195) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListeners(BlueprintEventDispatcher.java:178) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.blueprintEvent(BlueprintEventDispatcher.java:133) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:447) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:335) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:288) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:284) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:274) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422) > ~[?:?] > at > org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1180) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485) > ~[?:?] > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817) > ~[?:?] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2336) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?] > at > org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:165) > ~[?:?] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1160) > ~[?:?] > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:1041) > ~[?:?] > at >
[jira] [Resolved] (CAMEL-18405) camel-karaf - Camel-file ResumeAware
[ https://issues.apache.org/jira/browse/CAMEL-18405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18405. - Resolution: Fixed Wait for the release > camel-karaf - Camel-file ResumeAware > > > Key: CAMEL-18405 > URL: https://issues.apache.org/jira/browse/CAMEL-18405 > Project: Camel > Issue Type: Bug >Affects Versions: 3.18.1 >Reporter: TARTIERE >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.18.2 > > > Unable to start application with routes listening for files. > java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: > org/apache/camel/resume/ResumeAware > at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?] > at java.util.concurrent.FutureTask.get(FutureTask.java:191) ~[?:?] > at > java.util.concurrent.AbstractExecutorService.doInvokeAny(AbstractExecutorService.java:199) > ~[?:?] > at > java.util.concurrent.AbstractExecutorService.invokeAny(AbstractExecutorService.java:230) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$4.call(ScheduledExecutorServiceWrapper.java:185) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$15.call(ScheduledExecutorServiceWrapper.java:446) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.RWLock.runReadOperation(RWLock.java:33) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.runUnlessShutdown(ScheduledExecutorServiceWrapper.java:443) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.invokeAny(ScheduledExecutorServiceWrapper.java:180) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListener(BlueprintEventDispatcher.java:195) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListeners(BlueprintEventDispatcher.java:178) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.blueprintEvent(BlueprintEventDispatcher.java:133) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:447) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:335) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:288) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:284) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:274) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422) > ~[?:?] > at > org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1180) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485) > ~[?:?] > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817) > ~[?:?] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2336) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?] > at > org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:165) > ~[?:?] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1160) > ~[?:?] > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:1041) > ~[?:?] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1069) > ~[?:?] > at >
[jira] [Resolved] (CAMEL-18448) camel-jbang - Capture number of reloads
[ https://issues.apache.org/jira/browse/CAMEL-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18448. - Resolution: Fixed > camel-jbang - Capture number of reloads > --- > > Key: CAMEL-18448 > URL: https://issues.apache.org/jira/browse/CAMEL-18448 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.19.0 > > > See CAMEL-18267 > We can capture how many times camel has reloaded and output that in the camel > cli > - context > - routes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18449) camel-spring-boot - platform-http implementation
[ https://issues.apache.org/jira/browse/CAMEL-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599044#comment-17599044 ] Claus Ibsen commented on CAMEL-18449: - Ah yeah it does not make sense for spring boot to have other implementations so you can add to the existing > camel-spring-boot - platform-http implementation > > > Key: CAMEL-18449 > URL: https://issues.apache.org/jira/browse/CAMEL-18449 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Affects Versions: 3.18.0 >Reporter: Federico Mariani >Priority: Major > Fix For: 3.19.0 > > Attachments: rest-post-consumer.zip > > > I was wondering if an implementation for platform-http can be provided in > camel-spring-boot platform-http-starter. Attached you can find a simple POC, > do you think it can be helpful/possible to have something like > _SpringBootPlatformHttpEngine_ implemented in camel-platform-http-starter? > In this way the > [camel-quarkus|https://camel.apache.org/camel-quarkus/2.11.x/reference/extensions/platform-http.html#_using_platform_http_via_camel_rest_dsl] > and camel-spring-boot behavior will be similar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18449) camel-spring-boot - platform-http implementation
[ https://issues.apache.org/jira/browse/CAMEL-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599043#comment-17599043 ] Federico Mariani commented on CAMEL-18449: -- Should I create another starter? or the implementation can be added in [camel-platform-http-starter|https://github.com/apache/camel-spring-boot/tree/main/components-starter/camel-platform-http-starter] ? > camel-spring-boot - platform-http implementation > > > Key: CAMEL-18449 > URL: https://issues.apache.org/jira/browse/CAMEL-18449 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Affects Versions: 3.18.0 >Reporter: Federico Mariani >Priority: Major > Fix For: 3.19.0 > > Attachments: rest-post-consumer.zip > > > I was wondering if an implementation for platform-http can be provided in > camel-spring-boot platform-http-starter. Attached you can find a simple POC, > do you think it can be helpful/possible to have something like > _SpringBootPlatformHttpEngine_ implemented in camel-platform-http-starter? > In this way the > [camel-quarkus|https://camel.apache.org/camel-quarkus/2.11.x/reference/extensions/platform-http.html#_using_platform_http_via_camel_rest_dsl] > and camel-spring-boot behavior will be similar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18449) camel-spring-boot - platform-http implementation
[ https://issues.apache.org/jira/browse/CAMEL-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599040#comment-17599040 ] Claus Ibsen commented on CAMEL-18449: - And using servlet is a good way. You are welcome to if you can send a PR with the starter added to the codebase in the main branch of camel-spring-boot, then we can get this into 3.19 release. > camel-spring-boot - platform-http implementation > > > Key: CAMEL-18449 > URL: https://issues.apache.org/jira/browse/CAMEL-18449 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Affects Versions: 3.18.0 >Reporter: Federico Mariani >Priority: Major > Fix For: 3.19.0 > > Attachments: rest-post-consumer.zip > > > I was wondering if an implementation for platform-http can be provided in > camel-spring-boot platform-http-starter. Attached you can find a simple POC, > do you think it can be helpful/possible to have something like > _SpringBootPlatformHttpEngine_ implemented in camel-platform-http-starter? > In this way the > [camel-quarkus|https://camel.apache.org/camel-quarkus/2.11.x/reference/extensions/platform-http.html#_using_platform_http_via_camel_rest_dsl] > and camel-spring-boot behavior will be similar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18449) camel-spring-boot - platform-http implementation
[ https://issues.apache.org/jira/browse/CAMEL-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599039#comment-17599039 ] Claus Ibsen commented on CAMEL-18449: - Yes this is a good idea, we have ticket CAMEL-17852 about this too. Thanks for jumping on this feature. > camel-spring-boot - platform-http implementation > > > Key: CAMEL-18449 > URL: https://issues.apache.org/jira/browse/CAMEL-18449 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Affects Versions: 3.18.0 >Reporter: Federico Mariani >Priority: Major > Attachments: rest-post-consumer.zip > > > I was wondering if an implementation for platform-http can be provided in > camel-spring-boot platform-http-starter. Attached you can find a simple POC, > do you think it can be helpful/possible to have something like > _SpringBootPlatformHttpEngine_ implemented in camel-platform-http-starter? > In this way the > [camel-quarkus|https://camel.apache.org/camel-quarkus/2.11.x/reference/extensions/platform-http.html#_using_platform_http_via_camel_rest_dsl] > and camel-spring-boot behavior will be similar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18449) camel-spring-boot - platform-http implementation
[ https://issues.apache.org/jira/browse/CAMEL-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18449: Fix Version/s: 3.19.0 > camel-spring-boot - platform-http implementation > > > Key: CAMEL-18449 > URL: https://issues.apache.org/jira/browse/CAMEL-18449 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Affects Versions: 3.18.0 >Reporter: Federico Mariani >Priority: Major > Fix For: 3.19.0 > > Attachments: rest-post-consumer.zip > > > I was wondering if an implementation for platform-http can be provided in > camel-spring-boot platform-http-starter. Attached you can find a simple POC, > do you think it can be helpful/possible to have something like > _SpringBootPlatformHttpEngine_ implemented in camel-platform-http-starter? > In this way the > [camel-quarkus|https://camel.apache.org/camel-quarkus/2.11.x/reference/extensions/platform-http.html#_using_platform_http_via_camel_rest_dsl] > and camel-spring-boot behavior will be similar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18449) camel-spring-boot - platform-http implementation
Federico Mariani created CAMEL-18449: Summary: camel-spring-boot - platform-http implementation Key: CAMEL-18449 URL: https://issues.apache.org/jira/browse/CAMEL-18449 Project: Camel Issue Type: New Feature Components: camel-spring-boot Affects Versions: 3.18.0 Reporter: Federico Mariani Attachments: rest-post-consumer.zip I was wondering if an implementation for platform-http can be provided in camel-spring-boot platform-http-starter. Attached you can find a simple POC, do you think it can be helpful/possible to have something like _SpringBootPlatformHttpEngine_ implemented in camel-platform-http-starter? In this way the [camel-quarkus|https://camel.apache.org/camel-quarkus/2.11.x/reference/extensions/platform-http.html#_using_platform_http_via_camel_rest_dsl] and camel-spring-boot behavior will be similar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (CAMEL-18405) camel-karaf - Camel-file ResumeAware
[ https://issues.apache.org/jira/browse/CAMEL-18405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] TARTIERE reopened CAMEL-18405: -- Hello, We have changed the manifest file. Our manifest in bundle contain the line as mentionned in [commit|https://github.com/apache/camel/commit/159beeb85c9fcc7547c15a41acd8386fc16c5e77#diff-e3281f84bec82da1a03295ec0dee2bfb4e28215a81f1d6a0cbc054c8b8079542] "Private-Package: !*" We have the same error: Caused by: java.lang.ClassNotFoundException: org.apache.camel.resume.ResumeAware not found by org.apache.camel.camel-file [81] > camel-karaf - Camel-file ResumeAware > > > Key: CAMEL-18405 > URL: https://issues.apache.org/jira/browse/CAMEL-18405 > Project: Camel > Issue Type: Bug >Affects Versions: 3.18.1 >Reporter: TARTIERE >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.18.2 > > > Unable to start application with routes listening for files. > java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: > org/apache/camel/resume/ResumeAware > at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?] > at java.util.concurrent.FutureTask.get(FutureTask.java:191) ~[?:?] > at > java.util.concurrent.AbstractExecutorService.doInvokeAny(AbstractExecutorService.java:199) > ~[?:?] > at > java.util.concurrent.AbstractExecutorService.invokeAny(AbstractExecutorService.java:230) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$4.call(ScheduledExecutorServiceWrapper.java:185) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$15.call(ScheduledExecutorServiceWrapper.java:446) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.RWLock.runReadOperation(RWLock.java:33) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.runUnlessShutdown(ScheduledExecutorServiceWrapper.java:443) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.invokeAny(ScheduledExecutorServiceWrapper.java:180) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListener(BlueprintEventDispatcher.java:195) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListeners(BlueprintEventDispatcher.java:178) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.blueprintEvent(BlueprintEventDispatcher.java:133) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:447) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:335) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:288) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:284) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:274) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422) > ~[?:?] > at > org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1180) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485) > ~[?:?] > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817) > ~[?:?] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2336) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?] > at > org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:165) > ~[?:?] > at >
[jira] [Updated] (CAMEL-18448) camel-jbang - Capture number of reloads
[ https://issues.apache.org/jira/browse/CAMEL-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18448: Description: See CAMEL-18267 We can capture how many times camel has reloaded and output that in the camel cli - context - routes was: See CAMEL-18267 We can capture how many times camel has reloaded and output that in the camel cli > camel-jbang - Capture number of reloads > --- > > Key: CAMEL-18448 > URL: https://issues.apache.org/jira/browse/CAMEL-18448 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.19.0 > > > See CAMEL-18267 > We can capture how many times camel has reloaded and output that in the camel > cli > - context > - routes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18448) camel-jbang - Capture number of reloads
Claus Ibsen created CAMEL-18448: --- Summary: camel-jbang - Capture number of reloads Key: CAMEL-18448 URL: https://issues.apache.org/jira/browse/CAMEL-18448 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.19.0 See CAMEL-18267 We can capture how many times camel has reloaded and output that in the camel cli -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18448) camel-jbang - Capture number of reloads
[ https://issues.apache.org/jira/browse/CAMEL-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18448: Priority: Minor (was: Major) > camel-jbang - Capture number of reloads > --- > > Key: CAMEL-18448 > URL: https://issues.apache.org/jira/browse/CAMEL-18448 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.19.0 > > > See CAMEL-18267 > We can capture how many times camel has reloaded and output that in the camel > cli -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18267) Vault Support: Trigger a reload of properties from a particular Vault source based on events
[ https://issues.apache.org/jira/browse/CAMEL-18267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18267: Issue Type: New Feature (was: Improvement) > Vault Support: Trigger a reload of properties from a particular Vault source > based on events > > > Key: CAMEL-18267 > URL: https://issues.apache.org/jira/browse/CAMEL-18267 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > In case of rotation, update, patch etc. We need to trigger a reload. > This might be a service running with the properties source or something we > could enable on-demand. > In this way we could react to events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18267) Vault Support: Trigger a reload of properties from a particular Vault source based on events
[ https://issues.apache.org/jira/browse/CAMEL-18267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598897#comment-17598897 ] Claus Ibsen commented on CAMEL-18267: - Let me get started and add some API in camel-core we can use from the vaults > Vault Support: Trigger a reload of properties from a particular Vault source > based on events > > > Key: CAMEL-18267 > URL: https://issues.apache.org/jira/browse/CAMEL-18267 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > In case of rotation, update, patch etc. We need to trigger a reload. > This might be a service running with the properties source or something we > could enable on-demand. > In this way we could react to events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18267) Vault Support: Trigger a reload of properties from a particular Vault source based on events
[ https://issues.apache.org/jira/browse/CAMEL-18267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18267: Fix Version/s: 3.19.0 (was: 3.x) > Vault Support: Trigger a reload of properties from a particular Vault source > based on events > > > Key: CAMEL-18267 > URL: https://issues.apache.org/jira/browse/CAMEL-18267 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > In case of rotation, update, patch etc. We need to trigger a reload. > This might be a service running with the properties source or something we > could enable on-demand. > In this way we could react to events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18267) Vault Support: Trigger a reload of properties from a particular Vault source based on events
[ https://issues.apache.org/jira/browse/CAMEL-18267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18267: Component/s: camel-core > Vault Support: Trigger a reload of properties from a particular Vault source > based on events > > > Key: CAMEL-18267 > URL: https://issues.apache.org/jira/browse/CAMEL-18267 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > In case of rotation, update, patch etc. We need to trigger a reload. > This might be a service running with the properties source or something we > could enable on-demand. > In this way we could react to events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18440) camel-core - Stopping routes via management APIs should not make health-check fail
[
https://issues.apache.org/jira/browse/CAMEL-18440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18440.
-
Resolution: Won't Fix
After some more thought then this is more correct in a cloud environment where
your app is supposed to run autonomous and stopping routes is not a practice.
> camel-core - Stopping routes via management APIs should not make health-check
> fail
> --
>
> Key: CAMEL-18440
> URL: https://issues.apache.org/jira/browse/CAMEL-18440
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, jmx
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.19.0
>
>
> If you stop routes via JMX or some other management APIs then the
> health-check is reporting this as down.
> Here we have stopped the chuck app and 0 out of 3 routes is running and the
> ready is 0/6 (eg down)
> {code}
> PID NAMECAMELPLATFORM READY STATUSAGEROUTE
> TOTAL FAILED INFLIGHT SINCE-LAST
> 64673 bar.yaml3.19.0-SNAPSHOT JBang 1/1 Running 28m11s1/1
> 1617 0 0 0s
> 64686 chuck.yaml 3.19.0-SNAPSHOT JBang 0/6 Running 28m9s0/3
> 224 2 0 15m25s
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18057) rest-dsl - Combine rest and linked route together as single route
[ https://issues.apache.org/jira/browse/CAMEL-18057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598811#comment-17598811 ] ncasaux commented on CAMEL-18057: - Hello, I think it would be usefull to be able to set the routeId of the REST route itself. In case we have a REST route which could call let's say 3 other routes, it would not make sense to regroup them in a single route, and in that case, setting the routeId of the REST route makes sense. > rest-dsl - Combine rest and linked route together as single route > - > > Key: CAMEL-18057 > URL: https://issues.apache.org/jira/browse/CAMEL-18057 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > rest-dsl and routes are separated today in the model. We can look at adding > an option to rest-dsl that allows to combine them into a single route. > This makes it easier for monitoring and tracing systems to deal with just 1 > route instead of 2. > In previous versions of Camel users could embed routes directly in rest-dsl, > but its not possible anymore. > However the intent is the same, they have an api and may want this as 1 route > by Camel. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18447) Camel-pubsub: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed with real account
[
https://issues.apache.org/jira/browse/CAMEL-18447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Ondrusek updated CAMEL-18447:
--
Description:
During fixation of [https://github.com/apache/camel-quarkus/issues/4062] I
noticed regular exceptions shown only with real account (not with emulater):
{code:java}
Suppressed: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed
at
com.google.api.gax.rpc.ApiExceptions.callAndTranslateApiException(ApiExceptions.java:57)
at
com.google.api.gax.rpc.UnaryCallable.call(UnaryCallable.java:112) {code}
Exception shows that some connections is closed during the acking mechanism. It
should be fixed. (To reproduce issue run i.e. run test from CQ with real
account GooglePubsubTest#pubsubTopicProduceConsume)
was:
During fixation of [https://github.com/apache/camel-quarkus/issues/4062] I
noticed regular exceptions shown only with real account (not with emulater):
{code:java}
Suppressed: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed
at
com.google.api.gax.rpc.ApiExceptions.callAndTranslateApiException(ApiExceptions.java:57)
at
com.google.api.gax.rpc.UnaryCallable.call(UnaryCallable.java:112) {code}
Exception shows that some connections is closed during the acking mechanism. It
should be fixed. (To reproduce issue run i.e. test from CQ with lreal account
GooglePubsubTest#pubsubTopicProduceConsume)
> Camel-pubsub: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task
> failed with real account
> ---
>
> Key: CAMEL-18447
> URL: https://issues.apache.org/jira/browse/CAMEL-18447
> Project: Camel
> Issue Type: Bug
> Components: camel-google-pubsub
>Affects Versions: 3.18.2, 3.19.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Major
>
> During fixation of [https://github.com/apache/camel-quarkus/issues/4062] I
> noticed regular exceptions shown only with real account (not with emulater):
>
> {code:java}
> Suppressed: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task
> failed at
> com.google.api.gax.rpc.ApiExceptions.callAndTranslateApiException(ApiExceptions.java:57)
> at
> com.google.api.gax.rpc.UnaryCallable.call(UnaryCallable.java:112) {code}
> Exception shows that some connections is closed during the acking mechanism.
> It should be fixed. (To reproduce issue run i.e. run test from CQ with real
> account GooglePubsubTest#pubsubTopicProduceConsume)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18447) Camel-pubsub: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed with real account
Jiri Ondrusek created CAMEL-18447:
-
Summary: Camel-pubsub: com.google.api.gax.rpc.AsyncTaskException:
Asynchronous task failed with real account
Key: CAMEL-18447
URL: https://issues.apache.org/jira/browse/CAMEL-18447
Project: Camel
Issue Type: Bug
Components: camel-google-pubsub
Affects Versions: 3.18.2, 3.19.0
Reporter: Jiri Ondrusek
Assignee: Jiri Ondrusek
During fixation of [https://github.com/apache/camel-quarkus/issues/4062] I
noticed regular exceptions shown only with real account (not with emulater):
{code:java}
Suppressed: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed
at
com.google.api.gax.rpc.ApiExceptions.callAndTranslateApiException(ApiExceptions.java:57)
at
com.google.api.gax.rpc.UnaryCallable.call(UnaryCallable.java:112) {code}
Exception shows that some connections is closed during the acking mechanism. It
should be fixed. (To reproduce issue run i.e. test from CQ with lreal account
GooglePubsubTest#pubsubTopicProduceConsume)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18446) Failure in adviced route in unit test
[
https://issues.apache.org/jira/browse/CAMEL-18446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598782#comment-17598782
]
Claus Ibsen commented on CAMEL-18446:
-
See CAMEL-18443
> Failure in adviced route in unit test
> -
>
> Key: CAMEL-18446
> URL: https://issues.apache.org/jira/browse/CAMEL-18446
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 3.18.1
>Reporter: Vincent Paturet
>Priority: Major
>
> We experience a regression in unit tests when upgrading from Camel 3.18.0 to
> Camel 3.18.1:
> Example project: [https://github.com/vpaturet/test-advice-unit-test]
> The test passes with Camel 3.18.0 and fails with Camel 3.18.1
>
>
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> testedRoute at: >>> DoTry[[To[mock:testedSubRoute1],
> DoFinally[[To[direct:testedSubRoute2] <<< in route:
> Route(testedRoute)[From[direct:testedRoute] -> [DoTry[[To[mo... because of
> Multiple finally clauses added: DoFinally[[To[direct:testedSubRoute2]]] and
> DoFinally[[To[direct:testedSubRoute2]]] at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:240) at
> org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:74) at
> org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:862)
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:750)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2947)
> at org.apache.camel.support.service.BaseService.init(BaseService.java:83) at
> org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2630)
> at org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2649)
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:262)
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:119)
> at org.test.route.MyRouteTest.testBugAdvice(MyRouteTest.java:38){code}
>
> Route:
>
> {code:java}
> @Component
> public class MyRouteBuilder extends RouteBuilder {
> @Override
> public void configure() {
> from("direct:testedRoute")
> .doTry()
> .to("direct:testedSubRoute1")
> .doFinally()
> .to("direct:testedSubRoute2")
> .end()
> .routeId("testedRoute");
> from("direct:testedSubRoute1")
> .log(LoggingLevel.INFO, "testedSubRoute1")
> .routeId("testedSubRoute1");
> from("direct:testedSubRoute2")
> .log(LoggingLevel.INFO, "testedSubRoute2")
> .routeId("testedSubRoute2");
> }
> }{code}
>
> Unit test:
>
> {code:java}
> @CamelSpringBootTest
> @UseAdviceWith
> @SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.DEFINED_PORT,
> classes = TestApp.class)
> class MyRouteTest {
> @Autowired
> ModelCamelContext context;
> @Produce("direct:testedRoute")
> protected ProducerTemplate testedRoute;
> @EndpointInject("mock:testedSubRoute1")
> protected MockEndpoint testedSubRoute1;
> @Test
> void testBugAdvice() throws Exception {
> AdviceWith.adviceWith(context, "testedRoute", a ->
> a.weaveByToUri("direct:testedSubRoute1").replace().to("mock:testedSubRoute1"));
> testedSubRoute1.expectedMessageCount(1);
> context.start();
> testedRoute.requestBody(null);
> testedSubRoute1.assertIsSatisfied();
> }
> }{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18446) Failure in adviced route in unit test
[
https://issues.apache.org/jira/browse/CAMEL-18446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18446.
-
Resolution: Duplicate
> Failure in adviced route in unit test
> -
>
> Key: CAMEL-18446
> URL: https://issues.apache.org/jira/browse/CAMEL-18446
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 3.18.1
>Reporter: Vincent Paturet
>Priority: Major
>
> We experience a regression in unit tests when upgrading from Camel 3.18.0 to
> Camel 3.18.1:
> Example project: [https://github.com/vpaturet/test-advice-unit-test]
> The test passes with Camel 3.18.0 and fails with Camel 3.18.1
>
>
> {code:java}
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> testedRoute at: >>> DoTry[[To[mock:testedSubRoute1],
> DoFinally[[To[direct:testedSubRoute2] <<< in route:
> Route(testedRoute)[From[direct:testedRoute] -> [DoTry[[To[mo... because of
> Multiple finally clauses added: DoFinally[[To[direct:testedSubRoute2]]] and
> DoFinally[[To[direct:testedSubRoute2]]] at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:240) at
> org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:74) at
> org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:862)
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:750)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2947)
> at org.apache.camel.support.service.BaseService.init(BaseService.java:83) at
> org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2630)
> at org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2649)
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:262)
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:119)
> at org.test.route.MyRouteTest.testBugAdvice(MyRouteTest.java:38){code}
>
> Route:
>
> {code:java}
> @Component
> public class MyRouteBuilder extends RouteBuilder {
> @Override
> public void configure() {
> from("direct:testedRoute")
> .doTry()
> .to("direct:testedSubRoute1")
> .doFinally()
> .to("direct:testedSubRoute2")
> .end()
> .routeId("testedRoute");
> from("direct:testedSubRoute1")
> .log(LoggingLevel.INFO, "testedSubRoute1")
> .routeId("testedSubRoute1");
> from("direct:testedSubRoute2")
> .log(LoggingLevel.INFO, "testedSubRoute2")
> .routeId("testedSubRoute2");
> }
> }{code}
>
> Unit test:
>
> {code:java}
> @CamelSpringBootTest
> @UseAdviceWith
> @SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.DEFINED_PORT,
> classes = TestApp.class)
> class MyRouteTest {
> @Autowired
> ModelCamelContext context;
> @Produce("direct:testedRoute")
> protected ProducerTemplate testedRoute;
> @EndpointInject("mock:testedSubRoute1")
> protected MockEndpoint testedSubRoute1;
> @Test
> void testBugAdvice() throws Exception {
> AdviceWith.adviceWith(context, "testedRoute", a ->
> a.weaveByToUri("direct:testedSubRoute1").replace().to("mock:testedSubRoute1"));
> testedSubRoute1.expectedMessageCount(1);
> context.start();
> testedRoute.requestBody(null);
> testedSubRoute1.assertIsSatisfied();
> }
> }{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18446) Failure in adviced route in unit test
[
https://issues.apache.org/jira/browse/CAMEL-18446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Paturet updated CAMEL-18446:
Description:
We experience a regression in unit tests when upgrading from Camel 3.18.0 to
Camel 3.18.1:
Example project: [https://github.com/vpaturet/test-advice-unit-test]
The test passes with Camel 3.18.0 and fails with Camel 3.18.1
{code:java}
org.apache.camel.FailedToCreateRouteException: Failed to create route
testedRoute at: >>> DoTry[[To[mock:testedSubRoute1],
DoFinally[[To[direct:testedSubRoute2] <<< in route:
Route(testedRoute)[From[direct:testedRoute] -> [DoTry[[To[mo... because of
Multiple finally clauses added: DoFinally[[To[direct:testedSubRoute2]]] and
DoFinally[[To[direct:testedSubRoute2]]] at
org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:240) at
org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:74) at
org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:862)
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:750)
at
org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2947)
at org.apache.camel.support.service.BaseService.init(BaseService.java:83) at
org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2630)
at org.apache.camel.support.service.BaseService.start(BaseService.java:111) at
org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2649)
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:262)
at
org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:119)
at org.test.route.MyRouteTest.testBugAdvice(MyRouteTest.java:38){code}
Route:
{code:java}
@Component
public class MyRouteBuilder extends RouteBuilder {
@Override
public void configure() {
from("direct:testedRoute")
.doTry()
.to("direct:testedSubRoute1")
.doFinally()
.to("direct:testedSubRoute2")
.end()
.routeId("testedRoute");
from("direct:testedSubRoute1")
.log(LoggingLevel.INFO, "testedSubRoute1")
.routeId("testedSubRoute1");
from("direct:testedSubRoute2")
.log(LoggingLevel.INFO, "testedSubRoute2")
.routeId("testedSubRoute2");
}
}{code}
Unit test:
{code:java}
@CamelSpringBootTest
@UseAdviceWith
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.DEFINED_PORT,
classes = TestApp.class)
class MyRouteTest {
@Autowired
ModelCamelContext context;
@Produce("direct:testedRoute")
protected ProducerTemplate testedRoute;
@EndpointInject("mock:testedSubRoute1")
protected MockEndpoint testedSubRoute1;
@Test
void testBugAdvice() throws Exception {
AdviceWith.adviceWith(context, "testedRoute", a ->
a.weaveByToUri("direct:testedSubRoute1").replace().to("mock:testedSubRoute1"));
testedSubRoute1.expectedMessageCount(1);
context.start();
testedRoute.requestBody(null);
testedSubRoute1.assertIsSatisfied();
}
}{code}
was:
We experience a regression in unit tests when upgrading from Camel 3.18.0 to
Camel 3.18.1:
Example project: [https://github.com/vpaturet/test-advice-unit-test]
The test passes with Camel 3.18.0 and fails with Camel 3.18.1
{{}}
{code:java}
org.apache.camel.FailedToCreateRouteException: Failed to create route
testedRoute at: >>> DoTry[[To[mock:testedSubRoute1],
DoFinally[[To[direct:testedSubRoute2] <<< in route:
Route(testedRoute)[From[direct:testedRoute] -> [DoTry[[To[mo... because of
Multiple finally clauses added: DoFinally[[To[direct:testedSubRoute2]]] and
DoFinally[[To[direct:testedSubRoute2]]] at
org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:240) at
org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:74) at
org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:862)
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:750)
at
org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2947)
at org.apache.camel.support.service.BaseService.init(BaseService.java:83) at
org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2630)
at org.apache.camel.support.service.BaseService.start(BaseService.java:111) at
org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2649)
at
[jira] [Created] (CAMEL-18446) Failure in adviced route in unit test
Vincent Paturet created CAMEL-18446:
---
Summary: Failure in adviced route in unit test
Key: CAMEL-18446
URL: https://issues.apache.org/jira/browse/CAMEL-18446
Project: Camel
Issue Type: Bug
Components: camel-test
Affects Versions: 3.18.1
Reporter: Vincent Paturet
We experience a regression in unit tests when upgrading from Camel 3.18.0 to
Camel 3.18.1:
Example project: [https://github.com/vpaturet/test-advice-unit-test]
The test passes with Camel 3.18.0 and fails with Camel 3.18.1
{{}}
{code:java}
org.apache.camel.FailedToCreateRouteException: Failed to create route
testedRoute at: >>> DoTry[[To[mock:testedSubRoute1],
DoFinally[[To[direct:testedSubRoute2] <<< in route:
Route(testedRoute)[From[direct:testedRoute] -> [DoTry[[To[mo... because of
Multiple finally clauses added: DoFinally[[To[direct:testedSubRoute2]]] and
DoFinally[[To[direct:testedSubRoute2]]] at
org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:240) at
org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:74) at
org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:862)
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:750)
at
org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2947)
at org.apache.camel.support.service.BaseService.init(BaseService.java:83) at
org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2630)
at org.apache.camel.support.service.BaseService.start(BaseService.java:111) at
org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2649)
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:262)
at
org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:119)
at org.test.route.MyRouteTest.testBugAdvice(MyRouteTest.java:38){code}
{{}}
Route:
{{}}
{{}}
{code:java}
@Component
public class MyRouteBuilder extends RouteBuilder {
@Override
public void configure() {
from("direct:testedRoute")
.doTry()
.to("direct:testedSubRoute1")
.doFinally()
.to("direct:testedSubRoute2")
.end()
.routeId("testedRoute");
from("direct:testedSubRoute1")
.log(LoggingLevel.INFO, "testedSubRoute1")
.routeId("testedSubRoute1");
from("direct:testedSubRoute2")
.log(LoggingLevel.INFO, "testedSubRoute2")
.routeId("testedSubRoute2");
}
}{code}
{{}}
Unit test:
{{}}
{{}}
{{}}
{code:java}
@CamelSpringBootTest
@UseAdviceWith
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.DEFINED_PORT,
classes = TestApp.class)
class MyRouteTest {
@Autowired
ModelCamelContext context;
@Produce("direct:testedRoute")
protected ProducerTemplate testedRoute;
@EndpointInject("mock:testedSubRoute1")
protected MockEndpoint testedSubRoute1;
@Test
void testBugAdvice() throws Exception {
AdviceWith.adviceWith(context, "testedRoute", a ->
a.weaveByToUri("direct:testedSubRoute1").replace().to("mock:testedSubRoute1"));
testedSubRoute1.expectedMessageCount(1);
context.start();
testedRoute.requestBody(null);
testedSubRoute1.assertIsSatisfied();
}
}{code}
{{}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
