[jira] [Created] (CAMEL-20488) camel-openapi-java - Drop support for openapi v2
Claus Ibsen created CAMEL-20488: --- Summary: camel-openapi-java - Drop support for openapi v2 Key: CAMEL-20488 URL: https://issues.apache.org/jira/browse/CAMEL-20488 Project: Camel Issue Type: Improvement Components: camel-openapi-java Reporter: Claus Ibsen Fix For: 4.5.0 We use v3 swagger and parser today. And there is some special code to use a v3-to-v2 converter from swagger, but this uses some old swagger-core + models that are NOT jakarta EE compatible, which causes mixed JARs and classpath hell. See for example CAMEL-20487 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20487) REST API generator issue with typeOut
[
https://issues.apache.org/jira/browse/CAMEL-20487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821861#comment-17821861
]
Claus Ibsen edited comment on CAMEL-20487 at 2/28/24 8:16 PM:
--
Okay so this jakarta vs javax is a cluster fuck. You would need to add many
maven to remove the swagger-core that are not jakarta from all kind
of places.
The swagger team have not released a swagger-parser that uses jakarta so it
bring in those other JARs, and you also need to drop openapi v2 support as
those uses the old JARs also.
After this then camel-jbang can work. It was also due to camel-jbang comes with
openapi-generator as a command that adds a bunch of JARs that gets mixed up as
well.
was (Author: davsclaus):
Okay so this jakarta vs javax is a cluster fuck. You would need to add many
maven to remove the swagger-core that are not jakarta from all kind
of places.
The swagger team have not released a swagger-parser that uses jakarta so it
bring in those other JARs, and you also need to drop openapi v2 support as
those uses the old JARs also.
> REST API generator issue with typeOut
> -
>
> Key: CAMEL-20487
> URL: https://issues.apache.org/jira/browse/CAMEL-20487
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 4.4.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.1, 4.5.0
>
>
> If REST method typeOut defined then /api-doc throws exception.
> How to reproduce:
> 1. rest.camel.yaml
> {code:java}
> - restConfiguration:
> component: platform-http
> apiContextPath: /api-doc
> bindingMode: json
> - rest:
> id: rest-b339
> get:
> - id: get-c5d3
> path: /account
> to: direct:get-account
> outType: karavan.simple.Account
> bindingMode: json
> - route:
> id: route-4956
> nodePrefixId: route-7d3
> from:
> id: from-cad7
> uri: direct
> parameters:
> name: get-account
> steps:
> - setBody:
> id: setBody-0623
> expression:
> groovy:
> id: groovy-782e
> expression: |-
> def acc = new karavan.simple.Account()
> acc.setAccountNumber('12345')
> acc.setAccountName('test')
> return acc
> - log:
> id: log-bd34
> message: ${body}
> {code}
> 2. Java Class
> {code:java}
> public class Account {
> // Private fields for encapsulation
> private String accountNumber;
> private String accountName;
> private double balance;
> public Account() {
> }
> public String getAccountNumber() {
> return accountNumber;
> }
> public void setAccountNumber(String accountNumber) {
> this.accountNumber = accountNumber;
> }
> public String getAccountName() {
> return accountName;
> }
> public void setAccountName(String accountName) {
> this.accountName = accountName;
> }
> public double getBalance() {
> return balance;
> }
> public void setBalance(double balance) {
> this.balance = balance;
> }
> }
> {code}
> 3. Run
> {code:java}
> jbang "-Dcamel.jbang.version=4.4.0" camel@apache/camel run *
> --gav=karavan:simple:1
> {code}
> 4. Call /api-doc
> {code:java}
> curl --location 'localhost:8080/api-doc'
> {code}
> 5. Get exception:
> {code:java}
> 2024-02-27 12:46:29.336 WARN 52151 --- [worker-thread-0]
> agger.v3.core.jackson.ModelResolver : jackson
> BeanDescription.findJsonValueAccessor not found, this could lead to
> inaccurate result, please update jackson to 2.9+
> 2024-02-27 12:46:29.337 WARN 52151 --- [ntloop-thread-0]
> ttp.vertx.VertxPlatformHttpConsumer : Failed handling platform-http endpoint
> /api-doc. Caused by: [java.lang.NoClassDefFoundError -
> javax/xml/bind/annotation/XmlElement]
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlElement
> at
> io.swagger.v3.core.jackson.SwaggerAnnotationIntrospector.hasRequiredMarker(SwaggerAnnotationIntrospector.java:29)
> ~[swagger-core-2.2.19.jar:2.2.19]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20487) REST API generator issue with typeOut
[
https://issues.apache.org/jira/browse/CAMEL-20487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821861#comment-17821861
]
Claus Ibsen commented on CAMEL-20487:
-
Okay so this jakarta vs javax is a cluster fuck. You would need to add many
maven to remove the swagger-core that are not jakarta from all kind
of places.
The swagger team have not released a swagger-parser that uses jakarta so it
bring in those other JARs, and you also need to drop openapi v2 support as
those uses the old JARs also.
> REST API generator issue with typeOut
> -
>
> Key: CAMEL-20487
> URL: https://issues.apache.org/jira/browse/CAMEL-20487
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 4.4.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.1, 4.5.0
>
>
> If REST method typeOut defined then /api-doc throws exception.
> How to reproduce:
> 1. rest.camel.yaml
> {code:java}
> - restConfiguration:
> component: platform-http
> apiContextPath: /api-doc
> bindingMode: json
> - rest:
> id: rest-b339
> get:
> - id: get-c5d3
> path: /account
> to: direct:get-account
> outType: karavan.simple.Account
> bindingMode: json
> - route:
> id: route-4956
> nodePrefixId: route-7d3
> from:
> id: from-cad7
> uri: direct
> parameters:
> name: get-account
> steps:
> - setBody:
> id: setBody-0623
> expression:
> groovy:
> id: groovy-782e
> expression: |-
> def acc = new karavan.simple.Account()
> acc.setAccountNumber('12345')
> acc.setAccountName('test')
> return acc
> - log:
> id: log-bd34
> message: ${body}
> {code}
> 2. Java Class
> {code:java}
> public class Account {
> // Private fields for encapsulation
> private String accountNumber;
> private String accountName;
> private double balance;
> public Account() {
> }
> public String getAccountNumber() {
> return accountNumber;
> }
> public void setAccountNumber(String accountNumber) {
> this.accountNumber = accountNumber;
> }
> public String getAccountName() {
> return accountName;
> }
> public void setAccountName(String accountName) {
> this.accountName = accountName;
> }
> public double getBalance() {
> return balance;
> }
> public void setBalance(double balance) {
> this.balance = balance;
> }
> }
> {code}
> 3. Run
> {code:java}
> jbang "-Dcamel.jbang.version=4.4.0" camel@apache/camel run *
> --gav=karavan:simple:1
> {code}
> 4. Call /api-doc
> {code:java}
> curl --location 'localhost:8080/api-doc'
> {code}
> 5. Get exception:
> {code:java}
> 2024-02-27 12:46:29.336 WARN 52151 --- [worker-thread-0]
> agger.v3.core.jackson.ModelResolver : jackson
> BeanDescription.findJsonValueAccessor not found, this could lead to
> inaccurate result, please update jackson to 2.9+
> 2024-02-27 12:46:29.337 WARN 52151 --- [ntloop-thread-0]
> ttp.vertx.VertxPlatformHttpConsumer : Failed handling platform-http endpoint
> /api-doc. Caused by: [java.lang.NoClassDefFoundError -
> javax/xml/bind/annotation/XmlElement]
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlElement
> at
> io.swagger.v3.core.jackson.SwaggerAnnotationIntrospector.hasRequiredMarker(SwaggerAnnotationIntrospector.java:29)
> ~[swagger-core-2.2.19.jar:2.2.19]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20487) REST API generator issue with typeOut
[
https://issues.apache.org/jira/browse/CAMEL-20487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821849#comment-17821849
]
Claus Ibsen commented on CAMEL-20487:
-
Okay as a fat-jar then I can get the api-doc
{code}
~/workspace ❯ curl http://0.0.0.0:8080/api-doc
{
"openapi" : "3.0.1",
"info" : { },
"servers" : [ {
"url" : ""
} ],
"paths" : {
"/account" : {
"get" : {
"operationId" : "get-c5d3",
"responses" : {
"200" : {
"description" : "Output type",
"content" : {
"application/json" : {
"schema" : {
"$ref" : "#/components/schemas/Account"
}
}
}
}
}
}
}
},
"components" : {
"schemas" : {
"Account" : {
"type" : "object",
"properties" : {
"accountNumber" : {
"type" : "string"
},
"accountName" : {
"type" : "string"
},
"balance" : {
"type" : "number",
"format" : "double"
}
}
}
}
}
}%
{code}
I also had to remove some cruft from camel-openapi-java as it has openapi v2
support but that is problematic as they bring in old JARs that are not
JakartaEE compatible and you have classpath hell.
> REST API generator issue with typeOut
> -
>
> Key: CAMEL-20487
> URL: https://issues.apache.org/jira/browse/CAMEL-20487
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 4.4.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.1, 4.5.0
>
>
> If REST method typeOut defined then /api-doc throws exception.
> How to reproduce:
> 1. rest.camel.yaml
> {code:java}
> - restConfiguration:
> component: platform-http
> apiContextPath: /api-doc
> bindingMode: json
> - rest:
> id: rest-b339
> get:
> - id: get-c5d3
> path: /account
> to: direct:get-account
> outType: karavan.simple.Account
> bindingMode: json
> - route:
> id: route-4956
> nodePrefixId: route-7d3
> from:
> id: from-cad7
> uri: direct
> parameters:
> name: get-account
> steps:
> - setBody:
> id: setBody-0623
> expression:
> groovy:
> id: groovy-782e
> expression: |-
> def acc = new karavan.simple.Account()
> acc.setAccountNumber('12345')
> acc.setAccountName('test')
> return acc
> - log:
> id: log-bd34
> message: ${body}
> {code}
> 2. Java Class
> {code:java}
> public class Account {
> // Private fields for encapsulation
> private String accountNumber;
> private String accountName;
> private double balance;
> public Account() {
> }
> public String getAccountNumber() {
> return accountNumber;
> }
> public void setAccountNumber(String accountNumber) {
> this.accountNumber = accountNumber;
> }
> public String getAccountName() {
> return accountName;
> }
> public void setAccountName(String accountName) {
> this.accountName = accountName;
> }
> public double getBalance() {
> return balance;
> }
> public void setBalance(double balance) {
> this.balance = balance;
> }
> }
> {code}
> 3. Run
> {code:java}
> jbang "-Dcamel.jbang.version=4.4.0" camel@apache/camel run *
> --gav=karavan:simple:1
> {code}
> 4. Call /api-doc
> {code:java}
> curl --location 'localhost:8080/api-doc'
> {code}
> 5. Get exception:
> {code:java}
> 2024-02-27 12:46:29.336 WARN 52151 --- [worker-thread-0]
> agger.v3.core.jackson.ModelResolver : jackson
> BeanDescription.findJsonValueAccessor not found, this could lead to
> inaccurate result, please update jackson to 2.9+
> 2024-02-27 12:46:29.337 WARN 52151 --- [ntloop-thread-0]
> ttp.vertx.VertxPlatformHttpConsumer : Failed handling platform-http endpoint
> /api-doc. Caused by: [java.lang.NoClassDefFoundError -
> javax/xml/bind/annotation/XmlElement]
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlElement
> at
> io.swagger.v3.core.jackson.SwaggerAnnotationIntrospector.hasRequiredMarker(SwaggerAnnotationIntrospector.java:29)
> ~[swagger-core-2.2.19.jar:2.2.19]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20487) REST API generator issue with typeOut
[
https://issues.apache.org/jira/browse/CAMEL-20487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821828#comment-17821828
]
Claus Ibsen commented on CAMEL-20487:
-
This is a swagger problem. I created a ticket at them
https://github.com/swagger-api/swagger-core/issues/4622
> REST API generator issue with typeOut
> -
>
> Key: CAMEL-20487
> URL: https://issues.apache.org/jira/browse/CAMEL-20487
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 4.4.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.1, 4.5.0
>
>
> If REST method typeOut defined then /api-doc throws exception.
> How to reproduce:
> 1. rest.camel.yaml
> {code:java}
> - restConfiguration:
> component: platform-http
> apiContextPath: /api-doc
> bindingMode: json
> - rest:
> id: rest-b339
> get:
> - id: get-c5d3
> path: /account
> to: direct:get-account
> outType: karavan.simple.Account
> bindingMode: json
> - route:
> id: route-4956
> nodePrefixId: route-7d3
> from:
> id: from-cad7
> uri: direct
> parameters:
> name: get-account
> steps:
> - setBody:
> id: setBody-0623
> expression:
> groovy:
> id: groovy-782e
> expression: |-
> def acc = new karavan.simple.Account()
> acc.setAccountNumber('12345')
> acc.setAccountName('test')
> return acc
> - log:
> id: log-bd34
> message: ${body}
> {code}
> 2. Java Class
> {code:java}
> public class Account {
> // Private fields for encapsulation
> private String accountNumber;
> private String accountName;
> private double balance;
> public Account() {
> }
> public String getAccountNumber() {
> return accountNumber;
> }
> public void setAccountNumber(String accountNumber) {
> this.accountNumber = accountNumber;
> }
> public String getAccountName() {
> return accountName;
> }
> public void setAccountName(String accountName) {
> this.accountName = accountName;
> }
> public double getBalance() {
> return balance;
> }
> public void setBalance(double balance) {
> this.balance = balance;
> }
> }
> {code}
> 3. Run
> {code:java}
> jbang "-Dcamel.jbang.version=4.4.0" camel@apache/camel run *
> --gav=karavan:simple:1
> {code}
> 4. Call /api-doc
> {code:java}
> curl --location 'localhost:8080/api-doc'
> {code}
> 5. Get exception:
> {code:java}
> 2024-02-27 12:46:29.336 WARN 52151 --- [worker-thread-0]
> agger.v3.core.jackson.ModelResolver : jackson
> BeanDescription.findJsonValueAccessor not found, this could lead to
> inaccurate result, please update jackson to 2.9+
> 2024-02-27 12:46:29.337 WARN 52151 --- [ntloop-thread-0]
> ttp.vertx.VertxPlatformHttpConsumer : Failed handling platform-http endpoint
> /api-doc. Caused by: [java.lang.NoClassDefFoundError -
> javax/xml/bind/annotation/XmlElement]
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlElement
> at
> io.swagger.v3.core.jackson.SwaggerAnnotationIntrospector.hasRequiredMarker(SwaggerAnnotationIntrospector.java:29)
> ~[swagger-core-2.2.19.jar:2.2.19]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20487) REST API generator issue with typeOut
[
https://issues.apache.org/jira/browse/CAMEL-20487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20487:
---
Assignee: Claus Ibsen
> REST API generator issue with typeOut
> -
>
> Key: CAMEL-20487
> URL: https://issues.apache.org/jira/browse/CAMEL-20487
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 4.4.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.1, 4.5.0
>
>
> If REST method typeOut defined then /api-doc throws exception.
> How to reproduce:
> 1. rest.camel.yaml
> {code:java}
> - restConfiguration:
> component: platform-http
> apiContextPath: /api-doc
> bindingMode: json
> - rest:
> id: rest-b339
> get:
> - id: get-c5d3
> path: /account
> to: direct:get-account
> outType: karavan.simple.Account
> bindingMode: json
> - route:
> id: route-4956
> nodePrefixId: route-7d3
> from:
> id: from-cad7
> uri: direct
> parameters:
> name: get-account
> steps:
> - setBody:
> id: setBody-0623
> expression:
> groovy:
> id: groovy-782e
> expression: |-
> def acc = new karavan.simple.Account()
> acc.setAccountNumber('12345')
> acc.setAccountName('test')
> return acc
> - log:
> id: log-bd34
> message: ${body}
> {code}
> 2. Java Class
> {code:java}
> public class Account {
> // Private fields for encapsulation
> private String accountNumber;
> private String accountName;
> private double balance;
> public Account() {
> }
> public String getAccountNumber() {
> return accountNumber;
> }
> public void setAccountNumber(String accountNumber) {
> this.accountNumber = accountNumber;
> }
> public String getAccountName() {
> return accountName;
> }
> public void setAccountName(String accountName) {
> this.accountName = accountName;
> }
> public double getBalance() {
> return balance;
> }
> public void setBalance(double balance) {
> this.balance = balance;
> }
> }
> {code}
> 3. Run
> {code:java}
> jbang "-Dcamel.jbang.version=4.4.0" camel@apache/camel run *
> --gav=karavan:simple:1
> {code}
> 4. Call /api-doc
> {code:java}
> curl --location 'localhost:8080/api-doc'
> {code}
> 5. Get exception:
> {code:java}
> 2024-02-27 12:46:29.336 WARN 52151 --- [worker-thread-0]
> agger.v3.core.jackson.ModelResolver : jackson
> BeanDescription.findJsonValueAccessor not found, this could lead to
> inaccurate result, please update jackson to 2.9+
> 2024-02-27 12:46:29.337 WARN 52151 --- [ntloop-thread-0]
> ttp.vertx.VertxPlatformHttpConsumer : Failed handling platform-http endpoint
> /api-doc. Caused by: [java.lang.NoClassDefFoundError -
> javax/xml/bind/annotation/XmlElement]
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlElement
> at
> io.swagger.v3.core.jackson.SwaggerAnnotationIntrospector.hasRequiredMarker(SwaggerAnnotationIntrospector.java:29)
> ~[swagger-core-2.2.19.jar:2.2.19]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20487) REST API generator issue with typeOut
[
https://issues.apache.org/jira/browse/CAMEL-20487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821815#comment-17821815
]
Claus Ibsen commented on CAMEL-20487:
-
Hmm smell like some of the javax vs jakarta
> REST API generator issue with typeOut
> -
>
> Key: CAMEL-20487
> URL: https://issues.apache.org/jira/browse/CAMEL-20487
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 4.4.0
>Reporter: Marat Gubaidullin
>Priority: Minor
> Fix For: 4.4.1, 4.5.0
>
>
> If REST method typeOut defined then /api-doc throws exception.
> How to reproduce:
> 1. rest.camel.yaml
> {code:java}
> - restConfiguration:
> component: platform-http
> apiContextPath: /api-doc
> bindingMode: json
> - rest:
> id: rest-b339
> get:
> - id: get-c5d3
> path: /account
> to: direct:get-account
> outType: karavan.simple.Account
> bindingMode: json
> - route:
> id: route-4956
> nodePrefixId: route-7d3
> from:
> id: from-cad7
> uri: direct
> parameters:
> name: get-account
> steps:
> - setBody:
> id: setBody-0623
> expression:
> groovy:
> id: groovy-782e
> expression: |-
> def acc = new karavan.simple.Account()
> acc.setAccountNumber('12345')
> acc.setAccountName('test')
> return acc
> - log:
> id: log-bd34
> message: ${body}
> {code}
> 2. Java Class
> {code:java}
> public class Account {
> // Private fields for encapsulation
> private String accountNumber;
> private String accountName;
> private double balance;
> public Account() {
> }
> public String getAccountNumber() {
> return accountNumber;
> }
> public void setAccountNumber(String accountNumber) {
> this.accountNumber = accountNumber;
> }
> public String getAccountName() {
> return accountName;
> }
> public void setAccountName(String accountName) {
> this.accountName = accountName;
> }
> public double getBalance() {
> return balance;
> }
> public void setBalance(double balance) {
> this.balance = balance;
> }
> }
> {code}
> 3. Run
> {code:java}
> jbang "-Dcamel.jbang.version=4.4.0" camel@apache/camel run *
> --gav=karavan:simple:1
> {code}
> 4. Call /api-doc
> {code:java}
> curl --location 'localhost:8080/api-doc'
> {code}
> 5. Get exception:
> {code:java}
> 2024-02-27 12:46:29.336 WARN 52151 --- [worker-thread-0]
> agger.v3.core.jackson.ModelResolver : jackson
> BeanDescription.findJsonValueAccessor not found, this could lead to
> inaccurate result, please update jackson to 2.9+
> 2024-02-27 12:46:29.337 WARN 52151 --- [ntloop-thread-0]
> ttp.vertx.VertxPlatformHttpConsumer : Failed handling platform-http endpoint
> /api-doc. Caused by: [java.lang.NoClassDefFoundError -
> javax/xml/bind/annotation/XmlElement]
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlElement
> at
> io.swagger.v3.core.jackson.SwaggerAnnotationIntrospector.hasRequiredMarker(SwaggerAnnotationIntrospector.java:29)
> ~[swagger-core-2.2.19.jar:2.2.19]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20487) REST API generator issue with typeOut
[
https://issues.apache.org/jira/browse/CAMEL-20487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20487:
Fix Version/s: 4.4.1
4.5.0
> REST API generator issue with typeOut
> -
>
> Key: CAMEL-20487
> URL: https://issues.apache.org/jira/browse/CAMEL-20487
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 4.4.0
>Reporter: Marat Gubaidullin
>Priority: Minor
> Fix For: 4.4.1, 4.5.0
>
>
> If REST method typeOut defined then /api-doc throws exception.
> How to reproduce:
> 1. rest.camel.yaml
> {code:java}
> - restConfiguration:
> component: platform-http
> apiContextPath: /api-doc
> bindingMode: json
> - rest:
> id: rest-b339
> get:
> - id: get-c5d3
> path: /account
> to: direct:get-account
> outType: karavan.simple.Account
> bindingMode: json
> - route:
> id: route-4956
> nodePrefixId: route-7d3
> from:
> id: from-cad7
> uri: direct
> parameters:
> name: get-account
> steps:
> - setBody:
> id: setBody-0623
> expression:
> groovy:
> id: groovy-782e
> expression: |-
> def acc = new karavan.simple.Account()
> acc.setAccountNumber('12345')
> acc.setAccountName('test')
> return acc
> - log:
> id: log-bd34
> message: ${body}
> {code}
> 2. Java Class
> {code:java}
> public class Account {
> // Private fields for encapsulation
> private String accountNumber;
> private String accountName;
> private double balance;
> public Account() {
> }
> public String getAccountNumber() {
> return accountNumber;
> }
> public void setAccountNumber(String accountNumber) {
> this.accountNumber = accountNumber;
> }
> public String getAccountName() {
> return accountName;
> }
> public void setAccountName(String accountName) {
> this.accountName = accountName;
> }
> public double getBalance() {
> return balance;
> }
> public void setBalance(double balance) {
> this.balance = balance;
> }
> }
> {code}
> 3. Run
> {code:java}
> jbang "-Dcamel.jbang.version=4.4.0" camel@apache/camel run *
> --gav=karavan:simple:1
> {code}
> 4. Call /api-doc
> {code:java}
> curl --location 'localhost:8080/api-doc'
> {code}
> 5. Get exception:
> {code:java}
> 2024-02-27 12:46:29.336 WARN 52151 --- [worker-thread-0]
> agger.v3.core.jackson.ModelResolver : jackson
> BeanDescription.findJsonValueAccessor not found, this could lead to
> inaccurate result, please update jackson to 2.9+
> 2024-02-27 12:46:29.337 WARN 52151 --- [ntloop-thread-0]
> ttp.vertx.VertxPlatformHttpConsumer : Failed handling platform-http endpoint
> /api-doc. Caused by: [java.lang.NoClassDefFoundError -
> javax/xml/bind/annotation/XmlElement]
> java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlElement
> at
> io.swagger.v3.core.jackson.SwaggerAnnotationIntrospector.hasRequiredMarker(SwaggerAnnotationIntrospector.java:29)
> ~[swagger-core-2.2.19.jar:2.2.19]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20486) JMS OutOfMemoryError in Streaming Mode
[
https://issues.apache.org/jira/browse/CAMEL-20486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20486:
Priority: Minor (was: Major)
> JMS OutOfMemoryError in Streaming Mode
> --
>
> Key: CAMEL-20486
> URL: https://issues.apache.org/jira/browse/CAMEL-20486
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
>Affects Versions: 3.22.0
> Environment: *Environment: Platform: MacOS, Camel 3.22.0, Spring
> Boot: v2.7.18, Java 17.0.5*
>Reporter: Michael Rambichler
>Priority: Minor
>
> We are struggling with big messages sent over jms in streaming fashion in
> production.
> *Expected:* Messages are transferred in streaming mode without the need of
> the equivalent amount of memory as the size of the file.
>
> *Currently: Java.lang.OutOfMemoryError: Java heap space*
> *Environment: Platform: MacOS, Camel 3.22.0*
> And started some analysis locally with the following outcome:
>
> We setup a simple route wich receives a message from jms.
> {code:java}
> from("jms:testjms_q?streamMessageTypeEnabled=true=true=Bytes")
> .log("Start streaming from jms")
> .to("stream:out")
> .log("Finished"); {code}
> For testing purpose we restricted the Java Heap Size to 700MB (-Xmx700m)
>
> After some analysis we see the
> {code:java}
> io.netty.util.internal.PlatformDependent.allocateUninitializedArray(int size)
> {
> return UNINITIALIZED_ARRAY_ALLOCATION_THRESHOLD < 0 ||
> UNINITIALIZED_ARRAY_ALLOCATION_THRESHOLD > size ?
> new byte[size] : PlatformDependent0.allocateUninitializedArray(size);
> }{code}
> Where size is equivalent with the message size awaiting in the JMS queue
> (around 1GB)
> Which of course lead to a OutOfMemoryError
> {code:java}
> /:: Spring Boot :: (v2.7.18)
> 2024-02-28 19:00:54.857 INFO 36343 --- [ main]
> org.example.MySpringBootApplication : Starting MySpringBootApplication
> using Java 17.0.5 on atca-052347 with PID 36343
> (/Users/at00191173/dev/src/playground/helloJms/target/classes started by
> at00191173 in /Users/at00191173/dev/src/playground/helloJms)2024-02-28
> 19:00:54.859 INFO 36343 --- [ main]
> org.example.MySpringBootApplication : No active profile set, falling
> back to 1 default profile: "default"2024-02-28 19:00:55.518 WARN 36343 --- [
> main] io.undertow.websockets.jsr : UT026010: Buffer
> pool was not set on WebSocketDeploymentInfo, the default pool will be
> used2024-02-28 19:00:55.528 INFO 36343 --- [ main]
> io.undertow.servlet : Initializing Spring embedded
> WebApplicationContext2024-02-28 19:00:55.528 INFO 36343 --- [
> main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext:
> initialization completed in 645 ms2024-02-28 19:00:56.079 DEBUG 36343 --- [
> main] i.netty.util.internal.PlatformDependent : sun.misc.Unsafe:
> available2024-02-28 19:00:56.080 DEBUG 36343 --- [ main]
> i.netty.util.internal.PlatformDependent : -Dio.netty.tmpdir:
> /var/folders/1j/85cl6ywn0tbg9tg4z_kbnhsrgr/T (java.io.tmpdir)2024-02-28
> 19:00:56.080 DEBUG 36343 --- [ main]
> i.netty.util.internal.PlatformDependent : -Dio.netty.bitMode: 64
> (sun.arch.data.model)2024-02-28 19:00:56.080 DEBUG 36343 --- [
> main] i.netty.util.internal.PlatformDependent : Platform: MacOS2024-02-28
> 19:00:56.080 DEBUG 36343 --- [ main]
> i.netty.util.internal.PlatformDependent : -Dio.netty.maxDirectMemory: -1
> bytes2024-02-28 19:00:56.080 DEBUG 36343 --- [ main]
> i.netty.util.internal.PlatformDependent :
> -Dio.netty.uninitializedArrayAllocationThreshold: -12024-02-28 19:00:56.081
> DEBUG 36343 --- [ main] i.netty.util.internal.PlatformDependent :
> -Dio.netty.noPreferDirect: false2024-02-28 19:00:56.181 INFO 36343 --- [
> main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 2 endpoint(s)
> beneath base path '/actuator'2024-02-28 19:00:56.227 INFO 36343 --- [
> main] io.undertow : starting server: Undertow
> - 2.2.28.Final2024-02-28 19:00:56.231 INFO 36343 --- [ main]
> org.xnio : XNIO version 3.8.7.Final2024-02-28
> 19:00:56.236 INFO 36343 --- [ main] org.xnio.nio
> : XNIO NIO Implementation Version 3.8.7.Final2024-02-28
> 19:00:56.256 INFO 36343 --- [ main] org.jboss.threads
> : JBoss Threads version 3.1.0.Final2024-02-28 19:00:56.276 INFO
> 36343 --- [ main] o.s.b.w.e.undertow.UndertowWebServer :
> Undertow started on port(s) 8080 (http)2024-02-28 19:00:56.398 DEBUG 36343
> --- [ main]
[jira] [Created] (CAMEL-20487) REST API generator issue with typeOut
Marat Gubaidullin created CAMEL-20487:
-
Summary: REST API generator issue with typeOut
Key: CAMEL-20487
URL: https://issues.apache.org/jira/browse/CAMEL-20487
Project: Camel
Issue Type: Bug
Components: rest
Affects Versions: 4.4.0
Reporter: Marat Gubaidullin
If REST method typeOut defined then /api-doc throws exception.
How to reproduce:
1. rest.camel.yaml
{code:java}
- restConfiguration:
component: platform-http
apiContextPath: /api-doc
bindingMode: json
- rest:
id: rest-b339
get:
- id: get-c5d3
path: /account
to: direct:get-account
outType: karavan.simple.Account
bindingMode: json
- route:
id: route-4956
nodePrefixId: route-7d3
from:
id: from-cad7
uri: direct
parameters:
name: get-account
steps:
- setBody:
id: setBody-0623
expression:
groovy:
id: groovy-782e
expression: |-
def acc = new karavan.simple.Account()
acc.setAccountNumber('12345')
acc.setAccountName('test')
return acc
- log:
id: log-bd34
message: ${body}
{code}
2. Java Class
{code:java}
public class Account {
// Private fields for encapsulation
private String accountNumber;
private String accountName;
private double balance;
public Account() {
}
public String getAccountNumber() {
return accountNumber;
}
public void setAccountNumber(String accountNumber) {
this.accountNumber = accountNumber;
}
public String getAccountName() {
return accountName;
}
public void setAccountName(String accountName) {
this.accountName = accountName;
}
public double getBalance() {
return balance;
}
public void setBalance(double balance) {
this.balance = balance;
}
}
{code}
3. Run
{code:java}
jbang "-Dcamel.jbang.version=4.4.0" camel@apache/camel run *
--gav=karavan:simple:1
{code}
4. Call /api-doc
{code:java}
curl --location 'localhost:8080/api-doc'
{code}
5. Get exception:
{code:java}
2024-02-27 12:46:29.336 WARN 52151 --- [worker-thread-0]
agger.v3.core.jackson.ModelResolver : jackson
BeanDescription.findJsonValueAccessor not found, this could lead to inaccurate
result, please update jackson to 2.9+
2024-02-27 12:46:29.337 WARN 52151 --- [ntloop-thread-0]
ttp.vertx.VertxPlatformHttpConsumer : Failed handling platform-http endpoint
/api-doc. Caused by: [java.lang.NoClassDefFoundError -
javax/xml/bind/annotation/XmlElement]
java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlElement
at
io.swagger.v3.core.jackson.SwaggerAnnotationIntrospector.hasRequiredMarker(SwaggerAnnotationIntrospector.java:29)
~[swagger-core-2.2.19.jar:2.2.19]
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20452) Azure Storage Datalake CloudEvent transformer
[ https://issues.apache.org/jira/browse/CAMEL-20452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20452. -- Resolution: Fixed > Azure Storage Datalake CloudEvent transformer > - > > Key: CAMEL-20452 > URL: https://issues.apache.org/jira/browse/CAMEL-20452 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20486) JMS OutOfMemoryError in Streaming Mode
Michael Rambichler created CAMEL-20486:
--
Summary: JMS OutOfMemoryError in Streaming Mode
Key: CAMEL-20486
URL: https://issues.apache.org/jira/browse/CAMEL-20486
Project: Camel
Issue Type: Bug
Components: camel-jms
Affects Versions: 3.22.0
Environment: *Environment: Platform: MacOS, Camel 3.22.0, Spring Boot:
v2.7.18, Java 17.0.5*
Reporter: Michael Rambichler
We are struggling with big messages sent over jms in streaming fashion in
production.
*Expected:* Messages are transferred in streaming mode without the need of the
equivalent amount of memory as the size of the file.
*Currently: Java.lang.OutOfMemoryError: Java heap space*
*Environment: Platform: MacOS, Camel 3.22.0*
And started some analysis locally with the following outcome:
We setup a simple route wich receives a message from jms.
{code:java}
from("jms:testjms_q?streamMessageTypeEnabled=true=true=Bytes")
.log("Start streaming from jms")
.to("stream:out")
.log("Finished"); {code}
For testing purpose we restricted the Java Heap Size to 700MB (-Xmx700m)
After some analysis we see the
{code:java}
io.netty.util.internal.PlatformDependent.allocateUninitializedArray(int size) {
return UNINITIALIZED_ARRAY_ALLOCATION_THRESHOLD < 0 ||
UNINITIALIZED_ARRAY_ALLOCATION_THRESHOLD > size ?
new byte[size] : PlatformDependent0.allocateUninitializedArray(size);
}{code}
Where size is equivalent with the message size awaiting in the JMS queue
(around 1GB)
Which of course lead to a OutOfMemoryError
{code:java}
/:: Spring Boot :: (v2.7.18)
2024-02-28 19:00:54.857 INFO 36343 --- [ main]
org.example.MySpringBootApplication : Starting MySpringBootApplication
using Java 17.0.5 on atca-052347 with PID 36343
(/Users/at00191173/dev/src/playground/helloJms/target/classes started by
at00191173 in /Users/at00191173/dev/src/playground/helloJms)2024-02-28
19:00:54.859 INFO 36343 --- [ main]
org.example.MySpringBootApplication : No active profile set, falling back
to 1 default profile: "default"2024-02-28 19:00:55.518 WARN 36343 --- [
main] io.undertow.websockets.jsr : UT026010: Buffer pool was
not set on WebSocketDeploymentInfo, the default pool will be used2024-02-28
19:00:55.528 INFO 36343 --- [ main] io.undertow.servlet
: Initializing Spring embedded WebApplicationContext2024-02-28
19:00:55.528 INFO 36343 --- [ main]
w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext:
initialization completed in 645 ms2024-02-28 19:00:56.079 DEBUG 36343 --- [
main] i.netty.util.internal.PlatformDependent : sun.misc.Unsafe:
available2024-02-28 19:00:56.080 DEBUG 36343 --- [ main]
i.netty.util.internal.PlatformDependent : -Dio.netty.tmpdir:
/var/folders/1j/85cl6ywn0tbg9tg4z_kbnhsrgr/T (java.io.tmpdir)2024-02-28
19:00:56.080 DEBUG 36343 --- [ main]
i.netty.util.internal.PlatformDependent : -Dio.netty.bitMode: 64
(sun.arch.data.model)2024-02-28 19:00:56.080 DEBUG 36343 --- [ main]
i.netty.util.internal.PlatformDependent : Platform: MacOS2024-02-28
19:00:56.080 DEBUG 36343 --- [ main]
i.netty.util.internal.PlatformDependent : -Dio.netty.maxDirectMemory: -1
bytes2024-02-28 19:00:56.080 DEBUG 36343 --- [ main]
i.netty.util.internal.PlatformDependent :
-Dio.netty.uninitializedArrayAllocationThreshold: -12024-02-28 19:00:56.081
DEBUG 36343 --- [ main] i.netty.util.internal.PlatformDependent :
-Dio.netty.noPreferDirect: false2024-02-28 19:00:56.181 INFO 36343 --- [
main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 2 endpoint(s)
beneath base path '/actuator'2024-02-28 19:00:56.227 INFO 36343 --- [
main] io.undertow : starting server: Undertow -
2.2.28.Final2024-02-28 19:00:56.231 INFO 36343 --- [ main] org.xnio
: XNIO version 3.8.7.Final2024-02-28
19:00:56.236 INFO 36343 --- [ main] org.xnio.nio
: XNIO NIO Implementation Version 3.8.7.Final2024-02-28 19:00:56.256
INFO 36343 --- [ main] org.jboss.threads :
JBoss Threads version 3.1.0.Final2024-02-28 19:00:56.276 INFO 36343 --- [
main] o.s.b.w.e.undertow.UndertowWebServer : Undertow started on
port(s) 8080 (http)2024-02-28 19:00:56.398 DEBUG 36343 --- [ main]
o.a.camel.component.jms.JmsEndpoint : Using destinationName: testjms_q on
listenerContainer:
org.apache.camel.component.jms.DefaultJmsMessageListenerContainer@68454ed52024-02-28
19:00:56.400 INFO 36343 --- [ main]
o.a.c.impl.engine.AbstractCamelContext : Apache Camel 3.22.0 (MyCamel) is
starting2024-02-28 19:00:56.404 INFO 36343 --- [
[jira] [Created] (CAMEL-20485) Create a Camel-Milvus component
Andrea Cosentino created CAMEL-20485: Summary: Create a Camel-Milvus component Key: CAMEL-20485 URL: https://issues.apache.org/jira/browse/CAMEL-20485 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x https://github.com/milvus-io/milvus-sdk-java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20478) camel-jms: review and split Integration tests from Unit tests
[ https://issues.apache.org/jira/browse/CAMEL-20478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske reassigned CAMEL-20478: Assignee: Otavio Rodolfo Piske > camel-jms: review and split Integration tests from Unit tests > - > > Key: CAMEL-20478 > URL: https://issues.apache.org/jira/browse/CAMEL-20478 > Project: Camel > Issue Type: Test >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > > *Unit tests* > * Test component features > *Integration tests* > * Test broker features > * Test global camel features (i.e.: EIPs) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20484) camel-jbang - Using rest with /api context should have content-type in http summary
Claus Ibsen created CAMEL-20484: --- Summary: camel-jbang - Using rest with /api context should have content-type in http summary Key: CAMEL-20484 URL: https://issues.apache.org/jira/browse/CAMEL-20484 Project: Camel Issue Type: Improvement Components: camel-jbang, camel-rest-openapi Reporter: Claus Ibsen Fix For: 4.5.0 2024-02-28 17:23:49.465 INFO 40779 --- [ main] t.platform.http.main.MainHttpServer : HTTP endpoints summary 2024-02-28 17:23:49.466 INFO 40779 --- [ main] t.platform.http.main.MainHttpServer : http://0.0.0.0:8080/api-doc (GET) 2024-02-28 17:23:49.467 INFO 40779 --- [ main] t.platform.http.main.MainHttpServer : http://0.0.0.0:8080/helloapp (POST) (accept:application/json produce:application The /api-doc does not have any content-type. We should include that. It can be json | yaml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20470) camel-jbang - Rest dsl with /api context path should auto detect platform-http as consumer
[ https://issues.apache.org/jira/browse/CAMEL-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20470. - Resolution: Fixed > camel-jbang - Rest dsl with /api context path should auto detect > platform-http as consumer > -- > > Key: CAMEL-20470 > URL: https://issues.apache.org/jira/browse/CAMEL-20470 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.4.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.4.1, 4.5.0 > > > If you add api-context-path in rest configuration then jbang may fail on > startup as it cannot find a consumer component for it. If you set component = > platform-http it works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20470) camel-jbang - Rest dsl with /api context path should auto detect platform-http as consumer
[ https://issues.apache.org/jira/browse/CAMEL-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20470: Fix Version/s: 4.4.1 > camel-jbang - Rest dsl with /api context path should auto detect > platform-http as consumer > -- > > Key: CAMEL-20470 > URL: https://issues.apache.org/jira/browse/CAMEL-20470 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.4.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.4.1, 4.5.0 > > > If you add api-context-path in rest configuration then jbang may fail on > startup as it cannot find a consumer component for it. If you set component = > platform-http it works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20470) camel-jbang - Rest dsl with /api context path should auto detect platform-http as consumer
[ https://issues.apache.org/jira/browse/CAMEL-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20470: --- Assignee: Claus Ibsen > camel-jbang - Rest dsl with /api context path should auto detect > platform-http as consumer > -- > > Key: CAMEL-20470 > URL: https://issues.apache.org/jira/browse/CAMEL-20470 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.4.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.5.0 > > > If you add api-context-path in rest configuration then jbang may fail on > startup as it cannot find a consumer component for it. If you set component = > platform-http it works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20483) camel-core - Rest DSL with api-context-path may append null in host name
[ https://issues.apache.org/jira/browse/CAMEL-20483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20483. - Assignee: Claus Ibsen Resolution: Fixed > camel-core - Rest DSL with api-context-path may append null in host name > > > Key: CAMEL-20483 > URL: https://issues.apache.org/jira/browse/CAMEL-20483 > Project: Camel > Issue Type: Bug > Components: camel-core, rest >Affects Versions: 4.0.4, 4.4.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.1, 4.5.0 > > Attachments: Screenshot 2024-02-28 at 15.51.25.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20481) camel-core - Rest DSL should resolve placeholder for context-path and others
[
https://issues.apache.org/jira/browse/CAMEL-20481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20481.
-
Resolution: Fixed
> camel-core - Rest DSL should resolve placeholder for context-path and others
>
>
> Key: CAMEL-20481
> URL: https://issues.apache.org/jira/browse/CAMEL-20481
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.0.4, 4.4.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.4.1, 4.5.0
>
>
> You can end up with starting a Camel app with
> {code}
> 2024-02-28 13:42:46.558 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : HTTP endpoints summary
> 2024-02-28 13:42:46.559 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : http://0.0.0.0:8080/${app.mypath}
> (POST)(accept:application/json produce:appli
> {code}
> Where the context-path is not resolved:
> app.mypath = helloapp
> Its some code in RestDefinition that among others need to resolve placeholders
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20095) Create a component for OpenAI
[ https://issues.apache.org/jira/browse/CAMEL-20095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821726#comment-17821726 ] Zineb Bendhiba commented on CAMEL-20095: After multiple updates, I'm changing the code to have a global langchain4j for chat, available no matter what langchain component is needed, because langchain4j is huge project. I got some contribution for embeddings on my branch from [~lburgazzoli] I'm working on it this week. I need to add some tests and finish implementing stuff. For chat models: I'm running tests with Ollama docker image, so using Ollama model only. We can add any other model where it's possible to have an image, or free credentials. Also this component needs proper documentation to help user understand how to use it, before we can say it's ready. I just opened a draft PR to show progress only. I'll change status during this week. (cf https://github.com/apache/camel/pull/13341) > Create a component for OpenAI > - > > Key: CAMEL-20095 > URL: https://issues.apache.org/jira/browse/CAMEL-20095 > Project: Camel > Issue Type: New Feature >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Major > Attachments: telegram-openAPI.mp4 > > > Investigate on the Java library langchain4j, to create a component that can > integrate to OpenAI, HugginFace and more via langchain > > This is the link to the project : [https://github.com/langchain4j/langchain4j] > > the attached video is a first POC playing with Camel telegram and OpenAI > > [^telegram-openAPI.mp4] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20481) camel-core - Rest DSL should resolve placeholder for context-path and others
[
https://issues.apache.org/jira/browse/CAMEL-20481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20481:
Fix Version/s: (was: 4.0.5)
> camel-core - Rest DSL should resolve placeholder for context-path and others
>
>
> Key: CAMEL-20481
> URL: https://issues.apache.org/jira/browse/CAMEL-20481
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.0.4, 4.4.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.4.1, 4.5.0
>
>
> You can end up with starting a Camel app with
> {code}
> 2024-02-28 13:42:46.558 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : HTTP endpoints summary
> 2024-02-28 13:42:46.559 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : http://0.0.0.0:8080/${app.mypath}
> (POST)(accept:application/json produce:appli
> {code}
> Where the context-path is not resolved:
> app.mypath = helloapp
> Its some code in RestDefinition that among others need to resolve placeholders
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20483) camel-core - Rest DSL with api-context-path may append null in host name
[ https://issues.apache.org/jira/browse/CAMEL-20483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20483: Fix Version/s: (was: 4.0.5) > camel-core - Rest DSL with api-context-path may append null in host name > > > Key: CAMEL-20483 > URL: https://issues.apache.org/jira/browse/CAMEL-20483 > Project: Camel > Issue Type: Bug > Components: camel-core, rest >Affects Versions: 4.0.4, 4.4.0 >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.4.1, 4.5.0 > > Attachments: Screenshot 2024-02-28 at 15.51.25.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20483) camel-core - Rest DSL with api-context-path may append null in host name
Claus Ibsen created CAMEL-20483: --- Summary: camel-core - Rest DSL with api-context-path may append null in host name Key: CAMEL-20483 URL: https://issues.apache.org/jira/browse/CAMEL-20483 Project: Camel Issue Type: Bug Components: camel-core, rest Affects Versions: 4.4.0, 4.0.4 Reporter: Claus Ibsen Fix For: 4.4.1, 4.5.0, 4.0.5 Attachments: Screenshot 2024-02-28 at 15.51.25.png -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20482) camel-file - Can ant filter be optimized when using min/max depth
[ https://issues.apache.org/jira/browse/CAMEL-20482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20482: Priority: Minor (was: Major) > camel-file - Can ant filter be optimized when using min/max depth > - > > Key: CAMEL-20482 > URL: https://issues.apache.org/jira/browse/CAMEL-20482 > Project: Camel > Issue Type: Improvement > Components: camel-file >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > For example if you have min depth = 4, and max depth = 6, and use ant filer > for include / exclude then the filter may be executed for files not in those > depth levels. However the filter is needed to check for dirs, so some check > must be done. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20482) camel-file - Can ant filter be optimized when using min/max depth
Claus Ibsen created CAMEL-20482: --- Summary: camel-file - Can ant filter be optimized when using min/max depth Key: CAMEL-20482 URL: https://issues.apache.org/jira/browse/CAMEL-20482 Project: Camel Issue Type: Improvement Components: camel-file Reporter: Claus Ibsen Fix For: 4.x For example if you have min depth = 4, and max depth = 6, and use ant filer for include / exclude then the filter may be executed for files not in those depth levels. However the filter is needed to check for dirs, so some check must be done. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20481) camel-core - Rest DSL should resolve placeholder for context-path and others
[
https://issues.apache.org/jira/browse/CAMEL-20481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821693#comment-17821693
]
Claus Ibsen commented on CAMEL-20481:
-
Okay we have a better fix in some other part that benefit from this so lets
backport
> camel-core - Rest DSL should resolve placeholder for context-path and others
>
>
> Key: CAMEL-20481
> URL: https://issues.apache.org/jira/browse/CAMEL-20481
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.0.4, 4.4.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.5.0
>
>
> You can end up with starting a Camel app with
> {code}
> 2024-02-28 13:42:46.558 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : HTTP endpoints summary
> 2024-02-28 13:42:46.559 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : http://0.0.0.0:8080/${app.mypath}
> (POST)(accept:application/json produce:appli
> {code}
> Where the context-path is not resolved:
> app.mypath = helloapp
> Its some code in RestDefinition that among others need to resolve placeholders
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20481) camel-core - Rest DSL should resolve placeholder for context-path and others
[
https://issues.apache.org/jira/browse/CAMEL-20481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20481:
Fix Version/s: 4.4.1
4.0.5
> camel-core - Rest DSL should resolve placeholder for context-path and others
>
>
> Key: CAMEL-20481
> URL: https://issues.apache.org/jira/browse/CAMEL-20481
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.0.4, 4.4.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.4.1, 4.5.0, 4.0.5
>
>
> You can end up with starting a Camel app with
> {code}
> 2024-02-28 13:42:46.558 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : HTTP endpoints summary
> 2024-02-28 13:42:46.559 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : http://0.0.0.0:8080/${app.mypath}
> (POST)(accept:application/json produce:appli
> {code}
> Where the context-path is not resolved:
> app.mypath = helloapp
> Its some code in RestDefinition that among others need to resolve placeholders
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20481) camel-core - Rest DSL should resolve placeholder for context-path and others
[
https://issues.apache.org/jira/browse/CAMEL-20481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20481:
Fix Version/s: (was: 4.4.1)
(was: 4.0.5)
> camel-core - Rest DSL should resolve placeholder for context-path and others
>
>
> Key: CAMEL-20481
> URL: https://issues.apache.org/jira/browse/CAMEL-20481
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.0.4, 4.4.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.5.0
>
>
> You can end up with starting a Camel app with
> {code}
> 2024-02-28 13:42:46.558 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : HTTP endpoints summary
> 2024-02-28 13:42:46.559 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : http://0.0.0.0:8080/${app.mypath}
> (POST)(accept:application/json produce:appli
> {code}
> Where the context-path is not resolved:
> app.mypath = helloapp
> Its some code in RestDefinition that among others need to resolve placeholders
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20481) camel-core - Rest DSL should resolve placeholder for context-path and others
[
https://issues.apache.org/jira/browse/CAMEL-20481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821679#comment-17821679
]
Claus Ibsen commented on CAMEL-20481:
-
Argh it was wrong placeholder ${xxx} should be {{xxx}} instead
> camel-core - Rest DSL should resolve placeholder for context-path and others
>
>
> Key: CAMEL-20481
> URL: https://issues.apache.org/jira/browse/CAMEL-20481
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.0.4, 4.4.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.4.1, 4.5.0, 4.0.5
>
>
> You can end up with starting a Camel app with
> {code}
> 2024-02-28 13:42:46.558 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : HTTP endpoints summary
> 2024-02-28 13:42:46.559 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : http://0.0.0.0:8080/${app.mypath}
> (POST)(accept:application/json produce:appli
> {code}
> Where the context-path is not resolved:
> app.mypath = helloapp
> Its some code in RestDefinition that among others need to resolve placeholders
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20481) camel-core - Rest DSL should resolve placeholder for context-path and others
[
https://issues.apache.org/jira/browse/CAMEL-20481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821678#comment-17821678
]
Claus Ibsen commented on CAMEL-20481:
-
These are created a bit special without the reifier so they have to add
placeholder code in the model classes
> camel-core - Rest DSL should resolve placeholder for context-path and others
>
>
> Key: CAMEL-20481
> URL: https://issues.apache.org/jira/browse/CAMEL-20481
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.0.4, 4.4.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.4.1, 4.5.0, 4.0.5
>
>
> You can end up with starting a Camel app with
> {code}
> 2024-02-28 13:42:46.558 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : HTTP endpoints summary
> 2024-02-28 13:42:46.559 INFO 29979 --- [ main]
> t.platform.http.main.MainHttpServer : http://0.0.0.0:8080/${app.mypath}
> (POST)(accept:application/json produce:appli
> {code}
> Where the context-path is not resolved:
> app.mypath = helloapp
> Its some code in RestDefinition that among others need to resolve placeholders
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20476) Camel-AWS-Bedrock: Support Amazon Titan Image Generator G1 model
[ https://issues.apache.org/jira/browse/CAMEL-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20476. -- Resolution: Fixed > Camel-AWS-Bedrock: Support Amazon Titan Image Generator G1 model > > > Key: CAMEL-20476 > URL: https://issues.apache.org/jira/browse/CAMEL-20476 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20466) camel-core - Rest DSL to be inlined by default to avoid clutter up list of routes
[ https://issues.apache.org/jira/browse/CAMEL-20466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20466. - Resolution: Fixed > camel-core - Rest DSL to be inlined by default to avoid clutter up list of > routes > - > > Key: CAMEL-20466 > URL: https://issues.apache.org/jira/browse/CAMEL-20466 > Project: Camel > Issue Type: Improvement > Components: camel-core, rest >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > When using rest-dsl you have 1 route per rest verb (GET, POST etc) and then > another route that it typically call via direct. > There is an inlined = true option you can use to make this a single route. We > should make this the default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20481) camel-core - Rest DSL should resolve placeholder for context-path and others
Claus Ibsen created CAMEL-20481:
---
Summary: camel-core - Rest DSL should resolve placeholder for
context-path and others
Key: CAMEL-20481
URL: https://issues.apache.org/jira/browse/CAMEL-20481
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 4.4.0, 4.0.4
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 4.4.1, 4.5.0, 4.0.5
You can end up with starting a Camel app with
{code}
2024-02-28 13:42:46.558 INFO 29979 --- [ main]
t.platform.http.main.MainHttpServer : HTTP endpoints summary
2024-02-28 13:42:46.559 INFO 29979 --- [ main]
t.platform.http.main.MainHttpServer : http://0.0.0.0:8080/${app.mypath}
(POST)(accept:application/json produce:appli
{code}
Where the context-path is not resolved:
app.mypath = helloapp
Its some code in RestDefinition that among others need to resolve placeholders
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20466) camel-core - Rest DSL to be inlined by default to avoid clutter up list of routes
[ https://issues.apache.org/jira/browse/CAMEL-20466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821237#comment-17821237 ] Claus Ibsen edited comment on CAMEL-20466 at 2/28/24 12:25 PM: --- TODO: inline as default *DONE* TODO: camel-jbang debug should still work *DONE* TODO: inlined should make source:line still work *DONE* was (Author: davsclaus): TODO: inline as default *DONE* TODO: camel-jbang debug should still work *DONE* TODO: inlined should make source:line still work > camel-core - Rest DSL to be inlined by default to avoid clutter up list of > routes > - > > Key: CAMEL-20466 > URL: https://issues.apache.org/jira/browse/CAMEL-20466 > Project: Camel > Issue Type: Improvement > Components: camel-core, rest >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > When using rest-dsl you have 1 route per rest verb (GET, POST etc) and then > another route that it typically call via direct. > There is an inlined = true option you can use to make this a single route. We > should make this the default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20480) camel-platform-http-vertx - Execute using thread pool to not block event loop
Claus Ibsen created CAMEL-20480:
---
Summary: camel-platform-http-vertx - Execute using thread pool to
not block event loop
Key: CAMEL-20480
URL: https://issues.apache.org/jira/browse/CAMEL-20480
Project: Camel
Issue Type: Improvement
Components: camel-platform-http-vertx
Reporter: Claus Ibsen
Fix For: 4.x
When using camel jbang debug then you can be slow during bebugging and cause
the vertx thread to WARN log
{code}
2024-02-28 12:42:26.814 WARN 27518 --- [-thread-checker]
ertx.core.impl.BlockedThreadChecker : Thread
Thread[vert.x-worker-thread-4,5,main] has been blocked for 264930 ms, time
limit is 6 ms
io.vertx.core.VertxException: Thread blocked
at java.base/jdk.internal.misc.Unsafe.park(Native Method) ~[?:?]
at
java.base/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
~[?:?]
at
java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:717)
~[?:?]
at
java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1074)
~[?:?]
at
java.base/java.util.concurrent.CountDownLatch.await(CountDownLatch.java:276)
~[?:?]
at
org.apache.camel.impl.debugger.DefaultBacklogDebugger$NodeBreakpoint.beforeProcess(DefaultBacklogDebugger.java:910)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.debugger.DefaultDebugger.onBeforeProcess(DefaultDebugger.java:290)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.debugger.DefaultDebugger.beforeProcess(DefaultDebugger.java:232)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.debugger.DefaultBacklogDebugger.beforeProcess(DefaultBacklogDebugger.java:776)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.engine.CamelInternalProcessor$BacklogDebuggerAdvice.before(CamelInternalProcessor.java:769)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.engine.CamelInternalProcessor$BacklogDebuggerAdvice.before(CamelInternalProcessor.java:755)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:317)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:102)
~[camel-core-processor-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.doRun(DefaultReactiveExecutor.java:199)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeReactiveWork(DefaultReactiveExecutor.java:189)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.tryExecuteReactiveWork(DefaultReactiveExecutor.java:166)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:148)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:59)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at org.apache.camel.processor.Pipeline.process(Pipeline.java:163)
~[camel-core-processor-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.engine.CamelInternalProcessor.processNonTransacted(CamelInternalProcessor.java:354)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:330)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:82)
~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:32)
~[camel-support-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.component.platform.http.vertx.VertxPlatformHttpConsumer.processExchange(VertxPlatformHttpConsumer.java:236)
~[camel-platform-http-vertx-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.component.platform.http.vertx.VertxPlatformHttpConsumer.lambda$handleRequest$1(VertxPlatformHttpConsumer.java:204)
~[camel-platform-http-vertx-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
at
org.apache.camel.component.platform.http.vertx.VertxPlatformHttpConsumer$$Lambda$514/0x0008014aa340.call(Unknown
Source) ~[?:?]
at
[jira] [Comment Edited] (CAMEL-20466) camel-core - Rest DSL to be inlined by default to avoid clutter up list of routes
[ https://issues.apache.org/jira/browse/CAMEL-20466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821237#comment-17821237 ] Claus Ibsen edited comment on CAMEL-20466 at 2/28/24 11:38 AM: --- TODO: inline as default *DONE* TODO: camel-jbang debug should still work *DONE* TODO: inlined should make source:line still work was (Author: davsclaus): TODO: inline as default *DONE* TODO: camel-jbang debug should still work TODO: inlined should make source:line still work > camel-core - Rest DSL to be inlined by default to avoid clutter up list of > routes > - > > Key: CAMEL-20466 > URL: https://issues.apache.org/jira/browse/CAMEL-20466 > Project: Camel > Issue Type: Improvement > Components: camel-core, rest >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > When using rest-dsl you have 1 route per rest verb (GET, POST etc) and then > another route that it typically call via direct. > There is an inlined = true option you can use to make this a single route. We > should make this the default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20478) camel-jms: review and split Integration tests from Unit tests
[ https://issues.apache.org/jira/browse/CAMEL-20478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-20478: - Description: *Unit tests* * Test component features *Integration tests* * Test broker features * Test global camel features (i.e.: EIPs) was: Unit tests * Test component features * Integration tests * Test broker features * Test global camel features (i.e.: EIPs) > camel-jms: review and split Integration tests from Unit tests > - > > Key: CAMEL-20478 > URL: https://issues.apache.org/jira/browse/CAMEL-20478 > Project: Camel > Issue Type: Test >Reporter: Otavio Rodolfo Piske >Priority: Major > > *Unit tests* > * Test component features > *Integration tests* > * Test broker features > * Test global camel features (i.e.: EIPs) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20478) camel-jms: review and split Integration tests from Unit tests
[ https://issues.apache.org/jira/browse/CAMEL-20478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-20478: - Description: Unit tests * Test component features * Integration tests * Test broker features * Test global camel features (i.e.: EIPs) > camel-jms: review and split Integration tests from Unit tests > - > > Key: CAMEL-20478 > URL: https://issues.apache.org/jira/browse/CAMEL-20478 > Project: Camel > Issue Type: Test >Reporter: Otavio Rodolfo Piske >Priority: Major > > Unit tests > * Test component features > * > Integration tests > * Test broker features > * Test global camel features (i.e.: EIPs) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20479) camel-test-infra-artemis: delay broker configuration
[ https://issues.apache.org/jira/browse/CAMEL-20479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-20479: - Affects Version/s: 4.5.0 > camel-test-infra-artemis: delay broker configuration > - > > Key: CAMEL-20479 > URL: https://issues.apache.org/jira/browse/CAMEL-20479 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.5.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.5.0 > > > Configuring the broker in the AbstractArtemisEmbeddedService constructor is > likely unnecessary and as, in many cases, we are using a singleton instance > of the broker. > We should delay the configuration to the startup phase once we verified that > no broker has been configured. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20479) camel-test-infra-artemis: delay broker configuration
[ https://issues.apache.org/jira/browse/CAMEL-20479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-20479: - Fix Version/s: 4.5.0 > camel-test-infra-artemis: delay broker configuration > - > > Key: CAMEL-20479 > URL: https://issues.apache.org/jira/browse/CAMEL-20479 > Project: Camel > Issue Type: Improvement >Reporter: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.5.0 > > > Configuring the broker in the AbstractArtemisEmbeddedService constructor is > likely unnecessary and as, in many cases, we are using a singleton instance > of the broker. > We should delay the configuration to the startup phase once we verified that > no broker has been configured. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20479) camel-test-infra-artemis: delay broker configuration
Otavio Rodolfo Piske created CAMEL-20479: Summary: camel-test-infra-artemis: delay broker configuration Key: CAMEL-20479 URL: https://issues.apache.org/jira/browse/CAMEL-20479 Project: Camel Issue Type: Improvement Reporter: Otavio Rodolfo Piske Configuring the broker in the AbstractArtemisEmbeddedService constructor is likely unnecessary and as, in many cases, we are using a singleton instance of the broker. We should delay the configuration to the startup phase once we verified that no broker has been configured. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20478) camel-jms: review and split Integration tests from Unit tests
Otavio Rodolfo Piske created CAMEL-20478: Summary: camel-jms: review and split Integration tests from Unit tests Key: CAMEL-20478 URL: https://issues.apache.org/jira/browse/CAMEL-20478 Project: Camel Issue Type: Test Reporter: Otavio Rodolfo Piske -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19553) camel-quartz: ensure tests have assertions
[ https://issues.apache.org/jira/browse/CAMEL-19553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821596#comment-17821596 ] Otavio Rodolfo Piske commented on CAMEL-19553: -- Please, feel free to look at those tests and add/adjust the assertions as needed. Thanks for contributing! > camel-quartz: ensure tests have assertions > -- > > Key: CAMEL-19553 > URL: https://issues.apache.org/jira/browse/CAMEL-19553 > Project: Camel > Issue Type: Task > Components: camel-quartz, camel-quartz2, tests >Affects Versions: 4.0.0 >Reporter: Otavio Rodolfo Piske >Priority: Minor > Labels: easy, help-wanted > > Some tests do not have assertions and that prevents us from fully > understanding what is a test failure and what is an error. In many cases, > these are tests that were originally written with older versions of JUnit in > mind (i.e: equal or older than v4), so they lack modernization. > > We should ensure every test has an assertion. The assertion does not, > necessarily, needs to be visible (i.e.: it can be called in a separate > method). > > When asserting that a piece of code does not throw an error, we should use > JUnit's 5 > [assertDoesNotThrow|https://junit.org/junit5/docs/5.8.2/api/org.junit.jupiter.api/org/junit/jupiter/api/Assertions.html#assertDoesNotThrow(org.junit.jupiter.api.function.Executable)] > (either the linked method or one of the others with different signatures). > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19553) camel-quartz: ensure tests have assertions
[ https://issues.apache.org/jira/browse/CAMEL-19553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821589#comment-17821589 ] Gaëlle Fournier commented on CAMEL-19553: - I can take care of it if help is still needed. > camel-quartz: ensure tests have assertions > -- > > Key: CAMEL-19553 > URL: https://issues.apache.org/jira/browse/CAMEL-19553 > Project: Camel > Issue Type: Task > Components: camel-quartz, camel-quartz2, tests >Affects Versions: 4.0.0 >Reporter: Otavio Rodolfo Piske >Priority: Minor > Labels: easy, help-wanted > > Some tests do not have assertions and that prevents us from fully > understanding what is a test failure and what is an error. In many cases, > these are tests that were originally written with older versions of JUnit in > mind (i.e: equal or older than v4), so they lack modernization. > > We should ensure every test has an assertion. The assertion does not, > necessarily, needs to be visible (i.e.: it can be called in a separate > method). > > When asserting that a piece of code does not throw an error, we should use > JUnit's 5 > [assertDoesNotThrow|https://junit.org/junit5/docs/5.8.2/api/org.junit.jupiter.api/org/junit/jupiter/api/Assertions.html#assertDoesNotThrow(org.junit.jupiter.api.function.Executable)] > (either the linked method or one of the others with different signatures). > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20475) camel-bindy - Handle values with quotes better
[ https://issues.apache.org/jira/browse/CAMEL-20475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20475. - Assignee: Federico Mariani Resolution: Fixed > camel-bindy - Handle values with quotes better > -- > > Key: CAMEL-20475 > URL: https://issues.apache.org/jira/browse/CAMEL-20475 > Project: Camel > Issue Type: Bug > Components: camel-bindy >Affects Versions: 4.0.4, 4.4.0 >Reporter: Claus Ibsen >Assignee: Federico Mariani >Priority: Minor > Fix For: 4.4.1, 4.5.0, 4.0.5 > > > https://github.com/apache/camel/pull/13270 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20477) camel-jms: test flakiness
Otavio Rodolfo Piske created CAMEL-20477: Summary: camel-jms: test flakiness Key: CAMEL-20477 URL: https://issues.apache.org/jira/browse/CAMEL-20477 Project: Camel Issue Type: Test Components: camel-jms Affects Versions: 4.5.0 Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Fix For: 4.5.0 There's seems to be a higher incidence of test flakiness on JMS lately. We should investigate and Fix. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20476) Camel-AWS-Bedrock: Support Amazon Titan Image Generator G1 model
Andrea Cosentino created CAMEL-20476: Summary: Camel-AWS-Bedrock: Support Amazon Titan Image Generator G1 model Key: CAMEL-20476 URL: https://issues.apache.org/jira/browse/CAMEL-20476 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20463) Create an AWS Bedrock Runtime component
[ https://issues.apache.org/jira/browse/CAMEL-20463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20463. -- Resolution: Fixed > Create an AWS Bedrock Runtime component > --- > > Key: CAMEL-20463 > URL: https://issues.apache.org/jira/browse/CAMEL-20463 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20475) camel-bindy - Handle values with quotes better
Claus Ibsen created CAMEL-20475: --- Summary: camel-bindy - Handle values with quotes better Key: CAMEL-20475 URL: https://issues.apache.org/jira/browse/CAMEL-20475 Project: Camel Issue Type: Bug Components: camel-bindy Affects Versions: 4.4.0, 4.0.4 Reporter: Claus Ibsen Fix For: 4.4.1, 4.5.0, 4.0.5 https://github.com/apache/camel/pull/13270 -- This message was sent by Atlassian Jira (v8.20.10#820010)
