[jira] [Commented] (CAMEL-16001) Camel component // Huawei Cloud Simple Notification Services (SMN)
[ https://issues.apache.org/jira/browse/CAMEL-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266397#comment-17266397 ] Reji Mathews commented on CAMEL-16001: -- PR was raised against 3.4.0 branch. As per review comments from [~acosentino], I will shortly raise a fresh PR against the master branch. > Camel component // Huawei Cloud Simple Notification Services (SMN) > -- > > Key: CAMEL-16001 > URL: https://issues.apache.org/jira/browse/CAMEL-16001 > Project: Camel > Issue Type: New Feature >Affects Versions: 3.4.0 >Reporter: Reji Mathews >Priority: Minor > > New camel component to integrate with huawei cloud - [Simple Notification > Services](https://support.huaweicloud.com/en-us/productdesc-smn/en-us_topic_0043394877.html) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16001) Camel component // Huawei Cloud Simple Notification Services (SMN)
[ https://issues.apache.org/jira/browse/CAMEL-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266382#comment-17266382 ] Reji Mathews commented on CAMEL-16001: -- A draft version is available for review at https://github.com/apache/camel/pull/4894 . I am still waiting on HuaweiCloud SDK team for their release candidate version to be published. > Camel component // Huawei Cloud Simple Notification Services (SMN) > -- > > Key: CAMEL-16001 > URL: https://issues.apache.org/jira/browse/CAMEL-16001 > Project: Camel > Issue Type: New Feature >Affects Versions: 3.4.0 >Reporter: Reji Mathews >Priority: Minor > > New camel component to integrate with huawei cloud - [Simple Notification > Services](https://support.huaweicloud.com/en-us/productdesc-smn/en-us_topic_0043394877.html) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (CAMEL-16001) Camel component // Huawei Cloud Simple Notification Services (SMN)
[ https://issues.apache.org/jira/browse/CAMEL-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reji Mathews updated CAMEL-16001: - Comment: was deleted (was: A draft version is available for review at [https://github.com/apache/camel/pull/4893] . I am still waiting on HuaweiCloud SDK team for their release candidate version to be published. ) > Camel component // Huawei Cloud Simple Notification Services (SMN) > -- > > Key: CAMEL-16001 > URL: https://issues.apache.org/jira/browse/CAMEL-16001 > Project: Camel > Issue Type: New Feature >Affects Versions: 3.4.0 >Reporter: Reji Mathews >Priority: Minor > > New camel component to integrate with huawei cloud - [Simple Notification > Services](https://support.huaweicloud.com/en-us/productdesc-smn/en-us_topic_0043394877.html) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16001) Camel component // Huawei Cloud Simple Notification Services (SMN)
[ https://issues.apache.org/jira/browse/CAMEL-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266377#comment-17266377 ] Reji Mathews commented on CAMEL-16001: -- A draft version is available for review at [https://github.com/apache/camel/pull/4893] . I am still waiting on HuaweiCloud SDK team for their release candidate version to be published. > Camel component // Huawei Cloud Simple Notification Services (SMN) > -- > > Key: CAMEL-16001 > URL: https://issues.apache.org/jira/browse/CAMEL-16001 > Project: Camel > Issue Type: New Feature >Affects Versions: 3.4.0 >Reporter: Reji Mathews >Priority: Minor > > New camel component to integrate with huawei cloud - [Simple Notification > Services](https://support.huaweicloud.com/en-us/productdesc-smn/en-us_topic_0043394877.html) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16047) Error building camel 3.7.0 with jdk11
[ https://issues.apache.org/jira/browse/CAMEL-16047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16047: Issue Type: Task (was: Bug) > Error building camel 3.7.0 with jdk11 > - > > Key: CAMEL-16047 > URL: https://issues.apache.org/jira/browse/CAMEL-16047 > Project: Camel > Issue Type: Task > Components: camel-catalog >Reporter: Thomas Cunningham >Priority: Major > Fix For: 3.7.1, 3.8.0 > > > Getting an error trying to build camel 3.7.0 with jdk11 : > Caused by: java.io.FileNotFoundException: > /tmp/camel-3.7.0/catalog/camel-catalog/target/../../etc/apache-header.xml (No > such file or directory) > Can be fixed by setting the property in camel-catalog. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16047) Error building camel 3.7.0 with jdk11
[ https://issues.apache.org/jira/browse/CAMEL-16047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16047. - Fix Version/s: 3.8.0 3.7.1 Resolution: Fixed > Error building camel 3.7.0 with jdk11 > - > > Key: CAMEL-16047 > URL: https://issues.apache.org/jira/browse/CAMEL-16047 > Project: Camel > Issue Type: Bug > Components: camel-catalog >Reporter: Thomas Cunningham >Priority: Major > Fix For: 3.7.1, 3.8.0 > > > Getting an error trying to build camel 3.7.0 with jdk11 : > Caused by: java.io.FileNotFoundException: > /tmp/camel-3.7.0/catalog/camel-catalog/target/../../etc/apache-header.xml (No > such file or directory) > Can be fixed by setting the property in camel-catalog. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16047) Error building camel 3.7.0 with jdk11
[ https://issues.apache.org/jira/browse/CAMEL-16047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266308#comment-17266308 ] Thomas Cunningham commented on CAMEL-16047: --- https://github.com/apache/camel/pull/4892 > Error building camel 3.7.0 with jdk11 > - > > Key: CAMEL-16047 > URL: https://issues.apache.org/jira/browse/CAMEL-16047 > Project: Camel > Issue Type: Bug > Components: camel-catalog >Reporter: Thomas Cunningham >Priority: Major > > Getting an error trying to build camel 3.7.0 with jdk11 : > Caused by: java.io.FileNotFoundException: > /tmp/camel-3.7.0/catalog/camel-catalog/target/../../etc/apache-header.xml (No > such file or directory) > Can be fixed by setting the property in camel-catalog. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16047) Error building camel 3.7.0 with jdk11
Thomas Cunningham created CAMEL-16047: - Summary: Error building camel 3.7.0 with jdk11 Key: CAMEL-16047 URL: https://issues.apache.org/jira/browse/CAMEL-16047 Project: Camel Issue Type: Bug Components: camel-catalog Reporter: Thomas Cunningham Getting an error trying to build camel 3.7.0 with jdk11 : Caused by: java.io.FileNotFoundException: /tmp/camel-3.7.0/catalog/camel-catalog/target/../../etc/apache-header.xml (No such file or directory) Can be fixed by setting the property in camel-catalog. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16032) [camel-main] autoconfiguration does not bind dataformat in the registry
[ https://issues.apache.org/jira/browse/CAMEL-16032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16032. - Resolution: Fixed > [camel-main] autoconfiguration does not bind dataformat in the registry > > > Key: CAMEL-16032 > URL: https://issues.apache.org/jira/browse/CAMEL-16032 > Project: Camel > Issue Type: Bug > Components: camel-main >Affects Versions: 3.7.0 >Reporter: Luigi De Masi >Assignee: Luigi De Masi >Priority: Major > Fix For: 3.7.1, 3.8.0 > > Attachments: 816.zip > > > Configuring a dataformat through properties does not work because after > setting the properties, the dataformat bean is not bound in the registry and > when the route starts, the dataformat is recreated: > [https://pastebin.com/raw/Tf05i7FK] > Attached a reproducer [^816.zip] with FHIR dataformat, but it's the same for > every dataformat; -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16046) camel-ahc-ws client serving as both a producer and consumer
[
https://issues.apache.org/jira/browse/CAMEL-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh West updated CAMEL-16046:
--
Description:
While subscribing to a websocket using camel-ahc-ws the connection and session
is sometimes bidirectional. A session may be initiated to subscribe to
specific data points by sending a message over the same session as the producer
(incoming) exchange.
from("ahc-wss://ws-feed.example.com").routeId("incoming")
.log("received message: ${body}");
from("timer:wssfeedInitaitor?delay=10=1").routeId("feed-initiator")
.setBody().constant(WSS_SUBSCRIBE)
.to("ahc-wss://ws-feed.example.com")
.log("received message on initiator: ${body}");
The current behavior is that the "incoming" route connects but doesn't receive
any data.
The "feed-initiator" router successfully sends the subscribe message to the
remote endpoint and starts receiving data. The websocket data received is only
showing up in WsListener DEBUG logging messages "[cHttpClient-3-1]
o.a.camel.component.ahc.ws.WsEndpoint : Received message --> ..." without the
data on the exchange. The logging is coming from the "feed-initator" route,
which is not logging messages using the route given the initiator is in wrong
mode.
Is there a way to share the same session?
Otherwise can the component be enhanced to serve as both a producer and
consumer at the same time?
was:
While subscribing to a websocket using camel-ahc-ws the connection and session
is sometimes bidirectional. A session may be initiated to subscribe to
specific data points by sending a message over the same session as the producer
(incoming) exchange.
from("ahc-wss://ws-feed.example.com").routeId("incoming")
.log("received message: ${body}");
from("timer:wssfeedInitaitor?delay=10=1").routeId("feed-initiator")
.setBody().constant(WSS_SUBSCRIBE)
.to("ahc-wss://ws-feed.example.com")
.log("received message on initiator: ${body}");
The current behavior is that the "incoming" route connects but doesn't receive
any data.
The "feed-initiator" router successfully sends the subscribe message to the
remote endpoint and starts receiving data. The websocket data received is only
showing up in WsListener DEBUG logging messages "[cHttpClient-3-1]
o.a.camel.component.ahc.ws.WsEndpoint : Received message --> ..." without the
data on the exchange. The logging is coming from the "feed-initator" route,
which is not logging messages using the route given the initiator is in
consumer mode.
Is there a way to share the same session?
Otherwise can the component be enhanced to serve as both a producer and
consumer at the same time?
> camel-ahc-ws client serving as both a producer and consumer
> ---
>
> Key: CAMEL-16046
> URL: https://issues.apache.org/jira/browse/CAMEL-16046
> Project: Camel
> Issue Type: Improvement
> Components: camel-ahc-ws
>Affects Versions: 2.23.4
> Environment: N/A
>Reporter: Josh West
>Priority: Minor
> Fix For: Future
>
>
> While subscribing to a websocket using camel-ahc-ws the connection and
> session is sometimes bidirectional. A session may be initiated to subscribe
> to specific data points by sending a message over the same session as the
> producer (incoming) exchange.
>
> from("ahc-wss://ws-feed.example.com").routeId("incoming")
> .log("received message: ${body}");
>
>
> from("timer:wssfeedInitaitor?delay=10=1").routeId("feed-initiator")
> .setBody().constant(WSS_SUBSCRIBE)
> .to("ahc-wss://ws-feed.example.com")
> .log("received message on initiator: ${body}");
>
> The current behavior is that the "incoming" route connects but doesn't
> receive any data.
> The "feed-initiator" router successfully sends the subscribe message to the
> remote endpoint and starts receiving data. The websocket data received is
> only showing up in WsListener DEBUG logging messages "[cHttpClient-3-1]
> o.a.camel.component.ahc.ws.WsEndpoint : Received message --> ..." without the
> data on the exchange. The logging is coming from the "feed-initator" route,
> which is not logging messages using the route given the initiator is in wrong
> mode.
>
> Is there a way to share the same session?
>
> Otherwise can the component be enhanced to serve as both a producer and
> consumer at the same time?
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-16046) camel-ahc-ws client serving as both a producer and consumer
[
https://issues.apache.org/jira/browse/CAMEL-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh West updated CAMEL-16046:
--
Description:
While subscribing to a websocket using camel-ahc-ws the connection and session
is sometimes bidirectional. A session may be initiated to subscribe to
specific data points by sending a message over the same session as the producer
(incoming) exchange.
from("ahc-wss://ws-feed.example.com").routeId("incoming")
.log("received message: ${body}");
from("timer:wssfeedInitaitor?delay=10=1").routeId("feed-initiator")
.setBody().constant(WSS_SUBSCRIBE)
.to("ahc-wss://ws-feed.example.com")
.log("received message on initiator: ${body}");
The current behavior is that the "incoming" route connects but doesn't receive
any data.
The "feed-initiator" router successfully sends the subscribe message to the
remote endpoint and starts receiving data. The websocket data received is only
showing up in WsListener DEBUG logging messages "[cHttpClient-3-1]
o.a.camel.component.ahc.ws.WsEndpoint : Received message --> ..." without the
data on the exchange. The logging is coming from the "feed-initator" route,
which is not logging messages using the route given the initiator is in
consumer mode.
Is there a way to share the same session?
Otherwise can the component be enhanced to serve as both a producer and
consumer at the same time?
was:
While subscribing to a websocket using camel-ahc-ws the connection and session
is sometimes bidirectional. A session may be initiated to subscribe to
specific data points by sending a message over the same session as the producer
(incoming) exchange.
from("ahc-wss://ws-feed.example.com").routeId("incoming")
.log("received message: ${body}");
from("timer:wssfeedInitaitor?delay=10=1").routeId("feed-initiator")
.setBody().constant(WSS_SUBSCRIBE)
.to("ahc-wss://ws-feed.example.com")
.log("received message on initiator: ${body}");
The current behavior is that the "incoming" route connects but doesn't receive
any data.
The "feed-initiator" router successfully sends the subscribe message to the
remote endpoint and starts receiving data. The websocket data received is only
showing up in DEBUG logging messages "[cHttpClient-3-1]
o.a.camel.component.ahc.ws.WsEndpoint : Received message --> ..." without the
data on the exchange.
Is there a way to share the same session?
Otherwise can the component be enhanced to serve as both a producer and
consumer at the same time?
> camel-ahc-ws client serving as both a producer and consumer
> ---
>
> Key: CAMEL-16046
> URL: https://issues.apache.org/jira/browse/CAMEL-16046
> Project: Camel
> Issue Type: Improvement
> Components: camel-ahc-ws
>Affects Versions: 2.23.4
> Environment: N/A
>Reporter: Josh West
>Priority: Minor
> Fix For: Future
>
>
> While subscribing to a websocket using camel-ahc-ws the connection and
> session is sometimes bidirectional. A session may be initiated to subscribe
> to specific data points by sending a message over the same session as the
> producer (incoming) exchange.
>
> from("ahc-wss://ws-feed.example.com").routeId("incoming")
> .log("received message: ${body}");
>
>
> from("timer:wssfeedInitaitor?delay=10=1").routeId("feed-initiator")
> .setBody().constant(WSS_SUBSCRIBE)
> .to("ahc-wss://ws-feed.example.com")
> .log("received message on initiator: ${body}");
>
> The current behavior is that the "incoming" route connects but doesn't
> receive any data.
> The "feed-initiator" router successfully sends the subscribe message to the
> remote endpoint and starts receiving data. The websocket data received is
> only showing up in WsListener DEBUG logging messages "[cHttpClient-3-1]
> o.a.camel.component.ahc.ws.WsEndpoint : Received message --> ..." without the
> data on the exchange. The logging is coming from the "feed-initator" route,
> which is not logging messages using the route given the initiator is in
> consumer mode.
>
> Is there a way to share the same session?
>
> Otherwise can the component be enhanced to serve as both a producer and
> consumer at the same time?
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16001) Camel component // Huawei Cloud Simple Notification Services (SMN)
[ https://issues.apache.org/jira/browse/CAMEL-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266144#comment-17266144 ] Reji Mathews commented on CAMEL-16001: -- Sounds good. Raising PR shortly for review > Camel component // Huawei Cloud Simple Notification Services (SMN) > -- > > Key: CAMEL-16001 > URL: https://issues.apache.org/jira/browse/CAMEL-16001 > Project: Camel > Issue Type: New Feature >Affects Versions: 3.4.0 >Reporter: Reji Mathews >Priority: Minor > > New camel component to integrate with huawei cloud - [Simple Notification > Services](https://support.huaweicloud.com/en-us/productdesc-smn/en-us_topic_0043394877.html) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16045) rest-dsl - xml or json binding should create new instance of data formats
[ https://issues.apache.org/jira/browse/CAMEL-16045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16045. - Resolution: Fixed > rest-dsl - xml or json binding should create new instance of data formats > - > > Key: CAMEL-16045 > URL: https://issues.apache.org/jira/browse/CAMEL-16045 > Project: Camel > Issue Type: Bug > Components: camel-core, rest >Affects Versions: 3.7.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.7.1, 3.8.0 > > > Related to CAMEL-16032. > When you use json or xml binding out of the box they should use their own > private impl of data format as they have custom config that should not affect > other rest-dsl. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15998) Camel-Github: Better structure for consumer returned object
[ https://issues.apache.org/jira/browse/CAMEL-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266108#comment-17266108 ] Andrea Cosentino commented on CAMEL-15998: -- Fixed. > Camel-Github: Better structure for consumer returned object > --- > > Key: CAMEL-15998 > URL: https://issues.apache.org/jira/browse/CAMEL-15998 > Project: Camel > Issue Type: Improvement > Components: camel-git >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.8.0 > > > We can specify something more through headers. The problem is similar to > camel-git, we need to have a plain type as body and enrich the information > through headers. It will be much more easier to use, instead of having to > deal with egit pojos -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15998) Camel-Github: Better structure for consumer returned object
[ https://issues.apache.org/jira/browse/CAMEL-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266104#comment-17266104 ] Andrea Cosentino commented on CAMEL-15998: -- Yeah, it's a copy/paste problem. In this case the fields are just a subset of the original pojo. I don't think there is any values in having the whole Pojo, also end user may not know what kind of class will be in the body (for our fault, because it's not always well documented). In this case I think the essential information are returned. > Camel-Github: Better structure for consumer returned object > --- > > Key: CAMEL-15998 > URL: https://issues.apache.org/jira/browse/CAMEL-15998 > Project: Camel > Issue Type: Improvement > Components: camel-git >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.8.0 > > > We can specify something more through headers. The problem is similar to > camel-git, we need to have a plain type as body and enrich the information > through headers. It will be much more easier to use, instead of having to > deal with egit pojos -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16046) camel-ahc-ws client serving as both a producer and consumer
Josh West created CAMEL-16046:
-
Summary: camel-ahc-ws client serving as both a producer and
consumer
Key: CAMEL-16046
URL: https://issues.apache.org/jira/browse/CAMEL-16046
Project: Camel
Issue Type: Improvement
Components: camel-ahc-ws
Affects Versions: 2.23.4
Environment: N/A
Reporter: Josh West
Fix For: Future
While subscribing to a websocket using camel-ahc-ws the connection and session
is sometimes bidirectional. A session may be initiated to subscribe to
specific data points by sending a message over the same session as the producer
(incoming) exchange.
from("ahc-wss://ws-feed.example.com").routeId("incoming")
.log("received message: ${body}");
from("timer:wssfeedInitaitor?delay=10=1").routeId("feed-initiator")
.setBody().constant(WSS_SUBSCRIBE)
.to("ahc-wss://ws-feed.example.com")
.log("received message on initiator: ${body}");
The current behavior is that the "incoming" route connects but doesn't receive
any data.
The "feed-initiator" router successfully sends the subscribe message to the
remote endpoint and starts receiving data. The websocket data received is only
showing up in DEBUG logging messages "[cHttpClient-3-1]
o.a.camel.component.ahc.ws.WsEndpoint : Received message --> ..." without the
data on the exchange.
Is there a way to share the same session?
Otherwise can the component be enhanced to serve as both a producer and
consumer at the same time?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16045) rest-dsl - xml or json binding should create new instance of data formats
Claus Ibsen created CAMEL-16045: --- Summary: rest-dsl - xml or json binding should create new instance of data formats Key: CAMEL-16045 URL: https://issues.apache.org/jira/browse/CAMEL-16045 Project: Camel Issue Type: Bug Components: camel-core, rest Affects Versions: 3.7.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.7.1, 3.8.0 Related to CAMEL-16032. When you use json or xml binding out of the box they should use their own private impl of data format as they have custom config that should not affect other rest-dsl. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15998) Camel-Github: Better structure for consumer returned object
[ https://issues.apache.org/jira/browse/CAMEL-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266083#comment-17266083 ] Babak Vahdat commented on CAMEL-15998: -- Hi I think we override one set header value with another one: [https://github.com/apache/camel/blob/bd790e5afb5bd3d4fbe294138d4b0be111717847/components/camel-github/src/main/java/org/apache/camel/component/github/consumer/CommitConsumer.java#L75-L76] Maybe it needs another header name for that? And IMHO the downside of these changes is that as the github and / or git APIs evolve through time with more properties in those exposed POJOs of them then we continuously need to add them to the corresponding new headers as the time passes by. This however would not be necessary in case of the original implementation. > Camel-Github: Better structure for consumer returned object > --- > > Key: CAMEL-15998 > URL: https://issues.apache.org/jira/browse/CAMEL-15998 > Project: Camel > Issue Type: Improvement > Components: camel-git >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.8.0 > > > We can specify something more through headers. The problem is similar to > camel-git, we need to have a plain type as body and enrich the information > through headers. It will be much more easier to use, instead of having to > deal with egit pojos -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (CAMEL-16032) [camel-main] autoconfiguration does not bind dataformat in the registry
[ https://issues.apache.org/jira/browse/CAMEL-16032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reopened CAMEL-16032: - > [camel-main] autoconfiguration does not bind dataformat in the registry > > > Key: CAMEL-16032 > URL: https://issues.apache.org/jira/browse/CAMEL-16032 > Project: Camel > Issue Type: Bug > Components: camel-main >Affects Versions: 3.7.0 >Reporter: Luigi De Masi >Assignee: Luigi De Masi >Priority: Major > Fix For: 3.7.1, 3.8.0 > > Attachments: 816.zip > > > Configuring a dataformat through properties does not work because after > setting the properties, the dataformat bean is not bound in the registry and > when the route starts, the dataformat is recreated: > [https://pastebin.com/raw/Tf05i7FK] > Attached a reproducer [^816.zip] with FHIR dataformat, but it's the same for > every dataformat; -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16032) [camel-main] autoconfiguration does not bind dataformat in the registry
[ https://issues.apache.org/jira/browse/CAMEL-16032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16032. - Resolution: Fixed > [camel-main] autoconfiguration does not bind dataformat in the registry > > > Key: CAMEL-16032 > URL: https://issues.apache.org/jira/browse/CAMEL-16032 > Project: Camel > Issue Type: Bug > Components: camel-main >Affects Versions: 3.7.0 >Reporter: Luigi De Masi >Assignee: Luigi De Masi >Priority: Major > Fix For: 3.7.1, 3.8.0 > > Attachments: 816.zip > > > Configuring a dataformat through properties does not work because after > setting the properties, the dataformat bean is not bound in the registry and > when the route starts, the dataformat is recreated: > [https://pastebin.com/raw/Tf05i7FK] > Attached a reproducer [^816.zip] with FHIR dataformat, but it's the same for > every dataformat; -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16019) Create another Camel Paho component for MQTT 5 support
[ https://issues.apache.org/jira/browse/CAMEL-16019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266012#comment-17266012 ] Claus Ibsen commented on CAMEL-16019: - karaf feature added but disabled due to bug in paho, reported at: https://github.com/eclipse/paho.mqtt.java/issues/857 > Create another Camel Paho component for MQTT 5 support > -- > > Key: CAMEL-16019 > URL: https://issues.apache.org/jira/browse/CAMEL-16019 > Project: Camel > Issue Type: New Feature > Components: camel-paho >Affects Versions: 3.7.0 >Reporter: Tadayoshi Sato >Assignee: Tadayoshi Sato >Priority: Major > Fix For: 3.8.0 > > > Current camel-paho uses MQTT v3 client library. We need a camel-paho version > that uses [MQTT v5 client > library|https://github.com/eclipse/paho.mqtt.java/tree/v1.2.5/org.eclipse.paho.mqttv5.client] > so that we can use MQTT 5 with Camel. > About the component name: which one do we prefer? > - camel-paho5 > - camel-paho-mqtt5 > - anything else -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16044) camel-mutiny - Add integration to smallreye mutiny
Claus Ibsen created CAMEL-16044: --- Summary: camel-mutiny - Add integration to smallreye mutiny Key: CAMEL-16044 URL: https://issues.apache.org/jira/browse/CAMEL-16044 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Fix For: 3.x https://github.com/smallrye/smallrye-mutiny https://smallrye.io/smallrye-mutiny/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-16019) Create another Camel Paho component for MQTT 5 support
[ https://issues.apache.org/jira/browse/CAMEL-16019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265939#comment-17265939 ] Claus Ibsen edited comment on CAMEL-16019 at 1/15/21, 12:16 PM: We then need spring boot starter *DONE* and quarkus extension for this was (Author: davsclaus): We then need spring boot starter and quarkus extension for this > Create another Camel Paho component for MQTT 5 support > -- > > Key: CAMEL-16019 > URL: https://issues.apache.org/jira/browse/CAMEL-16019 > Project: Camel > Issue Type: New Feature > Components: camel-paho >Affects Versions: 3.7.0 >Reporter: Tadayoshi Sato >Assignee: Tadayoshi Sato >Priority: Major > Fix For: 3.8.0 > > > Current camel-paho uses MQTT v3 client library. We need a camel-paho version > that uses [MQTT v5 client > library|https://github.com/eclipse/paho.mqtt.java/tree/v1.2.5/org.eclipse.paho.mqttv5.client] > so that we can use MQTT 5 with Camel. > About the component name: which one do we prefer? > - camel-paho5 > - camel-paho-mqtt5 > - anything else -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16019) Create another Camel Paho component for MQTT 5 support
[ https://issues.apache.org/jira/browse/CAMEL-16019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16019: Fix Version/s: 3.8.0 > Create another Camel Paho component for MQTT 5 support > -- > > Key: CAMEL-16019 > URL: https://issues.apache.org/jira/browse/CAMEL-16019 > Project: Camel > Issue Type: New Feature > Components: camel-paho >Affects Versions: 3.7.0 >Reporter: Tadayoshi Sato >Assignee: Tadayoshi Sato >Priority: Major > Fix For: 3.8.0 > > > Current camel-paho uses MQTT v3 client library. We need a camel-paho version > that uses [MQTT v5 client > library|https://github.com/eclipse/paho.mqtt.java/tree/v1.2.5/org.eclipse.paho.mqttv5.client] > so that we can use MQTT 5 with Camel. > About the component name: which one do we prefer? > - camel-paho5 > - camel-paho-mqtt5 > - anything else -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16019) Create another Camel Paho component for MQTT 5 support
[ https://issues.apache.org/jira/browse/CAMEL-16019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265939#comment-17265939 ] Claus Ibsen commented on CAMEL-16019: - We then need spring boot starter and quarkus extension for this > Create another Camel Paho component for MQTT 5 support > -- > > Key: CAMEL-16019 > URL: https://issues.apache.org/jira/browse/CAMEL-16019 > Project: Camel > Issue Type: New Feature > Components: camel-paho >Affects Versions: 3.7.0 >Reporter: Tadayoshi Sato >Assignee: Tadayoshi Sato >Priority: Major > Fix For: 3.8.0 > > > Current camel-paho uses MQTT v3 client library. We need a camel-paho version > that uses [MQTT v5 client > library|https://github.com/eclipse/paho.mqtt.java/tree/v1.2.5/org.eclipse.paho.mqttv5.client] > so that we can use MQTT 5 with Camel. > About the component name: which one do we prefer? > - camel-paho5 > - camel-paho-mqtt5 > - anything else -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16011) Remove camel-example- prefix in folder names in camel-spring-boot-examples
[ https://issues.apache.org/jira/browse/CAMEL-16011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265937#comment-17265937 ] Claus Ibsen commented on CAMEL-16011: - Thanks the hystrix example has been fixed > Remove camel-example- prefix in folder names in camel-spring-boot-examples > -- > > Key: CAMEL-16011 > URL: https://issues.apache.org/jira/browse/CAMEL-16011 > Project: Camel > Issue Type: Sub-task > Components: examples >Reporter: Matthias Streidel >Priority: Major > Attachments: apache camel swagger simple springbootrun.txt, camel > spring boot hystrix stacktrace.txt > > > edit folder names in > [camel-spring-boot-examples|https://github.com/apache/camel-spring-boot-examples] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16011) Remove camel-example- prefix in folder names in camel-spring-boot-examples
[ https://issues.apache.org/jira/browse/CAMEL-16011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265933#comment-17265933 ] Claus Ibsen commented on CAMEL-16011: - The swagger example requires to download the spec online - it works for me. Wonder if they had a glitch or that you are behind some HTTP proxy and it returned some error. > Remove camel-example- prefix in folder names in camel-spring-boot-examples > -- > > Key: CAMEL-16011 > URL: https://issues.apache.org/jira/browse/CAMEL-16011 > Project: Camel > Issue Type: Sub-task > Components: examples >Reporter: Matthias Streidel >Priority: Major > Attachments: apache camel swagger simple springbootrun.txt, camel > spring boot hystrix stacktrace.txt > > > edit folder names in > [camel-spring-boot-examples|https://github.com/apache/camel-spring-boot-examples] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16042) Upgrade to Spring Boot 2.4.2
[ https://issues.apache.org/jira/browse/CAMEL-16042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16042. - Assignee: Claus Ibsen Resolution: Fixed > Upgrade to Spring Boot 2.4.2 > > > Key: CAMEL-16042 > URL: https://issues.apache.org/jira/browse/CAMEL-16042 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.7.1, 3.8.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16022) Add message ordering to Google Pubsub
[ https://issues.apache.org/jira/browse/CAMEL-16022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-16022. - Fix Version/s: (was: 3.x) 3.8.0 Resolution: Fixed > Add message ordering to Google Pubsub > -- > > Key: CAMEL-16022 > URL: https://issues.apache.org/jira/browse/CAMEL-16022 > Project: Camel > Issue Type: Improvement > Components: camel-google-pubsub >Affects Versions: 3.7.0 >Reporter: Preben Asmussen >Priority: Minor > Fix For: 3.8.0 > > > Message ordering is currently not supported on the producer side. > [https://github.com/apache/camel/blob/master/components/camel-google-pubsub/src/main/java/org/apache/camel/component/google/pubsub/GooglePubsubProducer.java#L98] > To support message ordering the PubsubMessage produced has to contain a > orderingKey according to eg. > [https://cloud.google.com/pubsub/lite/docs/samples/pubsublite-publish-ordering-key] > It might be that this feature has been added after the component was released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16029) camel-core - Log on startup if multiple instances of same component are in use
[
https://issues.apache.org/jira/browse/CAMEL-16029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-16029.
-
Resolution: Fixed
> camel-core - Log on startup if multiple instances of same component are in use
> --
>
> Key: CAMEL-16029
> URL: https://issues.apache.org/jira/browse/CAMEL-16029
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.8.0
>
>
> Mostly you would use the default component instances. But for messaging
> components like JMS you may have one for ActiveMQ and another for WMQ etc and
> therefore multiple instances in the same Camel.
> However with SB you can mistakenly configure a new JMS component such as
> @Bean
> JmsComponent jmsComponent() {
> ...
> }
> And think that "jms" will use it. But it uses the bean id, which is method
> name by default in SB, so you have 2 JMS components.
> Having a LOG at startup to help show this would better spot this problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16040) JAXB error Generating Swagger in Karaf
[
https://issues.apache.org/jira/browse/CAMEL-16040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-16040.
-
Resolution: Fixed
> JAXB error Generating Swagger in Karaf
> --
>
> Key: CAMEL-16040
> URL: https://issues.apache.org/jira/browse/CAMEL-16040
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger-java
>Affects Versions: 3.7.0
> Environment: Karaf 4.2.10
> Windows
> Camel Rest Dsl (Java)
>Reporter: Bob Paulin
>Priority: Minor
> Fix For: 3.7.1, 3.8.0
>
>
> When generating a Swagger for the Rest Java DSL in Karaf with the
> camel-core-osgi bundle I'm receiving the following exception[1]
> It appears this is happening because the core/camel-xml-jaxb bundle does not
> import all the packages defined in the
> org.apache.camel.model.Constants.JAXB_CONTEXT_PACKAGES so it is unable to see
> the jaxb.index.
>
> I was able to get it to work by manually adding the packages to the
> camel.osgi.import property in the pom since the packages are not used
> anywhere else in the camel-xml-jaxb. Doesn't seem like a great solution
> since it requires the pom to match the packages defined in
> Constants.JAXB_CONTEXT_PACKAGES. Open to other suggestions.
>
> [1]
>
> {code:java}
> 2021-01-14T16:35:37,850 | WARN | Camel (camel-2) thread #17 -
> NettyConsumerExecutorGroup | RestSwaggerProcessor | 164 -
> org.apache.camel.camel-swagger-java - 3.7.0 | | Error rendering Swagger API
> due "org.apache.camel.model.cloud" doesnt contain ObjectFactory.class or
> jaxb.index
> javax.xml.bind.JAXBException: "org.apache.camel.model.cloud" doesnt contain
> ObjectFactory.class or jaxb.index
> at
> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:260)
> ~[jaxb-runtime-2.3.3.jar:2.3.3]
> at
> com.sun.xml.bind.v2.JAXBContextFactory.createContext(JAXBContextFactory.java:48)
> ~[jaxb-runtime-2.3.3.jar:2.3.3]
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:302) ~[?:?]
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:478) ~[?:?]
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:435) ~[?:?]
> at
> org.apache.camel.xml.jaxb.DefaultModelJAXBContextFactory.newJAXBContext(DefaultModelJAXBContextFactory.java:39)
> ~[?:?]
> at
> org.apache.camel.xml.jaxb.DefaultModelJAXBContextFactory.newJAXBContext(DefaultModelJAXBContextFactory.java:29)
> ~[?:?]
> at
> org.apache.camel.xml.jaxb.JaxbModelToXMLDumper.getJAXBContext(JaxbModelToXMLDumper.java:195)
> ~[?:?]
> at
> org.apache.camel.xml.jaxb.JaxbModelToXMLDumper.dumpModelAsXml(JaxbModelToXMLDumper.java:69)
> ~[?:?]
> at
> org.apache.camel.swagger.RestSwaggerSupport.getRestDefinitions(RestSwaggerSupport.java:152)
> ~[!/:3.7.0]
> at
> org.apache.camel.swagger.RestSwaggerSupport.renderResourceListing(RestSwaggerSupport.java:232)
> ~[!/:3.7.0]
> at
> org.apache.camel.swagger.RestSwaggerProcessor.process(RestSwaggerProcessor.java:120)
> [!/:3.7.0]
> at
> org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:66)
> [!/:3.7.0]
> at
> org.apache.camel.component.rest.RestApiProducer.process(RestApiProducer.java:39)
> [!/:3.7.0]
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:169)
> [!/:3.7.0]
> at
> org.apache.camel.support.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:94)
> [!/:3.7.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:714)
> [!/:3.7.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:623)
> [!/:3.7.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:148)
> [!/:3.7.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:60)
> [!/:3.7.0]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:147)
> [!/:3.7.0]
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:312)
> [!/:3.7.0]
> at
> org.apache.camel.component.netty.handlers.ServerChannelHandler.processAsynchronously(ServerChannelHandler.java:142)
> [!/:3.7.0]
> at
> org.apache.camel.component.netty.handlers.ServerChannelHandler.channelRead0(ServerChannelHandler.java:113)
> [!/:3.7.0]
> at
> org.apache.camel.component.netty.http.handlers.HttpServerChannelHandler.channelRead0(HttpServerChannelHandler.java:221)
> [!/:3.7.0]
> at
>
[jira] [Updated] (CAMEL-16040) JAXB error Generating Swagger in Karaf
[
https://issues.apache.org/jira/browse/CAMEL-16040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-16040:
Fix Version/s: 3.8.0
3.7.1
> JAXB error Generating Swagger in Karaf
> --
>
> Key: CAMEL-16040
> URL: https://issues.apache.org/jira/browse/CAMEL-16040
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger-java
>Affects Versions: 3.7.0
> Environment: Karaf 4.2.10
> Windows
> Camel Rest Dsl (Java)
>Reporter: Bob Paulin
>Priority: Minor
> Fix For: 3.7.1, 3.8.0
>
>
> When generating a Swagger for the Rest Java DSL in Karaf with the
> camel-core-osgi bundle I'm receiving the following exception[1]
> It appears this is happening because the core/camel-xml-jaxb bundle does not
> import all the packages defined in the
> org.apache.camel.model.Constants.JAXB_CONTEXT_PACKAGES so it is unable to see
> the jaxb.index.
>
> I was able to get it to work by manually adding the packages to the
> camel.osgi.import property in the pom since the packages are not used
> anywhere else in the camel-xml-jaxb. Doesn't seem like a great solution
> since it requires the pom to match the packages defined in
> Constants.JAXB_CONTEXT_PACKAGES. Open to other suggestions.
>
> [1]
>
> {code:java}
> 2021-01-14T16:35:37,850 | WARN | Camel (camel-2) thread #17 -
> NettyConsumerExecutorGroup | RestSwaggerProcessor | 164 -
> org.apache.camel.camel-swagger-java - 3.7.0 | | Error rendering Swagger API
> due "org.apache.camel.model.cloud" doesnt contain ObjectFactory.class or
> jaxb.index
> javax.xml.bind.JAXBException: "org.apache.camel.model.cloud" doesnt contain
> ObjectFactory.class or jaxb.index
> at
> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:260)
> ~[jaxb-runtime-2.3.3.jar:2.3.3]
> at
> com.sun.xml.bind.v2.JAXBContextFactory.createContext(JAXBContextFactory.java:48)
> ~[jaxb-runtime-2.3.3.jar:2.3.3]
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:302) ~[?:?]
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:478) ~[?:?]
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:435) ~[?:?]
> at
> org.apache.camel.xml.jaxb.DefaultModelJAXBContextFactory.newJAXBContext(DefaultModelJAXBContextFactory.java:39)
> ~[?:?]
> at
> org.apache.camel.xml.jaxb.DefaultModelJAXBContextFactory.newJAXBContext(DefaultModelJAXBContextFactory.java:29)
> ~[?:?]
> at
> org.apache.camel.xml.jaxb.JaxbModelToXMLDumper.getJAXBContext(JaxbModelToXMLDumper.java:195)
> ~[?:?]
> at
> org.apache.camel.xml.jaxb.JaxbModelToXMLDumper.dumpModelAsXml(JaxbModelToXMLDumper.java:69)
> ~[?:?]
> at
> org.apache.camel.swagger.RestSwaggerSupport.getRestDefinitions(RestSwaggerSupport.java:152)
> ~[!/:3.7.0]
> at
> org.apache.camel.swagger.RestSwaggerSupport.renderResourceListing(RestSwaggerSupport.java:232)
> ~[!/:3.7.0]
> at
> org.apache.camel.swagger.RestSwaggerProcessor.process(RestSwaggerProcessor.java:120)
> [!/:3.7.0]
> at
> org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:66)
> [!/:3.7.0]
> at
> org.apache.camel.component.rest.RestApiProducer.process(RestApiProducer.java:39)
> [!/:3.7.0]
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:169)
> [!/:3.7.0]
> at
> org.apache.camel.support.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:94)
> [!/:3.7.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:714)
> [!/:3.7.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:623)
> [!/:3.7.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:148)
> [!/:3.7.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:60)
> [!/:3.7.0]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:147)
> [!/:3.7.0]
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:312)
> [!/:3.7.0]
> at
> org.apache.camel.component.netty.handlers.ServerChannelHandler.processAsynchronously(ServerChannelHandler.java:142)
> [!/:3.7.0]
> at
> org.apache.camel.component.netty.handlers.ServerChannelHandler.channelRead0(ServerChannelHandler.java:113)
> [!/:3.7.0]
> at
> org.apache.camel.component.netty.http.handlers.HttpServerChannelHandler.channelRead0(HttpServerChannelHandler.java:221)
> [!/:3.7.0]
> at
>
[jira] [Closed] (CAMEL-16043) [camel-kafka] additionalProperties option on endpoint level is broken
[ https://issues.apache.org/jira/browse/CAMEL-16043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omar Al-Safi closed CAMEL-16043. Resolution: Fixed > [camel-kafka] additionalProperties option on endpoint level is broken > - > > Key: CAMEL-16043 > URL: https://issues.apache.org/jira/browse/CAMEL-16043 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 3.7.0 >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Major > Fix For: 3.7.1, 3.8.0 > > > Currently the additionalProperties option on endpoint is broken, it works > however on the component level -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16043) [camel-kafka] additionalProperties option on endpoint level is broken
Omar Al-Safi created CAMEL-16043: Summary: [camel-kafka] additionalProperties option on endpoint level is broken Key: CAMEL-16043 URL: https://issues.apache.org/jira/browse/CAMEL-16043 Project: Camel Issue Type: Bug Components: camel-kafka Affects Versions: 3.7.0 Reporter: Omar Al-Safi Assignee: Omar Al-Safi Fix For: 3.7.1, 3.8.0 Currently the additionalProperties option on endpoint is broken, it works however on the component level -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16041) The managed dependency version through Camel Spring Boot BOM for com.google.guava:guava is from 2015
[
https://issues.apache.org/jira/browse/CAMEL-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265800#comment-17265800
]
Babak Vahdat commented on CAMEL-16041:
--
{quote}
Yeah try with 3.7.1 as there was a problem with the parent pom.xml being pulled
in
{quote}
Thanks will try as soon as it's out and would close this ticket accordingly.
> The managed dependency version through Camel Spring Boot BOM for
> com.google.guava:guava is from 2015
>
>
> Key: CAMEL-16041
> URL: https://issues.apache.org/jira/browse/CAMEL-16041
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.7.0
>Reporter: Babak Vahdat
>Priority: Minor
>
> Consider the following sample application POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
> com.foo
> bar
> 0.1.0-SNAPSHOT
>
>
>
>
> org.apache.camel.springboot
> camel-spring-boot-bom
> 3.7.0
> pom
> import
>
>
>
>
>
> com.google.guava
> guava
>
>
>
> {code}
> Then you would inherit the managed dependency version
> [19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
> released in {{2015}}:
> {code:java|title=Bar.java|borderStyle=solid}
> $> mvn dependency:tree
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < com.foo:bar
> >-
> [INFO] Building bar 0.1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
> [INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
> [INFO] \- com.google.guava:guava:jar:19.0:compile
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.190 s
> [INFO] Finished at: 2021-01-15T08:19:47+01:00
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16041) The managed dependency version through Camel Spring Boot BOM for com.google.guava:guava is from 2015
[
https://issues.apache.org/jira/browse/CAMEL-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265792#comment-17265792
]
Babak Vahdat commented on CAMEL-16041:
--
For sure as a workaround one can always use his own version to override that
old inherited managed dependency from Camel:
{code:xml}
com.google.guava
guava
${my.guava.version}
{code}
Please also note that exclusion of managed dependencies [is currently not
possible in Maven|https://github.com/apache/maven/pull/295].
And the real pain is the fact that the Maven managed dependencies have higher
precedence over the transitive ones! In our case this old version from Camel
overrided the version Wiremock [currently
uses|https://github.com/tomakehurst/wiremock/blob/28c5e6737caa7887e2070033bd361501e12ea3ee/build.gradle#L39].
And you would not even think of such a scenario until your tests start to
fail. :-(
> The managed dependency version through Camel Spring Boot BOM for
> com.google.guava:guava is from 2015
>
>
> Key: CAMEL-16041
> URL: https://issues.apache.org/jira/browse/CAMEL-16041
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.7.0
>Reporter: Babak Vahdat
>Priority: Minor
>
> Consider the following sample application POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
> com.foo
> bar
> 0.1.0-SNAPSHOT
>
>
>
>
> org.apache.camel.springboot
> camel-spring-boot-bom
> 3.7.0
> pom
> import
>
>
>
>
>
> com.google.guava
> guava
>
>
>
> {code}
> Then you would inherit the managed dependency version
> [19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
> released in {{2015}}:
> {code:java|title=Bar.java|borderStyle=solid}
> $> mvn dependency:tree
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < com.foo:bar
> >-
> [INFO] Building bar 0.1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
> [INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
> [INFO] \- com.google.guava:guava:jar:19.0:compile
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.190 s
> [INFO] Finished at: 2021-01-15T08:19:47+01:00
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
