[jira] [Updated] (CAMEL-19050) DHIS2 Component
[ https://issues.apache.org/jira/browse/CAMEL-19050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19050: Fix Version/s: 3.21.0 4.0-M2 4.0 > DHIS2 Component > --- > > Key: CAMEL-19050 > URL: https://issues.apache.org/jira/browse/CAMEL-19050 > Project: Camel > Issue Type: New Feature >Reporter: Claude Mamo >Priority: Major > Fix For: 3.21.0, 4.0-M2, 4.0 > > > The DHIS2 team is maintaining an Apache Camel component that leverages the > DHIS2 Java SDK to integrate Apache Camel with the DHIS2 Web API. We'd like to > add this component to the Apache Camel distribution. PRs contributing the > component will be opened soon on the main and 3.x branches. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18610) Support Debezium 2.0
[ https://issues.apache.org/jira/browse/CAMEL-18610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18610: Fix Version/s: 4.0-M2 > Support Debezium 2.0 > > > Key: CAMEL-18610 > URL: https://issues.apache.org/jira/browse/CAMEL-18610 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-debezium >Reporter: Vojtech Juranek >Priority: Major > Fix For: 4.0-M2, 4.0 > > > Upcoming Debezium 2.0 will bring several backward incompatible changes > (summary of the changes will be published in release notes and Debezium blog > once 2.0.0 is out) and these changes will break all (or al least most) > camel-debezium connectors. Adapt the connectors to to be able to work with > 2.0.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19045) Integrate camel-cdi in OSGi aries-cdi
[ https://issues.apache.org/jira/browse/CAMEL-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19045. - Resolution: Information Provided See PR > Integrate camel-cdi in OSGi aries-cdi > - > > Key: CAMEL-19045 > URL: https://issues.apache.org/jira/browse/CAMEL-19045 > Project: Camel > Issue Type: Improvement > Components: camel-cdi, camel-jaxb >Affects Versions: 3.18.1 >Reporter: Ciprian Ciubotariu >Priority: Major > > So, I've made this the last year, based on camel-3.18.1, and it works > perfectly fine with aries-cdi (CDI 2.0). At this stage it still is pretty > dirty. I thought I should contribute it and ask for directions on how to > separate the OSGi function from the non-osgi camel-cdi code. > However, I have noticed that the roadmap to camel-4 is dropping both > camel-cdi and moving away all of the OSGi support. > So I guess the question now would be I should contribute this here, or maybe > it would be better to attempt to submit this to camel-karaf, along with the > rest of camel-cdi. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19049) camel-bean: AmbiguousMethodCallException when using OSGi service reference
[
https://issues.apache.org/jira/browse/CAMEL-19049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19049:
Priority: Minor (was: Critical)
> camel-bean: AmbiguousMethodCallException when using OSGi service reference
> --
>
> Key: CAMEL-19049
> URL: https://issues.apache.org/jira/browse/CAMEL-19049
> Project: Camel
> Issue Type: Bug
> Components: camel-bean
>Affects Versions: 3.14.6
>Reporter: Rastislav Papp
>Priority: Minor
>
> After upgrading from 3.14.4 to 3.14.6 we can no longer call camel bean method
> on an instance of OSGI service which implements an interface. This is caused
> by the changes introduced in CAMEL-18411.
> Example:
> route:
> {code:java}
> public class TestRoute extends RouteBuilder {
> @BeanInject
> private MyInterface myInterface;
> @Override
> public void configure() {
> from("...")
> .bean(myInterface, "reinit");
> }
> }
> {code}
> The {{MyInterface}} is:
> {code}
> public interface MyInterface {
> void reinit();
> }
> {code}
> The object injected is a proxy reference to OSGI service, injected by
> blueprint in karaf runtime.
> Stacktrace:
> {code}
> org.apache.camel.component.bean.AmbiguousMethodCallException: Ambiguous
> method invocations possible: [public void
> Proxyb113d9d3_4aac_4ac9_b619_9bb68d221255.reinit(), public abstract void
> foo.bar.MyInterface.reinit()] on the exchange:
> Exchange[92BC3141E43445D-003F] at
> org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:246)
> at
> org.apache.camel.component.bean.AbstractBeanProcessor.process(AbstractBeanProcessor.java:126)
> at
> org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:81)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:818)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:726)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:185) at
> {code}
> The ambiguousness is caused by the {{reinit()}} method detected twice - once
> from the interface, and one from the {{Proxy}} class.
> I'm working on a solution.
> cc: [~AWeickel]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19035) Camel-jsonpath is parsing whole json payload from 3.10.0
[
https://issues.apache.org/jira/browse/CAMEL-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xilai Dai updated CAMEL-19035:
--
Description:
Given a json payload e.g:
{code}
{
"ABC": "A",
"VERSION_NO": "BASE",
"DEF": [
{
"GGG": 1,
"HHH": "N",
"OOO": [
{
"PPP": 1,
"QQQ": 555.55,
"RRR": 666.66,
"SSS": 0,
"TTT": 777.77
},
{
"PPP": 3,
"QQQ": .05,
"RRR": .10,
"SSS": 0,
"TTT": .10
}
]
}
]
}
{code}
In case of there is something e.g invalid integer value (.05) in the payload
- .jsonpath("$.VERSION_NO") works as expected in Camel version less than 3.10.0.
- .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
than or equal 3.10.0.
Investigation shows that this regression was starting happening after
CAMEL-16389.
https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee
Now camel-jsonpath is trying to parse whole json payload.
Attached test-jsonpath.zip for test/reproduce this issue.
was:
Given a json payload e.g:
{code}
{
"ABC": "A",
"VERSION_NO": "BASE",
"DEF": [
{
"GGG": 1,
"HHH": "N",
"OOO": [
{
"PPP": 1,
"QQQ": 555.55,
"RRR": 666.66,
"SSS": 0,
"TTT": 777.77
},
{
"PPP": 3,
"QQQ": .05,
"RRR": .10,
"SSS": 0,
"TTT": .10
}
]
}
]
}
{code}
In case of there is something e.g invalid integer value (.05) in the payload
- .jsonpath("$.VERSION_NO") works as expected in Camel version less than 3.10.0.
- .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
than 3.10.0.
Investigation shows that this regression was starting happening after
CAMEL-16389.
https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee
Now camel-jsonpath is trying to parse whole json payload.
Attached test-jsonpath.zip for test/reproduce this issue.
> Camel-jsonpath is parsing whole json payload from 3.10.0
>
>
> Key: CAMEL-19035
> URL: https://issues.apache.org/jira/browse/CAMEL-19035
> Project: Camel
> Issue Type: Bug
> Components: camel-jsonpath
>Affects Versions: 3.11.0
>Reporter: Xilai Dai
>Assignee: Nicolas Filotto
>Priority: Minor
> Attachments: test-jsonpath.zip
>
>
> Given a json payload e.g:
> {code}
> {
> "ABC": "A",
> "VERSION_NO": "BASE",
> "DEF": [
> {
> "GGG": 1,
> "HHH": "N",
> "OOO": [
> {
> "PPP": 1,
> "QQQ": 555.55,
> "RRR": 666.66,
> "SSS": 0,
> "TTT": 777.77
> },
> {
> "PPP": 3,
> "QQQ": .05,
> "RRR": .10,
> "SSS": 0,
> "TTT": .10
> }
> ]
> }
> ]
> }
> {code}
> In case of there is something e.g invalid integer value (.05) in the payload
> - .jsonpath("$.VERSION_NO") works as expected in Camel version less than
> 3.10.0.
> - .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
> than or equal 3.10.0.
> Investigation shows that this regression was starting happening after
> CAMEL-16389.
>
[jira] [Updated] (CAMEL-19035) Camel-jsonpath is parsing whole json payload from 3.10.0
[
https://issues.apache.org/jira/browse/CAMEL-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xilai Dai updated CAMEL-19035:
--
Affects Version/s: 3.10.0
(was: 3.11.0)
> Camel-jsonpath is parsing whole json payload from 3.10.0
>
>
> Key: CAMEL-19035
> URL: https://issues.apache.org/jira/browse/CAMEL-19035
> Project: Camel
> Issue Type: Bug
> Components: camel-jsonpath
>Affects Versions: 3.10.0
>Reporter: Xilai Dai
>Assignee: Nicolas Filotto
>Priority: Minor
> Attachments: test-jsonpath.zip
>
>
> Given a json payload e.g:
> {code}
> {
> "ABC": "A",
> "VERSION_NO": "BASE",
> "DEF": [
> {
> "GGG": 1,
> "HHH": "N",
> "OOO": [
> {
> "PPP": 1,
> "QQQ": 555.55,
> "RRR": 666.66,
> "SSS": 0,
> "TTT": 777.77
> },
> {
> "PPP": 3,
> "QQQ": .05,
> "RRR": .10,
> "SSS": 0,
> "TTT": .10
> }
> ]
> }
> ]
> }
> {code}
> In case of there is something e.g invalid integer value (.05) in the payload
> - .jsonpath("$.VERSION_NO") works as expected in Camel version less than
> 3.10.0.
> - .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
> than or equal 3.10.0.
> Investigation shows that this regression was starting happening after
> CAMEL-16389.
> https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee
> Now camel-jsonpath is trying to parse whole json payload.
> Attached test-jsonpath.zip for test/reproduce this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19035) Camel-jsonpath is parsing whole json payload from 3.10.0
[
https://issues.apache.org/jira/browse/CAMEL-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688816#comment-17688816
]
Xilai Dai commented on CAMEL-19035:
---
Yes, I confirm this issue is start happening after
https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee
(Updated the Jira description and linked with CAMEL-16389)
> Camel-jsonpath is parsing whole json payload from 3.10.0
>
>
> Key: CAMEL-19035
> URL: https://issues.apache.org/jira/browse/CAMEL-19035
> Project: Camel
> Issue Type: Bug
> Components: camel-jsonpath
>Affects Versions: 3.11.0
>Reporter: Xilai Dai
>Assignee: Nicolas Filotto
>Priority: Minor
> Attachments: test-jsonpath.zip
>
>
> Given a json payload e.g:
> {code}
> {
> "ABC": "A",
> "VERSION_NO": "BASE",
> "DEF": [
> {
> "GGG": 1,
> "HHH": "N",
> "OOO": [
> {
> "PPP": 1,
> "QQQ": 555.55,
> "RRR": 666.66,
> "SSS": 0,
> "TTT": 777.77
> },
> {
> "PPP": 3,
> "QQQ": .05,
> "RRR": .10,
> "SSS": 0,
> "TTT": .10
> }
> ]
> }
> ]
> }
> {code}
> In case of there is something e.g invalid integer value (.05) in the payload
> - .jsonpath("$.VERSION_NO") works as expected in Camel version less than
> 3.10.0.
> - .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
> than 3.10.0.
> Investigation shows that this regression was starting happening after
> CAMEL-16389.
> https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee
> Now camel-jsonpath is trying to parse whole json payload.
> Attached test-jsonpath.zip for test/reproduce this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19035) Camel-jsonpath is parsing whole json payload from 3.10.0
[
https://issues.apache.org/jira/browse/CAMEL-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xilai Dai updated CAMEL-19035:
--
Description:
Given a json payload e.g:
{code}
{
"ABC": "A",
"VERSION_NO": "BASE",
"DEF": [
{
"GGG": 1,
"HHH": "N",
"OOO": [
{
"PPP": 1,
"QQQ": 555.55,
"RRR": 666.66,
"SSS": 0,
"TTT": 777.77
},
{
"PPP": 3,
"QQQ": .05,
"RRR": .10,
"SSS": 0,
"TTT": .10
}
]
}
]
}
{code}
In case of there is something e.g invalid integer value (.05) in the payload
- .jsonpath("$.VERSION_NO") works as expected in Camel version less than 3.10.0.
- .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
than 3.10.0.
Investigation shows that this regression was starting happening after
CAMEL-16389.
https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee
Now camel-jsonpath is trying to parse whole json payload.
Attached test-jsonpath.zip for test/reproduce this issue.
was:
Given a json payload e.g:
{code}
{
"ABC": "A",
"VERSION_NO": "BASE",
"DEF": [
{
"GGG": 1,
"HHH": "N",
"OOO": [
{
"PPP": 1,
"QQQ": 555.55,
"RRR": 666.66,
"SSS": 0,
"TTT": 777.77
},
{
"PPP": 3,
"QQQ": .05,
"RRR": .10,
"SSS": 0,
"TTT": .10
}
]
}
]
}
{code}
In case of there is something e.g invalid integer value (.05) in the payload
- .jsonpath("$.VERSION_NO") works as expected in Camel version less than 3.10.0.
- .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
than 3.10.0.
Investigation shows that this regression was starting happening after
CAMEL-16397.
https://github.com/apache/camel/commit/e9e8ed2057f0122f30664eb123ca00775a69c538
Now camel-jsonpath is trying to parse whole json payload.
Attached test-jsonpath.zip for test/reproduce this issue.
> Camel-jsonpath is parsing whole json payload from 3.10.0
>
>
> Key: CAMEL-19035
> URL: https://issues.apache.org/jira/browse/CAMEL-19035
> Project: Camel
> Issue Type: Bug
> Components: camel-jsonpath
>Affects Versions: 3.11.0
>Reporter: Xilai Dai
>Assignee: Nicolas Filotto
>Priority: Minor
> Attachments: test-jsonpath.zip
>
>
> Given a json payload e.g:
> {code}
> {
> "ABC": "A",
> "VERSION_NO": "BASE",
> "DEF": [
> {
> "GGG": 1,
> "HHH": "N",
> "OOO": [
> {
> "PPP": 1,
> "QQQ": 555.55,
> "RRR": 666.66,
> "SSS": 0,
> "TTT": 777.77
> },
> {
> "PPP": 3,
> "QQQ": .05,
> "RRR": .10,
> "SSS": 0,
> "TTT": .10
> }
> ]
> }
> ]
> }
> {code}
> In case of there is something e.g invalid integer value (.05) in the payload
> - .jsonpath("$.VERSION_NO") works as expected in Camel version less than
> 3.10.0.
> - .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
> than 3.10.0.
> Investigation shows that this regression was starting happening after
> CAMEL-16389.
>
[jira] [Comment Edited] (CAMEL-19035) Camel-jsonpath is parsing whole json payload from 3.10.0
[
https://issues.apache.org/jira/browse/CAMEL-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688731#comment-17688731
]
Nicolas Filotto edited comment on CAMEL-19035 at 2/14/23 10:29 PM:
---
Camel changed of default {{jsonProvider}} from {{json-smart}}
({{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}}) to {{Jackson}}
({{com.jayway.jsonpath.spi.json.JacksonJsonProvider}}). The behavior change
comes from [the
commit|https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee]
corresponding to https://issues.apache.org/jira/browse/CAMEL-16389. The change
is due to a vulnerability issue
[CVE-2021-27568|https://nvd.nist.gov/vuln/detail/CVE-2021-27568] in
{{json-smart}} that is the reason why
{{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}} is no more used and
{{net.minidev.json-smart`}} excluded from the dependencies. Even if it has been
fixed in 2.4.7 (version used by {{json-path}}), the library
https://github.com/netplex/json-smart-v1 is no more active (no activity in the
past 2 years) so it has been decided to switch definitively to the Jackson Json
provider.
was (Author: JIRAUSER285918):
Camel changed of default {{jsonProvider}} from {{json-smart}}
({{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}}) to {{Jackson}}
({{com.jayway.jsonpath.spi.json.JacksonJsonProvider}}). The behavior change
comes from [the
commit|https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee]
corresponding to https://issues.apache.org/jira/browse/CAMEL-16389. The change
is due to a vulnerability issue
[CVE-2021-27568|https://nvd.nist.gov/vuln/detail/CVE-2021-27568] in
{{json-smart}} that is the reason why
{{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}} is no more used. Even if
it has been fixed in 2.4.7 (version used by {{json-path}}), the library
https://github.com/netplex/json-smart-v1 is no more active (no activity in the
past 2 years) so it has been decided to switch definitively to the Jackson Json
provider.
> Camel-jsonpath is parsing whole json payload from 3.10.0
>
>
> Key: CAMEL-19035
> URL: https://issues.apache.org/jira/browse/CAMEL-19035
> Project: Camel
> Issue Type: Bug
> Components: camel-jsonpath
>Affects Versions: 3.11.0
>Reporter: Xilai Dai
>Assignee: Nicolas Filotto
>Priority: Minor
> Attachments: test-jsonpath.zip
>
>
> Given a json payload e.g:
> {code}
> {
> "ABC": "A",
> "VERSION_NO": "BASE",
> "DEF": [
> {
> "GGG": 1,
> "HHH": "N",
> "OOO": [
> {
> "PPP": 1,
> "QQQ": 555.55,
> "RRR": 666.66,
> "SSS": 0,
> "TTT": 777.77
> },
> {
> "PPP": 3,
> "QQQ": .05,
> "RRR": .10,
> "SSS": 0,
> "TTT": .10
> }
> ]
> }
> ]
> }
> {code}
> In case of there is something e.g invalid integer value (.05) in the payload
> - .jsonpath("$.VERSION_NO") works as expected in Camel version less than
> 3.10.0.
> - .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
> than 3.10.0.
> Investigation shows that this regression was starting happening after
> CAMEL-16397.
> https://github.com/apache/camel/commit/e9e8ed2057f0122f30664eb123ca00775a69c538
>
> Now camel-jsonpath is trying to parse whole json payload.
> Attached test-jsonpath.zip for test/reproduce this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-19035) Camel-jsonpath is parsing whole json payload from 3.10.0
[
https://issues.apache.org/jira/browse/CAMEL-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688731#comment-17688731
]
Nicolas Filotto edited comment on CAMEL-19035 at 2/14/23 10:29 PM:
---
Camel changed of default {{jsonProvider}} from {{json-smart}}
({{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}}) to {{Jackson}}
({{com.jayway.jsonpath.spi.json.JacksonJsonProvider}}). The behavior change
comes from [the
commit|https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee]
corresponding to https://issues.apache.org/jira/browse/CAMEL-16389. The change
is due to a vulnerability issue
[CVE-2021-27568|https://nvd.nist.gov/vuln/detail/CVE-2021-27568] in
{{json-smart}} that is the reason why
{{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}} is no more used and
{{net.minidev.json-smart}} is excluded from the dependencies. Even if it has
been fixed in 2.4.7 (version used by {{json-path}}), the library
https://github.com/netplex/json-smart-v1 is no more active (no activity in the
past 2 years) so it has been decided to switch definitively to the Jackson Json
provider.
was (Author: JIRAUSER285918):
Camel changed of default {{jsonProvider}} from {{json-smart}}
({{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}}) to {{Jackson}}
({{com.jayway.jsonpath.spi.json.JacksonJsonProvider}}). The behavior change
comes from [the
commit|https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee]
corresponding to https://issues.apache.org/jira/browse/CAMEL-16389. The change
is due to a vulnerability issue
[CVE-2021-27568|https://nvd.nist.gov/vuln/detail/CVE-2021-27568] in
{{json-smart}} that is the reason why
{{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}} is no more used and
{{net.minidev.json-smart`}} excluded from the dependencies. Even if it has been
fixed in 2.4.7 (version used by {{json-path}}), the library
https://github.com/netplex/json-smart-v1 is no more active (no activity in the
past 2 years) so it has been decided to switch definitively to the Jackson Json
provider.
> Camel-jsonpath is parsing whole json payload from 3.10.0
>
>
> Key: CAMEL-19035
> URL: https://issues.apache.org/jira/browse/CAMEL-19035
> Project: Camel
> Issue Type: Bug
> Components: camel-jsonpath
>Affects Versions: 3.11.0
>Reporter: Xilai Dai
>Assignee: Nicolas Filotto
>Priority: Minor
> Attachments: test-jsonpath.zip
>
>
> Given a json payload e.g:
> {code}
> {
> "ABC": "A",
> "VERSION_NO": "BASE",
> "DEF": [
> {
> "GGG": 1,
> "HHH": "N",
> "OOO": [
> {
> "PPP": 1,
> "QQQ": 555.55,
> "RRR": 666.66,
> "SSS": 0,
> "TTT": 777.77
> },
> {
> "PPP": 3,
> "QQQ": .05,
> "RRR": .10,
> "SSS": 0,
> "TTT": .10
> }
> ]
> }
> ]
> }
> {code}
> In case of there is something e.g invalid integer value (.05) in the payload
> - .jsonpath("$.VERSION_NO") works as expected in Camel version less than
> 3.10.0.
> - .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
> than 3.10.0.
> Investigation shows that this regression was starting happening after
> CAMEL-16397.
> https://github.com/apache/camel/commit/e9e8ed2057f0122f30664eb123ca00775a69c538
>
> Now camel-jsonpath is trying to parse whole json payload.
> Attached test-jsonpath.zip for test/reproduce this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-19035) Camel-jsonpath is parsing whole json payload from 3.10.0
[
https://issues.apache.org/jira/browse/CAMEL-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688731#comment-17688731
]
Nicolas Filotto edited comment on CAMEL-19035 at 2/14/23 10:27 PM:
---
Camel changed of default {{jsonProvider}} from {{json-smart}}
({{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}}) to {{Jackson}}
({{com.jayway.jsonpath.spi.json.JacksonJsonProvider}}). The behavior change
comes from [the
commit|https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee]
corresponding to https://issues.apache.org/jira/browse/CAMEL-16389. The change
is due to a vulnerability issue
[CVE-2021-27568|https://nvd.nist.gov/vuln/detail/CVE-2021-27568] in
{{json-smart}} that is the reason why
{{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}} is no more used. Even if
it has been fixed in 2.4.7 (version used by {{json-path}}), the library
https://github.com/netplex/json-smart-v1 is no more active (no activity in the
past 2 years) so it has been decided to switch definitively to the Jackson Json
provider.
was (Author: JIRAUSER285918):
Camel changed of default {{jsonProvider}} from {{json-smart}}
({{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}}) to {{Jakson}}
({{com.jayway.jsonpath.spi.json.JacksonJsonProvider}}). The behavior change
comes from [the
commit|https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee]
corresponding to https://issues.apache.org/jira/browse/CAMEL-16389. The change
is due to a vulnerability issue
[CVE-2021-27568|https://nvd.nist.gov/vuln/detail/CVE-2021-27568] in
{{json-smart}} that is the reason why
{{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}} is no more used. Even if
it has been fixed in 2.4.7 (version used by {{json-path}}), the library
https://github.com/netplex/json-smart-v1 is no more active (no activity in the
past 2 years) so it has been decided to switch definitively to the Jackson Json
provider.
> Camel-jsonpath is parsing whole json payload from 3.10.0
>
>
> Key: CAMEL-19035
> URL: https://issues.apache.org/jira/browse/CAMEL-19035
> Project: Camel
> Issue Type: Bug
> Components: camel-jsonpath
>Affects Versions: 3.11.0
>Reporter: Xilai Dai
>Assignee: Nicolas Filotto
>Priority: Minor
> Attachments: test-jsonpath.zip
>
>
> Given a json payload e.g:
> {code}
> {
> "ABC": "A",
> "VERSION_NO": "BASE",
> "DEF": [
> {
> "GGG": 1,
> "HHH": "N",
> "OOO": [
> {
> "PPP": 1,
> "QQQ": 555.55,
> "RRR": 666.66,
> "SSS": 0,
> "TTT": 777.77
> },
> {
> "PPP": 3,
> "QQQ": .05,
> "RRR": .10,
> "SSS": 0,
> "TTT": .10
> }
> ]
> }
> ]
> }
> {code}
> In case of there is something e.g invalid integer value (.05) in the payload
> - .jsonpath("$.VERSION_NO") works as expected in Camel version less than
> 3.10.0.
> - .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
> than 3.10.0.
> Investigation shows that this regression was starting happening after
> CAMEL-16397.
> https://github.com/apache/camel/commit/e9e8ed2057f0122f30664eb123ca00775a69c538
>
> Now camel-jsonpath is trying to parse whole json payload.
> Attached test-jsonpath.zip for test/reproduce this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19035) Camel-jsonpath is parsing whole json payload from 3.10.0
[
https://issues.apache.org/jira/browse/CAMEL-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688731#comment-17688731
]
Nicolas Filotto commented on CAMEL-19035:
-
Camel changed of default {{jsonProvider}} from {{json-smart}}
({{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}}) to {{Jakson}}
({{com.jayway.jsonpath.spi.json.JacksonJsonProvider}}). The behavior change
comes from [the
commit|https://github.com/apache/camel/commit/b59a96ddf1ba647b979f937f5bd956bba32173ee]
corresponding to https://issues.apache.org/jira/browse/CAMEL-16389. The change
is due to a vulnerability issue
[CVE-2021-27568|https://nvd.nist.gov/vuln/detail/CVE-2021-27568] in
{{json-smart}} that is the reason why
{{com.jayway.jsonpath.spi.json.JsonSmartJsonProvider}} is no more used. Even if
it has been fixed in 2.4.7 (version used by {{json-path}}), the library
https://github.com/netplex/json-smart-v1 is no more active (no activity in the
past 2 years) so it has been decided to switch definitively to the Jackson Json
provider.
> Camel-jsonpath is parsing whole json payload from 3.10.0
>
>
> Key: CAMEL-19035
> URL: https://issues.apache.org/jira/browse/CAMEL-19035
> Project: Camel
> Issue Type: Bug
> Components: camel-jsonpath
>Affects Versions: 3.11.0
>Reporter: Xilai Dai
>Assignee: Nicolas Filotto
>Priority: Minor
> Attachments: test-jsonpath.zip
>
>
> Given a json payload e.g:
> {code}
> {
> "ABC": "A",
> "VERSION_NO": "BASE",
> "DEF": [
> {
> "GGG": 1,
> "HHH": "N",
> "OOO": [
> {
> "PPP": 1,
> "QQQ": 555.55,
> "RRR": 666.66,
> "SSS": 0,
> "TTT": 777.77
> },
> {
> "PPP": 3,
> "QQQ": .05,
> "RRR": .10,
> "SSS": 0,
> "TTT": .10
> }
> ]
> }
> ]
> }
> {code}
> In case of there is something e.g invalid integer value (.05) in the payload
> - .jsonpath("$.VERSION_NO") works as expected in Camel version less than
> 3.10.0.
> - .jsonpath("$.VERSION_NO") will throw parse exception in Camel version great
> than 3.10.0.
> Investigation shows that this regression was starting happening after
> CAMEL-16397.
> https://github.com/apache/camel/commit/e9e8ed2057f0122f30664eb123ca00775a69c538
>
> Now camel-jsonpath is trying to parse whole json payload.
> Attached test-jsonpath.zip for test/reproduce this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19050) DHIS2 Component
[ https://issues.apache.org/jira/browse/CAMEL-19050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Mamo updated CAMEL-19050: Description: The DHIS2 team is maintaining an Apache Camel component that leverages the DHIS2 Java SDK to integrate Apache Camel with the DHIS2 Web API. We'd like to add this component to the Apache Camel distribution. PRs contributing the component will be opened soon on the main and 3.x branches. (was: The DHIS2 team is maintaining an Apache Camel component that leverages the DHIS2 Java SDK to integrate Apache Camel with the DHIS2 Web API. We'd like to add this component to the Apache Camel distribution. PRs contributing the component will be opened soon on the main and 3.20.x branches.) > DHIS2 Component > --- > > Key: CAMEL-19050 > URL: https://issues.apache.org/jira/browse/CAMEL-19050 > Project: Camel > Issue Type: New Feature >Reporter: Claude Mamo >Priority: Major > > The DHIS2 team is maintaining an Apache Camel component that leverages the > DHIS2 Java SDK to integrate Apache Camel with the DHIS2 Web API. We'd like to > add this component to the Apache Camel distribution. PRs contributing the > component will be opened soon on the main and 3.x branches. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19050) DHIS2 Component
Claude Mamo created CAMEL-19050: --- Summary: DHIS2 Component Key: CAMEL-19050 URL: https://issues.apache.org/jira/browse/CAMEL-19050 Project: Camel Issue Type: New Feature Reporter: Claude Mamo The DHIS2 team is maintaining an Apache Camel component that leverages the DHIS2 Java SDK to integrate Apache Camel with the DHIS2 Web API. We'd like to add this component to the Apache Camel distribution. PRs contributing the component will be opened soon on the main and 3.20.x branches. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19049) camel-bean: AmbiguousMethodCallException when using OSGi service reference
[
https://issues.apache.org/jira/browse/CAMEL-19049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rastislav Papp updated CAMEL-19049:
---
Component/s: camel-bean
(was: camel-karaf)
> camel-bean: AmbiguousMethodCallException when using OSGi service reference
> --
>
> Key: CAMEL-19049
> URL: https://issues.apache.org/jira/browse/CAMEL-19049
> Project: Camel
> Issue Type: Bug
> Components: camel-bean
>Affects Versions: 3.14.6
>Reporter: Rastislav Papp
>Priority: Critical
>
> After upgrading from 3.14.4 to 3.14.6 we can no longer call camel bean method
> on an instance of OSGI service which implements an interface. This is caused
> by the changes introduced in CAMEL-18411.
> Example:
> route:
> {code:java}
> public class TestRoute extends RouteBuilder {
> @BeanInject
> private MyInterface myInterface;
> @Override
> public void configure() {
> from("...")
> .bean(myInterface, "reinit");
> }
> }
> {code}
> The {{MyInterface}} is:
> {code}
> public interface MyInterface {
> void reinit();
> }
> {code}
> The object inserted is a proxy reference to OSGI service, injected by
> blueprint in karaf runtime.
> Stacktrace:
> {code}
> org.apache.camel.component.bean.AmbiguousMethodCallException: Ambiguous
> method invocations possible: [public void
> Proxyb113d9d3_4aac_4ac9_b619_9bb68d221255.reinit(), public abstract void
> foo.bar.MyInterface.reinit()] on the exchange:
> Exchange[92BC3141E43445D-003F] at
> org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:246)
> at
> org.apache.camel.component.bean.AbstractBeanProcessor.process(AbstractBeanProcessor.java:126)
> at
> org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:81)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:818)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:726)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:185) at
> {code}
> The ambiguousness is caused by the {{reinit()}} method detected twice - once
> from the interface, and one from the {{Proxy}} class.
> I'm working on a solution.
> cc: [~AWeickel]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19049) camel-bean: AmbiguousMethodCallException when using OSGi service reference
[
https://issues.apache.org/jira/browse/CAMEL-19049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rastislav Papp updated CAMEL-19049:
---
Description:
After upgrading from 3.14.4 to 3.14.6 we can no longer call camel bean method
on an instance of OSGI service which implements an interface. This is caused by
the changes introduced in CAMEL-18411.
Example:
route:
{code:java}
public class TestRoute extends RouteBuilder {
@BeanInject
private MyInterface myInterface;
@Override
public void configure() {
from("...")
.bean(myInterface, "reinit");
}
}
{code}
The {{MyInterface}} is:
{code}
public interface MyInterface {
void reinit();
}
{code}
The object injected is a proxy reference to OSGI service, injected by blueprint
in karaf runtime.
Stacktrace:
{code}
org.apache.camel.component.bean.AmbiguousMethodCallException: Ambiguous method
invocations possible: [public void
Proxyb113d9d3_4aac_4ac9_b619_9bb68d221255.reinit(), public abstract void
foo.bar.MyInterface.reinit()] on the exchange:
Exchange[92BC3141E43445D-003F] at
org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:246) at
org.apache.camel.component.bean.AbstractBeanProcessor.process(AbstractBeanProcessor.java:126)
at
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:81) at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:818)
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:726)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:185) at
{code}
The ambiguousness is caused by the {{reinit()}} method detected twice - once
from the interface, and one from the {{Proxy}} class.
I'm working on a solution.
cc: [~AWeickel]
was:
After upgrading from 3.14.4 to 3.14.6 we can no longer call camel bean method
on an instance of OSGI service which implements an interface. This is caused by
the changes introduced in CAMEL-18411.
Example:
route:
{code:java}
public class TestRoute extends RouteBuilder {
@BeanInject
private MyInterface myInterface;
@Override
public void configure() {
from("...")
.bean(myInterface, "reinit");
}
}
{code}
The {{MyInterface}} is:
{code}
public interface MyInterface {
void reinit();
}
{code}
The object inserted is a proxy reference to OSGI service, injected by blueprint
in karaf runtime.
Stacktrace:
{code}
org.apache.camel.component.bean.AmbiguousMethodCallException: Ambiguous method
invocations possible: [public void
Proxyb113d9d3_4aac_4ac9_b619_9bb68d221255.reinit(), public abstract void
foo.bar.MyInterface.reinit()] on the exchange:
Exchange[92BC3141E43445D-003F] at
org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:246) at
org.apache.camel.component.bean.AbstractBeanProcessor.process(AbstractBeanProcessor.java:126)
at
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:81) at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:818)
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:726)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:185) at
{code}
The ambiguousness is caused by the {{reinit()}} method detected twice - once
from the interface, and one from the {{Proxy}} class.
I'm working on a solution.
cc: [~AWeickel]
> camel-bean: AmbiguousMethodCallException when using OSGi service reference
> --
>
> Key: CAMEL-19049
> URL: https://issues.apache.org/jira/browse/CAMEL-19049
> Project: Camel
> Issue Type: Bug
> Components: camel-bean
>Affects Versions: 3.14.6
>Reporter: Rastislav Papp
>Priority: Critical
>
> After upgrading from 3.14.4 to 3.14.6 we can no longer call camel bean method
> on an instance of OSGI service which implements an interface. This is caused
> by the changes introduced in CAMEL-18411.
> Example:
> route:
> {code:java}
> public class TestRoute extends RouteBuilder {
> @BeanInject
> private MyInterface myInterface;
> @Override
> public void configure() {
> from("...")
> .bean(myInterface, "reinit");
> }
> }
> {code}
>
[jira] [Created] (CAMEL-19049) camel-bean: AmbiguousMethodCallException when using OSGi service reference
Rastislav Papp created CAMEL-19049:
--
Summary: camel-bean: AmbiguousMethodCallException when using OSGi
service reference
Key: CAMEL-19049
URL: https://issues.apache.org/jira/browse/CAMEL-19049
Project: Camel
Issue Type: Bug
Components: camel-karaf
Affects Versions: 3.14.6
Reporter: Rastislav Papp
After upgrading from 3.14.4 to 3.14.6 we can no longer call camel bean method
on an instance of OSGI service which implements an interface. This is caused by
the changes introduced in CAMEL-18411.
Example:
route:
{code:java}
public class TestRoute extends RouteBuilder {
@BeanInject
private MyInterface myInterface;
@Override
public void configure() {
from("...")
.bean(myInterface, "reinit");
}
}
{code}
The {{MyInterface}} is:
{code}
public interface MyInterface {
void reinit();
}
{code}
The object inserted is a proxy reference to OSGI service, injected by blueprint
in karaf runtime.
Stacktrace:
{code}
org.apache.camel.component.bean.AmbiguousMethodCallException: Ambiguous method
invocations possible: [public void
Proxyb113d9d3_4aac_4ac9_b619_9bb68d221255.reinit(), public abstract void
foo.bar.MyInterface.reinit()] on the exchange:
Exchange[92BC3141E43445D-003F] at
org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:246) at
org.apache.camel.component.bean.AbstractBeanProcessor.process(AbstractBeanProcessor.java:126)
at
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:81) at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:818)
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:726)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:185) at
{code}
The ambiguousness is caused by the {{reinit()}} method detected twice - once
from the interface, and one from the {{Proxy}} class.
I'm working on a solution.
cc: [~AWeickel]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19048) camel-jbang - Add color to commands
Claus Ibsen created CAMEL-19048: --- Summary: camel-jbang - Add color to commands Key: CAMEL-19048 URL: https://issues.apache.org/jira/browse/CAMEL-19048 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Fix For: 4.0 The ListTrace has color output. We should make all commands output in color. And have some util method to make this easy to avoid copying to much code around. We should also make it possible to not output in color --color=false And later when we have settings then the user can default choose to turn it on or off Something ala: camel config set color=false -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19032) saga timeout value isn't depends on the min of the all participants like official doc described.
[ https://issues.apache.org/jira/browse/CAMEL-19032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688419#comment-17688419 ] adam chen commented on CAMEL-19032: --- [~zhfeng] yeah, I think the doc should be fixed. > saga timeout value isn't depends on the min of the all participants like > official doc described. > > > Key: CAMEL-19032 > URL: https://issues.apache.org/jira/browse/CAMEL-19032 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.19.0 >Reporter: adam chen >Priority: Major > Attachments: 2023-02-01-13-57-16.jpg, RouteCode.jpg > > Original Estimate: 120h > Remaining Estimate: 120h > > In my test result isn't like offical explanation (All participants (e.g. > credit service, order service) can set their own timeout. The minimum value > of those timeouts is taken as timeout for the saga when they are composed > together.) In my result show that saga timeut value is depending on first > participant's timeout value, not the minimum vlaue of participants. [Test > code|https://github.com/chen19980/SAGA_timeout_test] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19047) CamelTestSupport (junit5) - quarkus and springboot checks are not executed with ContextPerClass
Jiri Ondrusek created CAMEL-19047: - Summary: CamelTestSupport (junit5) - quarkus and springboot checks are not executed with ContextPerClass Key: CAMEL-19047 URL: https://issues.apache.org/jira/browse/CAMEL-19047 Project: Camel Issue Type: Bug Components: camel-test Affects Versions: 4.0-M1 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek There is a code in `CamelTestSupport` which verifies whether the right test parent is used in Quarkus or Spring-boot ([code|https://github.com/apache/camel/blob/main/components/camel-test/camel-test-junit5/src/main/java/org/apache/camel/test/junit5/CamelTestSupport.java#L373-L374]). These checks should be move above the `if` condition, to be called even if `Lifecycle.PER_CLASS` is used. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-13090) Update to servlet api 4
[ https://issues.apache.org/jira/browse/CAMEL-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13090. - Fix Version/s: 4.0-M1 Resolution: Fixed > Update to servlet api 4 > --- > > Key: CAMEL-13090 > URL: https://issues.apache.org/jira/browse/CAMEL-13090 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0, 4.0-M1 > > > Lets see if we can upgrade to servlet api 4. Currently we are on 3. > We would need to wait for OSGi to get working on master branch and then see > if karaf/osgi can work with servlet api 4. > Spring Boot 2 is supporting servlet api 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-14680) javax -> jakarta
[ https://issues.apache.org/jira/browse/CAMEL-14680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14680. - Fix Version/s: 4.0-M1 Resolution: Fixed > javax -> jakarta > > > Key: CAMEL-14680 > URL: https://issues.apache.org/jira/browse/CAMEL-14680 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0, 4.0-M1 > > > When the industry switches from javax to jarkarta then we should follow up as > well. > Its mostly JMS, Servlet, Mail, CDI, WS, JAX-RS, and other components. So at > some day we may have a release that switches fully over and is not backwards > compatible. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-16352) Generate JARS without OSGi metadata
[ https://issues.apache.org/jira/browse/CAMEL-16352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16352. - Fix Version/s: 4.0-M1 Resolution: Fixed > Generate JARS without OSGi metadata > --- > > Key: CAMEL-16352 > URL: https://issues.apache.org/jira/browse/CAMEL-16352 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0, 4.0-M1 > > > Just a ticket to remind that if we get camel-karaf to provide all JARs for > OSGi and with OSGi metadata in their MANIFEST.MF entires. > Then we can remove this from core Camel and that actually leads to reduce > memory footprint. As the OSGi manifest is very verbose and takes up memory > that is not for any good for non OSGi users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18824) upgrade to newer guava versions
[
https://issues.apache.org/jira/browse/CAMEL-18824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18824.
-
Fix Version/s: 4.0-M2
Resolution: Fixed
> upgrade to newer guava versions
> ---
>
> Key: CAMEL-18824
> URL: https://issues.apache.org/jira/browse/CAMEL-18824
> Project: Camel
> Issue Type: Dependency upgrade
> Components: build system
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 4.0-M2, 4.0
>
>
> We have a mix of different guava versions (mostly due to osgi import|export)
> restrictions.
> We can see if we can harmonize to use more same version and also upgrade to
> newer.
> We need > 24.1.1 due to CVEs in older versions
> pom.xml:20.0
> pom.xml:
> 30.1
> pom.xml:
> ${google-cloud-guava-version-prefix}-jre
> pom.xml:31.1-jre
> pom.xml:28.2-jre
> pom.xml:29.0-jre
> pom.xml:20.0
> pom.xml:
> pom.xml:
> 27.1-jre
> pom.xml:
> [27.0,28.0)
> pom.xml:31.1-jre
> pom.xml:30.1.1-jre
> pom.xml:21.0
> pom.xml:31.1-jre
> pom.xml:
> 27.1-jre
> pom.xml:31.1-jre
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18930) camel-spring-boot - Migrate undertow-security
[ https://issues.apache.org/jira/browse/CAMEL-18930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18930. - Resolution: Fixed > camel-spring-boot - Migrate undertow-security > - > > Key: CAMEL-18930 > URL: https://issues.apache.org/jira/browse/CAMEL-18930 > Project: Camel > Issue Type: Task > Components: camel-spring-boot-starters >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0-M2, 4.0 > > > https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18921) itests jakarta upgrade: Use Artemis and JmsComponent
[ https://issues.apache.org/jira/browse/CAMEL-18921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18921. - Fix Version/s: 4.0-M1 Resolution: Fixed > itests jakarta upgrade: Use Artemis and JmsComponent > > > Key: CAMEL-18921 > URL: https://issues.apache.org/jira/browse/CAMEL-18921 > Project: Camel > Issue Type: Test >Affects Versions: 4.0 >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Major > Fix For: 4.0, 4.0-M1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18930) camel-spring-boot - Migrate undertow-security
[ https://issues.apache.org/jira/browse/CAMEL-18930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18930: Fix Version/s: 4.0-M2 > camel-spring-boot - Migrate undertow-security > - > > Key: CAMEL-18930 > URL: https://issues.apache.org/jira/browse/CAMEL-18930 > Project: Camel > Issue Type: Task > Components: camel-spring-boot-starters >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0-M2, 4.0 > > > https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18946) camel-spring-boot - Upgrade to 3.0.2
[ https://issues.apache.org/jira/browse/CAMEL-18946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18946. - Fix Version/s: 4.0-M1 Resolution: Fixed > camel-spring-boot - Upgrade to 3.0.2 > > > Key: CAMEL-18946 > URL: https://issues.apache.org/jira/browse/CAMEL-18946 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0, 4.0-M1 > > > Is expected to be released tomorrrow -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19046) camel-core - Categorize error into source, processor or sink
Claus Ibsen created CAMEL-19046: --- Summary: camel-core - Categorize error into source, processor or sink Key: CAMEL-19046 URL: https://issues.apache.org/jira/browse/CAMEL-19046 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 4.0 We would like to be able to categorize an error (exception thrown) by Camel routing engine whether that error happend in the consumer/source, during processing (routing) or in the producer/sink (sending to external system). This can better assist where a problem lies, i.e. source and sink are related to external systems, processing is related to Camel or custom end user integration/business logic. We can also have some kind of SPI to introspect the thrown exception and error message, to enrich error details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
