[jira] [Resolved] (CAMEL-18302) Issue with special character % in the REST service password
[ https://issues.apache.org/jira/browse/CAMEL-18302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18302. - Resolution: Not A Bug > Issue with special character % in the REST service password > --- > > Key: CAMEL-18302 > URL: https://issues.apache.org/jira/browse/CAMEL-18302 > Project: Camel > Issue Type: Bug > Components: camel-http >Affects Versions: 3.6.0 >Reporter: Srikhar Venumbaka >Priority: Minor > > The Rest service connectivity is failing using the camel HTTP component when > the REST service password has a special character like %. e.g. "test%hello". > It seems the camel HTTP component API internally converting the special > characters in the password to URL encoded characters and in the conversion, > it is incorrectly converting the % character to %2525. In the example, as > given above, it is converting the password to "test%2525hello". > We are using camel version 3.6.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18302) Issue with special character % in the REST service password
[ https://issues.apache.org/jira/browse/CAMEL-18302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17571194#comment-17571194 ] Claus Ibsen commented on CAMEL-18302: - See this FAQ https://camel.apache.org/manual/faq/how-do-i-configure-password-options-on-camel-endpoints-without-the-value-being-encoded.html > Issue with special character % in the REST service password > --- > > Key: CAMEL-18302 > URL: https://issues.apache.org/jira/browse/CAMEL-18302 > Project: Camel > Issue Type: Bug > Components: camel-http >Affects Versions: 3.6.0 >Reporter: Srikhar Venumbaka >Priority: Minor > > The Rest service connectivity is failing using the camel HTTP component when > the REST service password has a special character like %. e.g. "test%hello". > It seems the camel HTTP component API internally converting the special > characters in the password to URL encoded characters and in the conversion, > it is incorrectly converting the % character to %2525. In the example, as > given above, it is converting the password to "test%2525hello". > We are using camel version 3.6.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18302) Issue with special character % in the REST service password
Srikhar Venumbaka created CAMEL-18302: - Summary: Issue with special character % in the REST service password Key: CAMEL-18302 URL: https://issues.apache.org/jira/browse/CAMEL-18302 Project: Camel Issue Type: Bug Components: camel-http Affects Versions: 3.6.0 Reporter: Srikhar Venumbaka The Rest service connectivity is failing using the camel HTTP component when the REST service password has a special character like %. e.g. "test%hello". It seems the camel HTTP component API internally converting the special characters in the password to URL encoded characters and in the conversion, it is incorrectly converting the % character to %2525. In the example, as given above, it is converting the password to "test%2525hello". We are using camel version 3.6.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18294) upgrade to spring boot 2.7.2
[ https://issues.apache.org/jira/browse/CAMEL-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17571191#comment-17571191 ] Claus Ibsen commented on CAMEL-18294: - Thanks we need PRs for the 3.18.x branch > upgrade to spring boot 2.7.2 > > > Key: CAMEL-18294 > URL: https://issues.apache.org/jira/browse/CAMEL-18294 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 3.18.0 >Reporter: Federico Mariani >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > https://github.com/spring-projects/spring-boot/releases/tag/v2.7.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18294) upgrade to spring boot 2.7.2
[ https://issues.apache.org/jira/browse/CAMEL-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18294: Component/s: camel-spring-boot > upgrade to spring boot 2.7.2 > > > Key: CAMEL-18294 > URL: https://issues.apache.org/jira/browse/CAMEL-18294 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Affects Versions: 3.18.0 >Reporter: Federico Mariani >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > https://github.com/spring-projects/spring-boot/releases/tag/v2.7.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18292) Datasonnet expression should not fail if body is empty
[
https://issues.apache.org/jira/browse/CAMEL-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18292.
-
Fix Version/s: 3.18.1
Resolution: Fixed
> Datasonnet expression should not fail if body is empty
> --
>
> Key: CAMEL-18292
> URL: https://issues.apache.org/jira/browse/CAMEL-18292
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 3.18.0
>Reporter: Eugene Berman
>Priority: Minor
> Fix For: 3.18.1, 3.19.0
>
>
> Sometimes the body of the message is empty (e.g. when handling the GET
> request), and it causes Datasonnet expression to fail and throw an exception:
> {{ujson.IncompleteParseException: exhausted input}}
> The fix would be to internally generate an empty object matching the
> Datasonnet input media type (e.g. {} if the body media type is
> {{application/json}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18301) Component for Sharepoint Lists (Office 365)
Adrien SALES created CAMEL-18301: Summary: Component for Sharepoint Lists (Office 365) Key: CAMEL-18301 URL: https://issues.apache.org/jira/browse/CAMEL-18301 Project: Camel Issue Type: New Feature Reporter: Adrien SALES h1. Context more and more users store data in Sharepoint LIsts on sharepointOnline. The tricky part comes when we are asked to perform integrations with these DATAs. They are served as REST APIs, OIDC and oAUth options are available but you be awesome to be able to grab these datas as easily as we can with the JDBC component for example. Our main usecase by the way is to copy data from SharepointLists to JDBC data sources... or Kafka topics. h1. Feature request * Add the Microsoft Sharepoint List component to core components -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18300) Google storage component does not set metadata appropriately
Jeff created CAMEL-18300:
Summary: Google storage component does not set metadata
appropriately
Key: CAMEL-18300
URL: https://issues.apache.org/jira/browse/CAMEL-18300
Project: Camel
Issue Type: Bug
Reporter: Jeff
Attachments: Screen Shot 2022-07-25 at 6.03.25 PM.png
The
[docs|https://camel.apache.org/components/3.18.x/google-storage-component.html#_configuring_component_options]
indicate that the CamelGoogleCloudStorageContentType header sets the content
type of the object. However, this is not the case. The
GoogleCloudStorageProducer class does set metadata, but it does so using the
setMetadata method of BlobInfo, which only sets custom metadata. So setting the
header like so:
.setHeader('CamelGoogleCloudStorageContentType', constant('text/plain'))
results in a blob stored with the attached metadata, where the Content-Type is
the default application/octet-stream, and the Custom Metadata includes that set
on the header.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18262) Templated route exception handling not working
[
https://issues.apache.org/jira/browse/CAMEL-18262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570978#comment-17570978
]
Claus Ibsen commented on CAMEL-18262:
-
Thanks for reporting and the PR
> Templated route exception handling not working
> --
>
> Key: CAMEL-18262
> URL: https://issues.apache.org/jira/browse/CAMEL-18262
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
> Environment: * Camel 3.18.0
> * Spring-boot 2.7.1
> * OpenJDK 11
> * Maven 3.5.0
>Reporter: j vh
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
> Attachments: camel-template-so.7z, camel-template-so.zip
>
>
> Using Route Templates as described here in the Camel docs: [route-template,
> |https://camel.apache.org/manual/route-template.html]I cannot get any
> exception handling to work unless I define it within the class that is
> constructing the template itself.
> Specifically, trying to use global exception handling in the class that
> calls TemplatedRouteBuilder.builder() to build a route from my template.
> Expected exceptions are not caught.
> And there is no .onException() method implementation to customize the
> handling that could be called in the list of fluent methods starting with
> TemplatedRouteBuilder.build().
> I have already posted this, with my example code, in the Camel mailing list.
> Please have a look at the discussion here:
> [mail-archive|[https://lists.apache.org/thread/26kp2tpfbgj9mxpfdr106f36xyj51d7g]]
> This is the hi-level description from that mail article:
> {code:java}
> Hi-level overview:
> - 2 projects: 1 camel template base jar and 1 springboot camel application
> (that builds its route using the template from the other project).
> - the base jar builds a route template
> - the application jar builds a route using the template from the base jar
> - the desire here is to do some extra customization in the application (at
> templated-route creation time) to setup extra exception handling that is not
> included in the base template.
> - I have also tried to define global level exception handling using
> onException() in my application project's configure() method. But this is not
> catching anything either.
> {code}
> There is a overview of the code in the mail article as well. But I also have
> a simplified single spring-boot test project with junit that I can provide if
> needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18262) Templated route exception handling not working
[
https://issues.apache.org/jira/browse/CAMEL-18262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18262.
-
Resolution: Fixed
> Templated route exception handling not working
> --
>
> Key: CAMEL-18262
> URL: https://issues.apache.org/jira/browse/CAMEL-18262
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
> Environment: * Camel 3.18.0
> * Spring-boot 2.7.1
> * OpenJDK 11
> * Maven 3.5.0
>Reporter: j vh
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
> Attachments: camel-template-so.7z, camel-template-so.zip
>
>
> Using Route Templates as described here in the Camel docs: [route-template,
> |https://camel.apache.org/manual/route-template.html]I cannot get any
> exception handling to work unless I define it within the class that is
> constructing the template itself.
> Specifically, trying to use global exception handling in the class that
> calls TemplatedRouteBuilder.builder() to build a route from my template.
> Expected exceptions are not caught.
> And there is no .onException() method implementation to customize the
> handling that could be called in the list of fluent methods starting with
> TemplatedRouteBuilder.build().
> I have already posted this, with my example code, in the Camel mailing list.
> Please have a look at the discussion here:
> [mail-archive|[https://lists.apache.org/thread/26kp2tpfbgj9mxpfdr106f36xyj51d7g]]
> This is the hi-level description from that mail article:
> {code:java}
> Hi-level overview:
> - 2 projects: 1 camel template base jar and 1 springboot camel application
> (that builds its route using the template from the other project).
> - the base jar builds a route template
> - the application jar builds a route using the template from the base jar
> - the desire here is to do some extra customization in the application (at
> templated-route creation time) to setup extra exception handling that is not
> included in the base template.
> - I have also tried to define global level exception handling using
> onException() in my application project's configure() method. But this is not
> catching anything either.
> {code}
> There is a overview of the code in the mail article as well. But I also have
> a simplified single spring-boot test project with junit that I can provide if
> needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18262) Templated route exception handling not working
[
https://issues.apache.org/jira/browse/CAMEL-18262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18262:
Fix Version/s: 3.18.1
3.19.0
> Templated route exception handling not working
> --
>
> Key: CAMEL-18262
> URL: https://issues.apache.org/jira/browse/CAMEL-18262
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
> Environment: * Camel 3.18.0
> * Spring-boot 2.7.1
> * OpenJDK 11
> * Maven 3.5.0
>Reporter: j vh
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
> Attachments: camel-template-so.7z, camel-template-so.zip
>
>
> Using Route Templates as described here in the Camel docs: [route-template,
> |https://camel.apache.org/manual/route-template.html]I cannot get any
> exception handling to work unless I define it within the class that is
> constructing the template itself.
> Specifically, trying to use global exception handling in the class that
> calls TemplatedRouteBuilder.builder() to build a route from my template.
> Expected exceptions are not caught.
> And there is no .onException() method implementation to customize the
> handling that could be called in the list of fluent methods starting with
> TemplatedRouteBuilder.build().
> I have already posted this, with my example code, in the Camel mailing list.
> Please have a look at the discussion here:
> [mail-archive|[https://lists.apache.org/thread/26kp2tpfbgj9mxpfdr106f36xyj51d7g]]
> This is the hi-level description from that mail article:
> {code:java}
> Hi-level overview:
> - 2 projects: 1 camel template base jar and 1 springboot camel application
> (that builds its route using the template from the other project).
> - the base jar builds a route template
> - the application jar builds a route using the template from the base jar
> - the desire here is to do some extra customization in the application (at
> templated-route creation time) to setup extra exception handling that is not
> included in the base template.
> - I have also tried to define global level exception handling using
> onException() in my application project's configure() method. But this is not
> catching anything either.
> {code}
> There is a overview of the code in the mail article as well. But I also have
> a simplified single spring-boot test project with junit that I can provide if
> needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-15566) Create a AWS Cloudtrail component
[ https://issues.apache.org/jira/browse/CAMEL-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-15566: - Fix Version/s: 3.19.0 (was: 3.x) > Create a AWS Cloudtrail component > - > > Key: CAMEL-15566 > URL: https://issues.apache.org/jira/browse/CAMEL-15566 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-15965) Create a Azure Functions component
[ https://issues.apache.org/jira/browse/CAMEL-15965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-15965. -- Resolution: Won't Fix There is no Java SDK for this purpose, but we could use any http component. > Create a Azure Functions component > -- > > Key: CAMEL-15965 > URL: https://issues.apache.org/jira/browse/CAMEL-15965 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18179) Supporting camel-jira OSGi deployment
[ https://issues.apache.org/jira/browse/CAMEL-18179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18179. - Fix Version/s: 3.19.0 Resolution: Fixed > Supporting camel-jira OSGi deployment > - > > Key: CAMEL-18179 > URL: https://issues.apache.org/jira/browse/CAMEL-18179 > Project: Camel > Issue Type: Dependency upgrade > Components: karaf >Reporter: Xilai Dai >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 3.19.0 > > > There is no "camel-jira" karaf feature available in Camel 3, e.g in the > https://repo1.maven.org/maven2/org/apache/camel/karaf/apache-camel/3.17.0/apache-camel-3.17.0-features.xml > for sure currently the libraries from com.atlassian.jira are not in the maven > central but under here http://packages.atlassian.com/maven-external/, > also the libraries are plain jar, NOT OSGi bundle, > But it would be good to the users if we can make camel-jira OSGi-ready. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18279) When run 3.18.0 with Spring Boot, received java.io.FileNotFoundException: class path resource [.class] cannot be opened because it does not exist
[
https://issues.apache.org/jira/browse/CAMEL-18279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-18279:
---
Assignee: Claus Ibsen
> When run 3.18.0 with Spring Boot, received java.io.FileNotFoundException:
> class path resource [.class] cannot be opened because it does not exist
> -
>
> Key: CAMEL-18279
> URL: https://issues.apache.org/jira/browse/CAMEL-18279
> Project: Camel
> Issue Type: Bug
> Components: came-cxf
>Affects Versions: 3.18.0
>Reporter: John Yin
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
> Attachments: screenshot-camel.png
>
>
> After upgrading a springboot application to Camel 3.18.0, received the
> following exception during startup (Spring AutoConfiguration):
> java.io.FileNotFoundException: class path resource [.class] cannot be opened
> because it does not exist
> It is most likely related to a camel cxf class. A breakpoint in Spring
> AutoConfigurationSorter.java shows that the list of camel classNames to be
> configured contains an empty class name ("") between
> org.apache.camel.component.cxf.jaxrs.springboot.CxfRsComponentConverter and
> org.apache.camel.component.cxf.jaxws.springboot.CxfComponentAutoConfiguration.
> See the attached screenshots.
> !screenshot-camel.png!
> Here is the stacktrace:
> java.lang.IllegalStateException: Unable to read meta-data for class
> at
> org.springframework.boot.autoconfigure.AutoConfigurationSorter$AutoConfigurationClass.getAnnotationMetadata(AutoConfigurationSorter.java:237)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationSorter$AutoConfigurationClass.getOrder(AutoConfigurationSorter.java:208)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationSorter$AutoConfigurationClass.access$000(AutoConfigurationSorter.java:154)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationSorter.lambda$getInPriorityOrder$0(AutoConfigurationSorter.java:64)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355) ~[?:?]
> at java.util.TimSort.sort(TimSort.java:234) ~[?:?]
> at java.util.Arrays.sort(Arrays.java:1515) ~[?:?]
> at java.util.ArrayList.sort(ArrayList.java:1750) ~[?:?]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationSorter.getInPriorityOrder(AutoConfigurationSorter.java:62)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationImportSelector$AutoConfigurationGroup.sortAutoConfigurations(AutoConfigurationImportSelector.java:474)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationImportSelector$AutoConfigurationGroup.selectImports(AutoConfigurationImportSelector.java:459)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.context.annotation.ConfigurationClassParser$DeferredImportSelectorGrouping.getImports(ConfigurationClassParser.java:882)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.annotation.ConfigurationClassParser$DeferredImportSelectorGroupingHandler.processGroupImports(ConfigurationClassParser.java:809)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.annotation.ConfigurationClassParser$DeferredImportSelectorHandler.process(ConfigurationClassParser.java:780)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:193)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:331)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:247)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:311)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:112)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
>
[jira] [Resolved] (CAMEL-18279) When run 3.18.0 with Spring Boot, received java.io.FileNotFoundException: class path resource [.class] cannot be opened because it does not exist
[
https://issues.apache.org/jira/browse/CAMEL-18279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18279.
-
Fix Version/s: 3.18.1
3.19.0
Resolution: Fixed
Thanks fixed that spring.factories file
> When run 3.18.0 with Spring Boot, received java.io.FileNotFoundException:
> class path resource [.class] cannot be opened because it does not exist
> -
>
> Key: CAMEL-18279
> URL: https://issues.apache.org/jira/browse/CAMEL-18279
> Project: Camel
> Issue Type: Bug
> Components: came-cxf
>Affects Versions: 3.18.0
>Reporter: John Yin
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
> Attachments: screenshot-camel.png
>
>
> After upgrading a springboot application to Camel 3.18.0, received the
> following exception during startup (Spring AutoConfiguration):
> java.io.FileNotFoundException: class path resource [.class] cannot be opened
> because it does not exist
> It is most likely related to a camel cxf class. A breakpoint in Spring
> AutoConfigurationSorter.java shows that the list of camel classNames to be
> configured contains an empty class name ("") between
> org.apache.camel.component.cxf.jaxrs.springboot.CxfRsComponentConverter and
> org.apache.camel.component.cxf.jaxws.springboot.CxfComponentAutoConfiguration.
> See the attached screenshots.
> !screenshot-camel.png!
> Here is the stacktrace:
> java.lang.IllegalStateException: Unable to read meta-data for class
> at
> org.springframework.boot.autoconfigure.AutoConfigurationSorter$AutoConfigurationClass.getAnnotationMetadata(AutoConfigurationSorter.java:237)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationSorter$AutoConfigurationClass.getOrder(AutoConfigurationSorter.java:208)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationSorter$AutoConfigurationClass.access$000(AutoConfigurationSorter.java:154)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationSorter.lambda$getInPriorityOrder$0(AutoConfigurationSorter.java:64)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355) ~[?:?]
> at java.util.TimSort.sort(TimSort.java:234) ~[?:?]
> at java.util.Arrays.sort(Arrays.java:1515) ~[?:?]
> at java.util.ArrayList.sort(ArrayList.java:1750) ~[?:?]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationSorter.getInPriorityOrder(AutoConfigurationSorter.java:62)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationImportSelector$AutoConfigurationGroup.sortAutoConfigurations(AutoConfigurationImportSelector.java:474)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.boot.autoconfigure.AutoConfigurationImportSelector$AutoConfigurationGroup.selectImports(AutoConfigurationImportSelector.java:459)
> ~[spring-boot-autoconfigure-2.7.1.jar:2.7.1]
> at
> org.springframework.context.annotation.ConfigurationClassParser$DeferredImportSelectorGrouping.getImports(ConfigurationClassParser.java:882)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.annotation.ConfigurationClassParser$DeferredImportSelectorGroupingHandler.processGroupImports(ConfigurationClassParser.java:809)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.annotation.ConfigurationClassParser$DeferredImportSelectorHandler.process(ConfigurationClassParser.java:780)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:193)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:331)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:247)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:311)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
> org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:112)
> ~[spring-context-5.3.21.jar:5.3.21]
> at
>
[jira] [Assigned] (CAMEL-18299) camel-core - ResumeAdapter should use FactoryFinder to lookup implementations
[ https://issues.apache.org/jira/browse/CAMEL-18299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske reassigned CAMEL-18299: Assignee: Otavio Rodolfo Piske > camel-core - ResumeAdapter should use FactoryFinder to lookup implementations > - > > Key: CAMEL-18299 > URL: https://issues.apache.org/jira/browse/CAMEL-18299 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.19.0 > > > This class should generally be removed > org.apache.camel.support.resume.AdapterHelper > And how resume adapters is loaded should be done the standard Camel way using > FactoryFinder. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18299) camel-core - ResumeAdapter should use FactoryFinder to lookup implementations
[ https://issues.apache.org/jira/browse/CAMEL-18299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570896#comment-17570896 ] Otavio Rodolfo Piske commented on CAMEL-18299: -- [~davsclaus] thanks. I'm back from trips / PTO and I'll ping you this week on the chat for some pointers. I'm back at working on the resume bits. > camel-core - ResumeAdapter should use FactoryFinder to lookup implementations > - > > Key: CAMEL-18299 > URL: https://issues.apache.org/jira/browse/CAMEL-18299 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > This class should generally be removed > org.apache.camel.support.resume.AdapterHelper > And how resume adapters is loaded should be done the standard Camel way using > FactoryFinder. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18286) [Camel Spring Boot] camel-lra-starter needs camel-servlet-starter to work
[
https://issues.apache.org/jira/browse/CAMEL-18286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18286:
Fix Version/s: 3.18.1
> [Camel Spring Boot] camel-lra-starter needs camel-servlet-starter to work
> -
>
> Key: CAMEL-18286
> URL: https://issues.apache.org/jira/browse/CAMEL-18286
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot, camel-spring-boot-starters
>Affects Versions: 3.18.0
>Reporter: Marco Carletti
>Priority: Minor
> Fix For: 3.18.1, 3.19.0
>
> Attachments: saga-lra.zip
>
>
> Despite the
> [documentation|https://camel.apache.org/components/latest/eips/saga-eip.html#_using_the_lra_saga_service_in_spring_boot]
> says that the necessary dependencies are _camel-lra-starter_ and
> {_}camel-undertow-starter{_}, _camel-servlet-starter_ dependecy is necessary
> to make the saga works as expected.
> To reproduce the error:
> 1) start Narayana LRA Coordinator on port
> {code:bash}
> docker run --network host -e QUARKUS_HTTP_PORT= -e LOG_LEVEL=INFO --rm
> docker.io/jbosstm/lra-coordinator:latest
> {code}
> 2) start attached application
> {code:bash}
> mvn spring-boot:run
> {code}
>
> looking at the transactions at [http://localhost:/lra-coordinator/] we
> will see that all the transactions will be in "Closing" status, I expected no
> transactions here (all completed/compensated)
> The issue is that the REST endpoint are not exposed by the [camel-lra
> component|https://github.com/apache/camel/blob/main/components/camel-lra/src/main/java/org/apache/camel/service/lra/LRASagaRoutes.java#L45-L61]
> so the LRA cannot be completed by the LRA Coordinator (it is possible to see
> WARN log in the container log)
> The workaround is adding camel-servlet-starter dependency
> 3) start application with the dependency:
> {code:bash}
> mvn spring-boot:run -Pworkaround
> {code}
> now there are no "Closing" transactions at
> [http://localhost:/lra-coordinator/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18286) [Camel Spring Boot] camel-lra-starter needs camel-servlet-starter to work
[
https://issues.apache.org/jira/browse/CAMEL-18286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570895#comment-17570895
]
Claus Ibsen commented on CAMEL-18286:
-
You are welcome to send a PR against main branch for camel-spring-boot to add
the dependency in the pom.xml for the starter
> [Camel Spring Boot] camel-lra-starter needs camel-servlet-starter to work
> -
>
> Key: CAMEL-18286
> URL: https://issues.apache.org/jira/browse/CAMEL-18286
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot, camel-spring-boot-starters
>Affects Versions: 3.18.0
>Reporter: Marco Carletti
>Priority: Minor
> Fix For: 3.19.0
>
> Attachments: saga-lra.zip
>
>
> Despite the
> [documentation|https://camel.apache.org/components/latest/eips/saga-eip.html#_using_the_lra_saga_service_in_spring_boot]
> says that the necessary dependencies are _camel-lra-starter_ and
> {_}camel-undertow-starter{_}, _camel-servlet-starter_ dependecy is necessary
> to make the saga works as expected.
> To reproduce the error:
> 1) start Narayana LRA Coordinator on port
> {code:bash}
> docker run --network host -e QUARKUS_HTTP_PORT= -e LOG_LEVEL=INFO --rm
> docker.io/jbosstm/lra-coordinator:latest
> {code}
> 2) start attached application
> {code:bash}
> mvn spring-boot:run
> {code}
>
> looking at the transactions at [http://localhost:/lra-coordinator/] we
> will see that all the transactions will be in "Closing" status, I expected no
> transactions here (all completed/compensated)
> The issue is that the REST endpoint are not exposed by the [camel-lra
> component|https://github.com/apache/camel/blob/main/components/camel-lra/src/main/java/org/apache/camel/service/lra/LRASagaRoutes.java#L45-L61]
> so the LRA cannot be completed by the LRA Coordinator (it is possible to see
> WARN log in the container log)
> The workaround is adding camel-servlet-starter dependency
> 3) start application with the dependency:
> {code:bash}
> mvn spring-boot:run -Pworkaround
> {code}
> now there are no "Closing" transactions at
> [http://localhost:/lra-coordinator/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18299) camel-core - ResumeAdapter should use FactoryFinder to lookup implementations
[ https://issues.apache.org/jira/browse/CAMEL-18299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570894#comment-17570894 ] Claus Ibsen commented on CAMEL-18299: - Ping me on chat for pointers > camel-core - ResumeAdapter should use FactoryFinder to lookup implementations > - > > Key: CAMEL-18299 > URL: https://issues.apache.org/jira/browse/CAMEL-18299 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > This class should generally be removed > org.apache.camel.support.resume.AdapterHelper > And how resume adapters is loaded should be done the standard Camel way using > FactoryFinder. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18299) camel-core - ResumeAdapter should use FactoryFinder to lookup implementations
[ https://issues.apache.org/jira/browse/CAMEL-18299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570893#comment-17570893 ] Claus Ibsen commented on CAMEL-18299: - [~orpiske] at first look it seems that the adapter helper has its own way of loading a implementation class in Camel. Instead it should be done the standard way. And then you can use annotations on a class to mark it, and Camel generate the metafile itself automatic. > camel-core - ResumeAdapter should use FactoryFinder to lookup implementations > - > > Key: CAMEL-18299 > URL: https://issues.apache.org/jira/browse/CAMEL-18299 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > This class should generally be removed > org.apache.camel.support.resume.AdapterHelper > And how resume adapters is loaded should be done the standard Camel way using > FactoryFinder. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18299) camel-core - ResumeAdapter should use FactoryFinder to lookup implementations
Claus Ibsen created CAMEL-18299: --- Summary: camel-core - ResumeAdapter should use FactoryFinder to lookup implementations Key: CAMEL-18299 URL: https://issues.apache.org/jira/browse/CAMEL-18299 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 3.19.0 This class should generally be removed org.apache.camel.support.resume.AdapterHelper And how resume adapters is loaded should be done the standard Camel way using FactoryFinder. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18274) OSGi - camel-file: ClassNotFoundException because of Private-Package
[
https://issues.apache.org/jira/browse/CAMEL-18274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570887#comment-17570887
]
Claus Ibsen commented on CAMEL-18274:
-
Argh .. osgi bundle plugin generates wrong manifest :(
> OSGi - camel-file: ClassNotFoundException because of Private-Package
>
>
> Key: CAMEL-18274
> URL: https://issues.apache.org/jira/browse/CAMEL-18274
> Project: Camel
> Issue Type: Bug
> Components: camel-file
>Affects Versions: 3.18.0
>Reporter: Börcsök József
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> Using camel-file component(3.18.0) in OSGi environment (Apache Karaf) throws
> ClassNotFoundException:
> {noformat}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.camel.resume.ResumeAware not found by org.apache.camel.camel-file
> [46]
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591)
> at
> org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1976)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
> {noformat}
> The reason may be *org.apache.camel.resume* package is in Private-Package
> section of MANIFEST.MF in camel-file bundle (JAR file contains single
> configuration file: adapter.properties in this package) so exported package
> of camel-api bundle is hidden. I found that it has been changed since 3.17.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18278) AdviceWith fails with Spring XML and several route cross cutting concerns
[ https://issues.apache.org/jira/browse/CAMEL-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18278: Fix Version/s: 3.18.1 > AdviceWith fails with Spring XML and several route cross cutting concerns > - > > Key: CAMEL-18278 > URL: https://issues.apache.org/jira/browse/CAMEL-18278 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.4, 3.18.0 >Reporter: Benjamin Graf >Priority: Minor > Fix For: 3.18.1, 3.19.0 > > > Using Spring XML DSL to describe routes using several crosscutting concerns > like onException and transaction at once fails if tests are trying to modify > routes with adviceWith. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18291) SSLContextParameters parsePropertyValue support for certAlias property
[
https://issues.apache.org/jira/browse/CAMEL-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18291:
Fix Version/s: 3.18.1
> SSLContextParameters parsePropertyValue support for certAlias property
> --
>
> Key: CAMEL-18291
> URL: https://issues.apache.org/jira/browse/CAMEL-18291
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Robin Vishwakarma
>Priority: Minor
> Labels: sslContextParameters
> Fix For: 3.18.1, 3.19.0
>
>
> SSLContextParameters does have the provision to provide certAlias in case
> there are multiple certificate-key pair aliases present inside keystore but
> it doesn't have support for parsing the value for certAlias.
> It would be nice to add support of parsePropertyValue for certAlias property
> so that it can be externalized based on the configuration.
> Example - We have 2 environments, System Integration Testing(SIT) and User
> Acceptance Testing(UAT). We store certificate-key pair of both the
> environments in keystore JKS file and we want to select certificate-key pair
> for SSLContext via certAlias but here we have to provide the exact name of
> alias -
> {code:java}
>
>
> password="{{keystore.password}}"/>
>
>
> password="{{truststore.password}}"/>
>
> {code}
> Since certAlias doesn't have support for parsePropertyValue like other
> properties keyPassword, password, etc. We can't use property place holders
> for passing certAlias name.
> {code:java}
>
> certAlias="{{env.alias}}">
>
> password="{{keystore.password}}"/>
>
>
> password="{{truststore.password}}"/>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-17841) camel-azure - Add checkpoint events by batch
[ https://issues.apache.org/jira/browse/CAMEL-17841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17841. -- Resolution: Fixed > camel-azure - Add checkpoint events by batch > > > Key: CAMEL-17841 > URL: https://issues.apache.org/jira/browse/CAMEL-17841 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Kévin LACIRE >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.19.0 > > > Currently the Azure Eventhub consumer is checkpoint it's offset on [every > processed > exchange|https://github.com/apache/camel/blob/cb9d18559c2a482445be47ff28d423e1ddcdb7e9/components/camel-azure/camel-azure-eventhubs/src/main/java/org/apache/camel/component/azure/eventhubs/EventHubsConsumer.java#L149] > a quick upgrade would be to expose a *batchSize* parameter to execute this > checkpoint less frequently (this dramatically alter consumption performances) > a time interval could also be complementary to avoid potentially unlimited > pending checkpoint of the last batch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-17841) camel-azure - Add checkpoint events by batch
[ https://issues.apache.org/jira/browse/CAMEL-17841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-17841: Assignee: Andrea Cosentino > camel-azure - Add checkpoint events by batch > > > Key: CAMEL-17841 > URL: https://issues.apache.org/jira/browse/CAMEL-17841 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Kévin LACIRE >Assignee: Andrea Cosentino >Priority: Minor > > Currently the Azure Eventhub consumer is checkpoint it's offset on [every > processed > exchange|https://github.com/apache/camel/blob/cb9d18559c2a482445be47ff28d423e1ddcdb7e9/components/camel-azure/camel-azure-eventhubs/src/main/java/org/apache/camel/component/azure/eventhubs/EventHubsConsumer.java#L149] > a quick upgrade would be to expose a *batchSize* parameter to execute this > checkpoint less frequently (this dramatically alter consumption performances) > a time interval could also be complementary to avoid potentially unlimited > pending checkpoint of the last batch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-17841) camel-azure - Add checkpoint events by batch
[ https://issues.apache.org/jira/browse/CAMEL-17841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17841: - Fix Version/s: 3.19.0 > camel-azure - Add checkpoint events by batch > > > Key: CAMEL-17841 > URL: https://issues.apache.org/jira/browse/CAMEL-17841 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Kévin LACIRE >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.19.0 > > > Currently the Azure Eventhub consumer is checkpoint it's offset on [every > processed > exchange|https://github.com/apache/camel/blob/cb9d18559c2a482445be47ff28d423e1ddcdb7e9/components/camel-azure/camel-azure-eventhubs/src/main/java/org/apache/camel/component/azure/eventhubs/EventHubsConsumer.java#L149] > a quick upgrade would be to expose a *batchSize* parameter to execute this > checkpoint less frequently (this dramatically alter consumption performances) > a time interval could also be complementary to avoid potentially unlimited > pending checkpoint of the last batch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18278) AdviceWith fails with Spring XML and several route cross cutting concerns
[ https://issues.apache.org/jira/browse/CAMEL-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570876#comment-17570876 ] Benjamin Graf commented on CAMEL-18278: --- [~davsclaus]: Possible to get it also into latest LTS? > AdviceWith fails with Spring XML and several route cross cutting concerns > - > > Key: CAMEL-18278 > URL: https://issues.apache.org/jira/browse/CAMEL-18278 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.4, 3.18.0 >Reporter: Benjamin Graf >Priority: Minor > Fix For: 3.19.0 > > > Using Spring XML DSL to describe routes using several crosscutting concerns > like onException and transaction at once fails if tests are trying to modify > routes with adviceWith. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18291) SSLContextParameters parsePropertyValue support for certAlias property
[
https://issues.apache.org/jira/browse/CAMEL-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18291.
-
Fix Version/s: 3.19.0
Resolution: Fixed
> SSLContextParameters parsePropertyValue support for certAlias property
> --
>
> Key: CAMEL-18291
> URL: https://issues.apache.org/jira/browse/CAMEL-18291
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Robin Vishwakarma
>Priority: Minor
> Labels: sslContextParameters
> Fix For: 3.19.0
>
>
> SSLContextParameters does have the provision to provide certAlias in case
> there are multiple certificate-key pair aliases present inside keystore but
> it doesn't have support for parsing the value for certAlias.
> It would be nice to add support of parsePropertyValue for certAlias property
> so that it can be externalized based on the configuration.
> Example - We have 2 environments, System Integration Testing(SIT) and User
> Acceptance Testing(UAT). We store certificate-key pair of both the
> environments in keystore JKS file and we want to select certificate-key pair
> for SSLContext via certAlias but here we have to provide the exact name of
> alias -
> {code:java}
>
>
> password="{{keystore.password}}"/>
>
>
> password="{{truststore.password}}"/>
>
> {code}
> Since certAlias doesn't have support for parsePropertyValue like other
> properties keyPassword, password, etc. We can't use property place holders
> for passing certAlias name.
> {code:java}
>
> certAlias="{{env.alias}}">
>
> password="{{keystore.password}}"/>
>
>
> password="{{truststore.password}}"/>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18292) Datasonnet expression should not fail if body is empty
[
https://issues.apache.org/jira/browse/CAMEL-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18292:
Fix Version/s: 3.19.0
> Datasonnet expression should not fail if body is empty
> --
>
> Key: CAMEL-18292
> URL: https://issues.apache.org/jira/browse/CAMEL-18292
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 3.18.0
>Reporter: Eugene Berman
>Priority: Minor
> Fix For: 3.19.0
>
>
> Sometimes the body of the message is empty (e.g. when handling the GET
> request), and it causes Datasonnet expression to fail and throw an exception:
> {{ujson.IncompleteParseException: exhausted input}}
> The fix would be to internally generate an empty object matching the
> Datasonnet input media type (e.g. {} if the body media type is
> {{application/json}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18294) upgrade to spring boot 2.7.2
[ https://issues.apache.org/jira/browse/CAMEL-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18294: Fix Version/s: 3.19.0 > upgrade to spring boot 2.7.2 > > > Key: CAMEL-18294 > URL: https://issues.apache.org/jira/browse/CAMEL-18294 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 3.18.0 >Reporter: Federico Mariani >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > https://github.com/spring-projects/spring-boot/releases/tag/v2.7.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18295) Restore couchbase IT tests
[
https://issues.apache.org/jira/browse/CAMEL-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18295:
Component/s: tests
> Restore couchbase IT tests
> --
>
> Key: CAMEL-18295
> URL: https://issues.apache.org/jira/browse/CAMEL-18295
> Project: Camel
> Issue Type: Test
> Components: tests
>Affects Versions: 3.18.0
>Reporter: Federico Mariani
>Assignee: Federico Mariani
>Priority: Minor
> Fix For: 3.19.0
>
>
> IT tests do not run due to
> {code:java}
> Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out
> waiting for URL to be accessible (http://localhost:8091/pools should return
> HTTP [200])
> at
> org.testcontainers.containers.wait.strategy.HttpWaitStrategy.waitUntilReady(HttpWaitStrategy.java:318)
> at
> org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
> at
> org.testcontainers.couchbase.CouchbaseContainer.waitUntilNodeIsOnline(CouchbaseContainer.java:351){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18295) Restore couchbase IT tests
[
https://issues.apache.org/jira/browse/CAMEL-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18295.
-
Resolution: Fixed
> Restore couchbase IT tests
> --
>
> Key: CAMEL-18295
> URL: https://issues.apache.org/jira/browse/CAMEL-18295
> Project: Camel
> Issue Type: Test
> Components: tests
>Affects Versions: 3.18.0
>Reporter: Federico Mariani
>Assignee: Federico Mariani
>Priority: Minor
> Fix For: 3.19.0
>
>
> IT tests do not run due to
> {code:java}
> Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out
> waiting for URL to be accessible (http://localhost:8091/pools should return
> HTTP [200])
> at
> org.testcontainers.containers.wait.strategy.HttpWaitStrategy.waitUntilReady(HttpWaitStrategy.java:318)
> at
> org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
> at
> org.testcontainers.couchbase.CouchbaseContainer.waitUntilNodeIsOnline(CouchbaseContainer.java:351){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18278) AdviceWith fails with Spring XML and several route cross cutting concerns
[ https://issues.apache.org/jira/browse/CAMEL-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18278: Priority: Minor (was: Major) > AdviceWith fails with Spring XML and several route cross cutting concerns > - > > Key: CAMEL-18278 > URL: https://issues.apache.org/jira/browse/CAMEL-18278 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.4, 3.18.0 >Reporter: Benjamin Graf >Priority: Minor > Fix For: 3.19.0 > > > Using Spring XML DSL to describe routes using several crosscutting concerns > like onException and transaction at once fails if tests are trying to modify > routes with adviceWith. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18278) AdviceWith fails with Spring XML and several route cross cutting concerns
[ https://issues.apache.org/jira/browse/CAMEL-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18278. - Fix Version/s: 3.19.0 Resolution: Fixed > AdviceWith fails with Spring XML and several route cross cutting concerns > - > > Key: CAMEL-18278 > URL: https://issues.apache.org/jira/browse/CAMEL-18278 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.4, 3.18.0 >Reporter: Benjamin Graf >Priority: Major > Fix For: 3.19.0 > > > Using Spring XML DSL to describe routes using several crosscutting concerns > like onException and transaction at once fails if tests are trying to modify > routes with adviceWith. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18285) camel-file - Lazy-loading for file length and last modified attributes for faster performance
[ https://issues.apache.org/jira/browse/CAMEL-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18285: Summary: camel-file - Lazy-loading for file length and last modified attributes for faster performance (was: camel-file - Lazy-loading for file length and last modified attributes) > camel-file - Lazy-loading for file length and last modified attributes for > faster performance > - > > Key: CAMEL-18285 > URL: https://issues.apache.org/jira/browse/CAMEL-18285 > Project: Camel > Issue Type: Improvement > Components: camel-file >Affects Versions: 3.18.0 >Reporter: Radovan Netuka >Assignee: Radovan Netuka >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > In network-mounted drives, a user can experience long processing time due to > File#length and File#lastModified large invocation time. > > Use case: > There is a network-mounted drive. A user is polling a directory with > thousands of files inside, but only needs to process few of them. > > Current behaviour: > File length and last modified attributes are read for each such file, > seriously slowing the processing time. > > Expected behaviour: > File length and last modified attributes are read only when needed. > > Affected method is FileConsumer#asGenericFile. A solution for this can be to > load these two attributes lazily. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18285) Lazy-loading for file length and last modified attributes
[ https://issues.apache.org/jira/browse/CAMEL-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570868#comment-17570868 ] Claus Ibsen commented on CAMEL-18285: - Backported to 3.18 LTS as this benefits users with better performance > Lazy-loading for file length and last modified attributes > - > > Key: CAMEL-18285 > URL: https://issues.apache.org/jira/browse/CAMEL-18285 > Project: Camel > Issue Type: Improvement > Components: camel-file >Affects Versions: 3.18.0 >Reporter: Radovan Netuka >Assignee: Radovan Netuka >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > In network-mounted drives, a user can experience long processing time due to > File#length and File#lastModified large invocation time. > > Use case: > There is a network-mounted drive. A user is polling a directory with > thousands of files inside, but only needs to process few of them. > > Current behaviour: > File length and last modified attributes are read for each such file, > seriously slowing the processing time. > > Expected behaviour: > File length and last modified attributes are read only when needed. > > Affected method is FileConsumer#asGenericFile. A solution for this can be to > load these two attributes lazily. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18285) camel-file - Lazy-loading for file length and last modified attributes
[ https://issues.apache.org/jira/browse/CAMEL-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18285: Summary: camel-file - Lazy-loading for file length and last modified attributes (was: Lazy-loading for file length and last modified attributes) > camel-file - Lazy-loading for file length and last modified attributes > -- > > Key: CAMEL-18285 > URL: https://issues.apache.org/jira/browse/CAMEL-18285 > Project: Camel > Issue Type: Improvement > Components: camel-file >Affects Versions: 3.18.0 >Reporter: Radovan Netuka >Assignee: Radovan Netuka >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > In network-mounted drives, a user can experience long processing time due to > File#length and File#lastModified large invocation time. > > Use case: > There is a network-mounted drive. A user is polling a directory with > thousands of files inside, but only needs to process few of them. > > Current behaviour: > File length and last modified attributes are read for each such file, > seriously slowing the processing time. > > Expected behaviour: > File length and last modified attributes are read only when needed. > > Affected method is FileConsumer#asGenericFile. A solution for this can be to > load these two attributes lazily. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18285) Lazy-loading for file length and last modified attributes
[ https://issues.apache.org/jira/browse/CAMEL-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18285: Fix Version/s: 3.18.1 > Lazy-loading for file length and last modified attributes > - > > Key: CAMEL-18285 > URL: https://issues.apache.org/jira/browse/CAMEL-18285 > Project: Camel > Issue Type: Improvement > Components: camel-file >Affects Versions: 3.18.0 >Reporter: Radovan Netuka >Assignee: Radovan Netuka >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > In network-mounted drives, a user can experience long processing time due to > File#length and File#lastModified large invocation time. > > Use case: > There is a network-mounted drive. A user is polling a directory with > thousands of files inside, but only needs to process few of them. > > Current behaviour: > File length and last modified attributes are read for each such file, > seriously slowing the processing time. > > Expected behaviour: > File length and last modified attributes are read only when needed. > > Affected method is FileConsumer#asGenericFile. A solution for this can be to > load these two attributes lazily. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18285) Lazy-loading for file length and last modified attributes
[ https://issues.apache.org/jira/browse/CAMEL-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radovan Netuka resolved CAMEL-18285. Resolution: Fixed > Lazy-loading for file length and last modified attributes > - > > Key: CAMEL-18285 > URL: https://issues.apache.org/jira/browse/CAMEL-18285 > Project: Camel > Issue Type: Improvement > Components: camel-file >Affects Versions: 3.18.0 >Reporter: Radovan Netuka >Assignee: Radovan Netuka >Priority: Major > Fix For: 3.19.0 > > > In network-mounted drives, a user can experience long processing time due to > File#length and File#lastModified large invocation time. > > Use case: > There is a network-mounted drive. A user is polling a directory with > thousands of files inside, but only needs to process few of them. > > Current behaviour: > File length and last modified attributes are read for each such file, > seriously slowing the processing time. > > Expected behaviour: > File length and last modified attributes are read only when needed. > > Affected method is FileConsumer#asGenericFile. A solution for this can be to > load these two attributes lazily. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17760) camel-core: consolidate copy-exchange-if-capable logic
[
https://issues.apache.org/jira/browse/CAMEL-17760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske resolved CAMEL-17760.
--
Resolution: Fixed
Resolved with the linked PR.
> camel-core: consolidate copy-exchange-if-capable logic
> ---
>
> Key: CAMEL-17760
> URL: https://issues.apache.org/jira/browse/CAMEL-17760
> Project: Camel
> Issue Type: Task
> Components: camel-core
>Affects Versions: 3.15.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.x
>
>
> We have lots of code doing this:
>
> {code:java}
> if (exchange.getPattern().isOutCapable()) {
> exchange.getOut().copyFrom(exchange.getIn());
> exchange.getOut().setBody(body);
> } else {
> exchange.getIn().setBody(body);
> }{code}
>
> Because getOut is deprecated, this generates a lot of warnings. We can
> consolidate this logic in the ExchangeHelper class to simplify cleaning it up
> in the future.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18285) Lazy-loading for file length and last modified attributes
[ https://issues.apache.org/jira/browse/CAMEL-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18285: Fix Version/s: 3.19.0 > Lazy-loading for file length and last modified attributes > - > > Key: CAMEL-18285 > URL: https://issues.apache.org/jira/browse/CAMEL-18285 > Project: Camel > Issue Type: Improvement > Components: camel-file >Affects Versions: 3.18.0 >Reporter: Radovan Netuka >Assignee: Radovan Netuka >Priority: Major > Fix For: 3.19.0 > > > In network-mounted drives, a user can experience long processing time due to > File#length and File#lastModified large invocation time. > > Use case: > There is a network-mounted drive. A user is polling a directory with > thousands of files inside, but only needs to process few of them. > > Current behaviour: > File length and last modified attributes are read for each such file, > seriously slowing the processing time. > > Expected behaviour: > File length and last modified attributes are read only when needed. > > Affected method is FileConsumer#asGenericFile. A solution for this can be to > load these two attributes lazily. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-17760) camel-core: consolidate copy-exchange-if-capable logic
[
https://issues.apache.org/jira/browse/CAMEL-17760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-17760 started by Otavio Rodolfo Piske.
> camel-core: consolidate copy-exchange-if-capable logic
> ---
>
> Key: CAMEL-17760
> URL: https://issues.apache.org/jira/browse/CAMEL-17760
> Project: Camel
> Issue Type: Task
> Components: camel-core
>Affects Versions: 3.15.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.x
>
>
> We have lots of code doing this:
>
> {code:java}
> if (exchange.getPattern().isOutCapable()) {
> exchange.getOut().copyFrom(exchange.getIn());
> exchange.getOut().setBody(body);
> } else {
> exchange.getIn().setBody(body);
> }{code}
>
> Because getOut is deprecated, this generates a lot of warnings. We can
> consolidate this logic in the ExchangeHelper class to simplify cleaning it up
> in the future.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18298) camel-jbang - Add support for @Startup beans
Claus Ibsen created CAMEL-18298: --- Summary: camel-jbang - Add support for @Startup beans Key: CAMEL-18298 URL: https://issues.apache.org/jira/browse/CAMEL-18298 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Fix For: 3.19.0 Lets see if we can detect @Startup bean classes that has methods that can produce beans that customize camel components etc, which we should detect and register into camel. We do have some support for @Produce already today. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18297) camel-core - Languages with namespace support should be exposed in model
Claus Ibsen created CAMEL-18297: --- Summary: camel-core - Languages with namespace support should be exposed in model Key: CAMEL-18297 URL: https://issues.apache.org/jira/browse/CAMEL-18297 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 3.19.0 A few languages like xpath, xquery extends org.apache.camel.model.language.NamespaceAwareExpression have the namespace options not exposed in the model, but specially in XML DSL. We should expose this in the model so its general for all DSLs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18296) camel-example tag is using snapshot camel version
[ https://issues.apache.org/jira/browse/CAMEL-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570789#comment-17570789 ] Claus Ibsen edited comment on CAMEL-18296 at 7/25/22 9:15 AM: -- The main branch is SNAPSHOT. Checkout a tag to use a specific release https://github.com/apache/camel-examples/tree/camel-examples-3.18.0 However the examples/pom.xml is wrong in that tag as it should be 3.18.0 and not SNAPSHOT was (Author: davsclaus): The main branch is SNAPSHOT. Checkout a tag to use a specific release https://github.com/apache/camel-examples/tree/camel-examples-3.18.0 > camel-example tag is using snapshot camel version > - > > Key: CAMEL-18296 > URL: https://issues.apache.org/jira/browse/CAMEL-18296 > Project: Camel > Issue Type: Task > Components: examples >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Minor > > see > https://github.com/apache/camel-examples/blob/27d60cbd1f113036df48daffd7edea8375a954aa/examples/pom.xml#L170 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18296) camel-example tag is using snapshot camel version
[ https://issues.apache.org/jira/browse/CAMEL-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18296: Fix Version/s: 3.18.1 3.19.0 > camel-example tag is using snapshot camel version > - > > Key: CAMEL-18296 > URL: https://issues.apache.org/jira/browse/CAMEL-18296 > Project: Camel > Issue Type: Task > Components: examples >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 3.18.1, 3.19.0 > > > see > https://github.com/apache/camel-examples/blob/27d60cbd1f113036df48daffd7edea8375a954aa/examples/pom.xml#L170 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18296) camel-example tag is using snapshot camel version
[ https://issues.apache.org/jira/browse/CAMEL-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570789#comment-17570789 ] Claus Ibsen commented on CAMEL-18296: - The main branch is SNAPSHOT. Checkout a tag to use a specific release https://github.com/apache/camel-examples/tree/camel-examples-3.18.0 > camel-example tag is using snapshot camel version > - > > Key: CAMEL-18296 > URL: https://issues.apache.org/jira/browse/CAMEL-18296 > Project: Camel > Issue Type: Task > Components: examples >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Minor > > see > https://github.com/apache/camel-examples/blob/27d60cbd1f113036df48daffd7edea8375a954aa/examples/pom.xml#L170 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18296) camel-example tag is using snapshot camel version
[ https://issues.apache.org/jira/browse/CAMEL-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18296: Issue Type: Task (was: Bug) > camel-example tag is using snapshot camel version > - > > Key: CAMEL-18296 > URL: https://issues.apache.org/jira/browse/CAMEL-18296 > Project: Camel > Issue Type: Task > Components: examples >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Major > > see > https://github.com/apache/camel-examples/blob/27d60cbd1f113036df48daffd7edea8375a954aa/examples/pom.xml#L170 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18296) camel-example tag is using snapshot camel version
[ https://issues.apache.org/jira/browse/CAMEL-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18296: Priority: Minor (was: Major) > camel-example tag is using snapshot camel version > - > > Key: CAMEL-18296 > URL: https://issues.apache.org/jira/browse/CAMEL-18296 > Project: Camel > Issue Type: Task > Components: examples >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Minor > > see > https://github.com/apache/camel-examples/blob/27d60cbd1f113036df48daffd7edea8375a954aa/examples/pom.xml#L170 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18296) camel-example tag is using snapshot camel version
Aurélien Pupier created CAMEL-18296: --- Summary: camel-example tag is using snapshot camel version Key: CAMEL-18296 URL: https://issues.apache.org/jira/browse/CAMEL-18296 Project: Camel Issue Type: Bug Components: examples Affects Versions: 3.18.0 Reporter: Aurélien Pupier see https://github.com/apache/camel-examples/blob/27d60cbd1f113036df48daffd7edea8375a954aa/examples/pom.xml#L170 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18295) Restore couchbase IT tests
Federico Mariani created CAMEL-18295:
Summary: Restore couchbase IT tests
Key: CAMEL-18295
URL: https://issues.apache.org/jira/browse/CAMEL-18295
Project: Camel
Issue Type: Test
Affects Versions: 3.18.0
Reporter: Federico Mariani
Assignee: Federico Mariani
Fix For: 3.19.0
IT tests do not run due to
{code:java}
Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out
waiting for URL to be accessible (http://localhost:8091/pools should return
HTTP [200])
at
org.testcontainers.containers.wait.strategy.HttpWaitStrategy.waitUntilReady(HttpWaitStrategy.java:318)
at
org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
at
org.testcontainers.couchbase.CouchbaseContainer.waitUntilNodeIsOnline(CouchbaseContainer.java:351){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18280) Reuse AWS localstack docker image
[ https://issues.apache.org/jira/browse/CAMEL-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570775#comment-17570775 ] Otavio Rodolfo Piske commented on CAMEL-18280: -- [~Federico Mariani] I think it could be reused and, probably, would be a nice improvement to them. Unfortunately I don't know yet when I'll be able to look closely at this. I'll keep it in my mind for now, ok? > Reuse AWS localstack docker image > - > > Key: CAMEL-18280 > URL: https://issues.apache.org/jira/browse/CAMEL-18280 > Project: Camel > Issue Type: Improvement >Reporter: Federico Mariani >Assignee: Otavio Rodolfo Piske >Priority: Minor > > AWS IT tests execution is slow mostly due to localstack docker image > restarts, can the docker image be reused via testcontainer? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18293) camel-cxf - Move CXFTestSupport to test-jar
[ https://issues.apache.org/jira/browse/CAMEL-18293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18293. - Assignee: Claus Ibsen Resolution: Fixed > camel-cxf - Move CXFTestSupport to test-jar > --- > > Key: CAMEL-18293 > URL: https://issues.apache.org/jira/browse/CAMEL-18293 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Affects Versions: 3.18.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > After the splitup then CXFTestSupport was moved into src/main and has junit > dependencies as runtime scoped, but they should be test scoped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18294) upgrade to spring boot 2.7.2
Federico Mariani created CAMEL-18294: Summary: upgrade to spring boot 2.7.2 Key: CAMEL-18294 URL: https://issues.apache.org/jira/browse/CAMEL-18294 Project: Camel Issue Type: Dependency upgrade Affects Versions: 3.18.0 Reporter: Federico Mariani Fix For: 3.18.1 https://github.com/spring-projects/spring-boot/releases/tag/v2.7.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18293) camel-cxf - Move CXFTestSupport to test-jar
Claus Ibsen created CAMEL-18293: --- Summary: camel-cxf - Move CXFTestSupport to test-jar Key: CAMEL-18293 URL: https://issues.apache.org/jira/browse/CAMEL-18293 Project: Camel Issue Type: Improvement Components: camel-cxf Affects Versions: 3.18.0 Reporter: Claus Ibsen Fix For: 3.18.1, 3.19.0 After the splitup then CXFTestSupport was moved into src/main and has junit dependencies as runtime scoped, but they should be test scoped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-9627) Splitup camel-cxf into modules so REST dont pull in old SOAP stuff
[ https://issues.apache.org/jira/browse/CAMEL-9627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570715#comment-17570715 ] Claus Ibsen commented on CAMEL-9627: Thanks Andrei I created a ticket https://issues.apache.org/jira/browse/CAMEL-18293 > Splitup camel-cxf into modules so REST dont pull in old SOAP stuff > -- > > Key: CAMEL-9627 > URL: https://issues.apache.org/jira/browse/CAMEL-9627 > Project: Camel > Issue Type: Improvement > Components: came-cxf >Reporter: Claus Ibsen >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.18.0 > > > To make camel-cxf feature less bloated and not include this seldom used > component which you can install as its own feature. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-16938) StackOverflowError in RedeliveryErrorHandler when using transacted
[ https://issues.apache.org/jira/browse/CAMEL-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17570711#comment-17570711 ] Claus Ibsen commented on CAMEL-16938: - Camel 3.11 is EOL > StackOverflowError in RedeliveryErrorHandler when using transacted > -- > > Key: CAMEL-16938 > URL: https://issues.apache.org/jira/browse/CAMEL-16938 > Project: Camel > Issue Type: Bug > Components: came-core >Affects Versions: 3.11.0 >Reporter: Wojciech Strzałka >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.13.0 > > Attachments: StackOverflowTest.java > > > After migration from Camel 2.25.x to 3.11.0 there is issue with redelivery > logic causing stack trace overflow eventually. > See the stack trace: > Caused by: java.lang.StackOverflowError > at > com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:769) > at > com.google.common.util.concurrent.SettableFuture.setException(SettableFuture.java:53) > at > com.google.common.cache.LocalCache$LoadingValueReference.setException(LocalCache.java:3503) > at > com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3549) > at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2278) > at > com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2155) > at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2045) > at com.google.common.cache.LocalCache.get(LocalCache.java:3951) > at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3974) > at > com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4935) > at > com.google.common.cache.LocalCache$LocalLoadingCache.getUnchecked(LocalCache.java:4941) > at com.foo.bar.AtomicCache.get(AtomicCache.java:34) > at > com.foo.bar.CachingZoneServiceRegistry.findWithZoneId(CachingZoneServiceRegistry.java:55) > at > com.foo.bar.PersistenceBasedRoutingsLoader.lambda$getDestinationFunction$1(PersistenceBasedRoutingsLoader.java:34) > at > com.foo.bar.RoutingDestination.getTargetDestinationsFor(RoutingDestination.java:66) > at > com.foo.bar.RoutingDestination.getClientCamelUris(RoutingDestination.java:59) > at sun.reflect.GeneratedMethodAccessor461.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.camel.support.ObjectHelper.invokeMethodSafe(ObjectHelper.java:380) > at org.apache.camel.component.bean.MethodInfo.invoke(MethodInfo.java:494) > at org.apache.camel.component.bean.MethodInfo$1.doProceed(MethodInfo.java:316) > at org.apache.camel.component.bean.MethodInfo$1.proceed(MethodInfo.java:286) > at > org.apache.camel.component.bean.AbstractBeanProcessor.process(AbstractBeanProcessor.java:146) > at > org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:83) > at > org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:41) > at > org.apache.camel.language.bean.BeanExpression.invokeBean(BeanExpression.java:347) > at > org.apache.camel.language.bean.BeanExpression.evaluate(BeanExpression.java:202) > at > org.apache.camel.language.bean.BeanExpression.evaluate(BeanExpression.java:214) > at > org.apache.camel.processor.SetPropertyProcessor.process(SetPropertyProcessor.java:47) > at > org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:83) > at > org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:41) > at > org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:369) > at org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:109) > at > org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:179) > at > org.apache.camel.impl.engine.DefaultReactiveExecutor.schedule(DefaultReactiveExecutor.java:59) > at > org.apache.camel.impl.engine.CamelInternalProcessor$AsyncAfterTask.done(CamelInternalProcessor.java:274) > at > org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:377) > at org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:109) > at > org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:179) > at > org.apache.camel.impl.engine.DefaultReactiveExecutor.schedule(DefaultReactiveExecutor.java:59) > at > org.apache.camel.impl.engine.CamelInternalProcessor$AsyncAfterTask.done(CamelInternalProcessor.java:274) > at > org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:377) > at
[jira] [Updated] (CAMEL-18268) Camel-dependencies is misaligned to current version in camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18268: Fix Version/s: 3.19.0 > Camel-dependencies is misaligned to current version in camel-spring-boot > > > Key: CAMEL-18268 > URL: https://issues.apache.org/jira/browse/CAMEL-18268 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Marco Carletti >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.19.0 > > > The camel-dependencies version is 3.18.0-SNAPSHOT in > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L26 and the > current version is 3.19.0-SNAPSHOT > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18268) Camel-dependencies is misaligned to current version in camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18268: Priority: Minor (was: Major) > Camel-dependencies is misaligned to current version in camel-spring-boot > > > Key: CAMEL-18268 > URL: https://issues.apache.org/jira/browse/CAMEL-18268 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Marco Carletti >Assignee: Andrea Cosentino >Priority: Minor > > The camel-dependencies version is 3.18.0-SNAPSHOT in > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L26 and the > current version is 3.19.0-SNAPSHOT > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18268) Camel-dependencies is misaligned to current version in camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18268: Issue Type: Task (was: Bug) > Camel-dependencies is misaligned to current version in camel-spring-boot > > > Key: CAMEL-18268 > URL: https://issues.apache.org/jira/browse/CAMEL-18268 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Marco Carletti >Assignee: Andrea Cosentino >Priority: Major > > The camel-dependencies version is 3.18.0-SNAPSHOT in > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L26 and the > current version is 3.19.0-SNAPSHOT > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18274) OSGi - camel-file: ClassNotFoundException because of Private-Package
[
https://issues.apache.org/jira/browse/CAMEL-18274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18274:
Summary: OSGi - camel-file: ClassNotFoundException because of
Private-Package (was: camel-resume-api: ClassNotFoundException because of
Private-Package)
> OSGi - camel-file: ClassNotFoundException because of Private-Package
>
>
> Key: CAMEL-18274
> URL: https://issues.apache.org/jira/browse/CAMEL-18274
> Project: Camel
> Issue Type: Bug
> Components: camel-resume-api
>Affects Versions: 3.18.0
>Reporter: Börcsök József
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> Using camel-file component(3.18.0) in OSGi environment (Apache Karaf) throws
> ClassNotFoundException:
> {noformat}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.camel.resume.ResumeAware not found by org.apache.camel.camel-file
> [46]
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591)
> at
> org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1976)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
> {noformat}
> The reason may be *org.apache.camel.resume* package is in Private-Package
> section of MANIFEST.MF in camel-file bundle (JAR file contains single
> configuration file: adapter.properties in this package) so exported package
> of camel-api bundle is hidden. I found that it has been changed since 3.17.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18274) OSGi - camel-file: ClassNotFoundException because of Private-Package
[
https://issues.apache.org/jira/browse/CAMEL-18274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18274:
Component/s: camel-file
(was: camel-resume-api)
> OSGi - camel-file: ClassNotFoundException because of Private-Package
>
>
> Key: CAMEL-18274
> URL: https://issues.apache.org/jira/browse/CAMEL-18274
> Project: Camel
> Issue Type: Bug
> Components: camel-file
>Affects Versions: 3.18.0
>Reporter: Börcsök József
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> Using camel-file component(3.18.0) in OSGi environment (Apache Karaf) throws
> ClassNotFoundException:
> {noformat}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.camel.resume.ResumeAware not found by org.apache.camel.camel-file
> [46]
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591)
> at
> org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1976)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
> {noformat}
> The reason may be *org.apache.camel.resume* package is in Private-Package
> section of MANIFEST.MF in camel-file bundle (JAR file contains single
> configuration file: adapter.properties in this package) so exported package
> of camel-api bundle is hidden. I found that it has been changed since 3.17.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18274) camel-resume-api: ClassNotFoundException because of Private-Package
[
https://issues.apache.org/jira/browse/CAMEL-18274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18274:
Fix Version/s: 3.18.1
3.19.0
> camel-resume-api: ClassNotFoundException because of Private-Package
> ---
>
> Key: CAMEL-18274
> URL: https://issues.apache.org/jira/browse/CAMEL-18274
> Project: Camel
> Issue Type: Bug
> Components: camel-resume-api
>Affects Versions: 3.18.0
>Reporter: Börcsök József
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> Using camel-file component(3.18.0) in OSGi environment (Apache Karaf) throws
> ClassNotFoundException:
> {noformat}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.camel.resume.ResumeAware not found by org.apache.camel.camel-file
> [46]
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591)
> at
> org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1976)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
> {noformat}
> The reason may be *org.apache.camel.resume* package is in Private-Package
> section of MANIFEST.MF in camel-file bundle (JAR file contains single
> configuration file: adapter.properties in this package) so exported package
> of camel-api bundle is hidden. I found that it has been changed since 3.17.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18286) [Camel Spring Boot] camel-lra-starter needs camel-servlet-starter to work
[
https://issues.apache.org/jira/browse/CAMEL-18286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18286:
Priority: Minor (was: Major)
> [Camel Spring Boot] camel-lra-starter needs camel-servlet-starter to work
> -
>
> Key: CAMEL-18286
> URL: https://issues.apache.org/jira/browse/CAMEL-18286
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot, camel-spring-boot-starters
>Affects Versions: 3.18.0
>Reporter: Marco Carletti
>Priority: Minor
> Fix For: 3.19.0
>
> Attachments: saga-lra.zip
>
>
> Despite the
> [documentation|https://camel.apache.org/components/latest/eips/saga-eip.html#_using_the_lra_saga_service_in_spring_boot]
> says that the necessary dependencies are _camel-lra-starter_ and
> {_}camel-undertow-starter{_}, _camel-servlet-starter_ dependecy is necessary
> to make the saga works as expected.
> To reproduce the error:
> 1) start Narayana LRA Coordinator on port
> {code:bash}
> docker run --network host -e QUARKUS_HTTP_PORT= -e LOG_LEVEL=INFO --rm
> docker.io/jbosstm/lra-coordinator:latest
> {code}
> 2) start attached application
> {code:bash}
> mvn spring-boot:run
> {code}
>
> looking at the transactions at [http://localhost:/lra-coordinator/] we
> will see that all the transactions will be in "Closing" status, I expected no
> transactions here (all completed/compensated)
> The issue is that the REST endpoint are not exposed by the [camel-lra
> component|https://github.com/apache/camel/blob/main/components/camel-lra/src/main/java/org/apache/camel/service/lra/LRASagaRoutes.java#L45-L61]
> so the LRA cannot be completed by the LRA Coordinator (it is possible to see
> WARN log in the container log)
> The workaround is adding camel-servlet-starter dependency
> 3) start application with the dependency:
> {code:bash}
> mvn spring-boot:run -Pworkaround
> {code}
> now there are no "Closing" transactions at
> [http://localhost:/lra-coordinator/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18286) [Camel Spring Boot] camel-lra-starter needs camel-servlet-starter to work
[
https://issues.apache.org/jira/browse/CAMEL-18286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18286:
Fix Version/s: 3.19.0
> [Camel Spring Boot] camel-lra-starter needs camel-servlet-starter to work
> -
>
> Key: CAMEL-18286
> URL: https://issues.apache.org/jira/browse/CAMEL-18286
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot, camel-spring-boot-starters
>Affects Versions: 3.18.0
>Reporter: Marco Carletti
>Priority: Major
> Fix For: 3.19.0
>
> Attachments: saga-lra.zip
>
>
> Despite the
> [documentation|https://camel.apache.org/components/latest/eips/saga-eip.html#_using_the_lra_saga_service_in_spring_boot]
> says that the necessary dependencies are _camel-lra-starter_ and
> {_}camel-undertow-starter{_}, _camel-servlet-starter_ dependecy is necessary
> to make the saga works as expected.
> To reproduce the error:
> 1) start Narayana LRA Coordinator on port
> {code:bash}
> docker run --network host -e QUARKUS_HTTP_PORT= -e LOG_LEVEL=INFO --rm
> docker.io/jbosstm/lra-coordinator:latest
> {code}
> 2) start attached application
> {code:bash}
> mvn spring-boot:run
> {code}
>
> looking at the transactions at [http://localhost:/lra-coordinator/] we
> will see that all the transactions will be in "Closing" status, I expected no
> transactions here (all completed/compensated)
> The issue is that the REST endpoint are not exposed by the [camel-lra
> component|https://github.com/apache/camel/blob/main/components/camel-lra/src/main/java/org/apache/camel/service/lra/LRASagaRoutes.java#L45-L61]
> so the LRA cannot be completed by the LRA Coordinator (it is possible to see
> WARN log in the container log)
> The workaround is adding camel-servlet-starter dependency
> 3) start application with the dependency:
> {code:bash}
> mvn spring-boot:run -Pworkaround
> {code}
> now there are no "Closing" transactions at
> [http://localhost:/lra-coordinator/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18292) Datasonnet expression should not fail if body is empty
[
https://issues.apache.org/jira/browse/CAMEL-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18292:
Issue Type: Improvement (was: Bug)
> Datasonnet expression should not fail if body is empty
> --
>
> Key: CAMEL-18292
> URL: https://issues.apache.org/jira/browse/CAMEL-18292
> Project: Camel
> Issue Type: Improvement
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: Eugene Berman
>Priority: Minor
>
> Sometimes the body of the message is empty (e.g. when handling the GET
> request), and it causes Datasonnet expression to fail and throw an exception:
> {{ujson.IncompleteParseException: exhausted input}}
> The fix would be to internally generate an empty object matching the
> Datasonnet input media type (e.g. {} if the body media type is
> {{application/json}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18292) Datasonnet expression should not fail if body is empty
[
https://issues.apache.org/jira/browse/CAMEL-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18292:
Component/s: (was: came-core)
> Datasonnet expression should not fail if body is empty
> --
>
> Key: CAMEL-18292
> URL: https://issues.apache.org/jira/browse/CAMEL-18292
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 3.18.0
>Reporter: Eugene Berman
>Priority: Minor
>
> Sometimes the body of the message is empty (e.g. when handling the GET
> request), and it causes Datasonnet expression to fail and throw an exception:
> {{ujson.IncompleteParseException: exhausted input}}
> The fix would be to internally generate an empty object matching the
> Datasonnet input media type (e.g. {} if the body media type is
> {{application/json}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
