[jira] [Updated] (CAMEL-18326) google-mail-stream
[
https://issues.apache.org/jira/browse/CAMEL-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jérôme GARCIA updated CAMEL-18326:
--
Description:
Hello,
In *google-mail-stream* component, the mail body is displayed as plain text and
is not easy to manipulate the data.
The component should add the possibility to change this behavior and displayed
a standardize object (JSON or other).
{code:java}
// code placeholder
from('google-mail-stream:index?' +
'applicationName={{camel-app-name}}&' +
'accessToken={{gmail.client.access.token}}&' +
'refreshToken={{gmail.client.access.refresh.token}}&' +
'clientId={{gmail.client.id}}&' +
'query=is:unread&' +
'clientSecret={{gmail.client.secret}}')
.log('body: ${body}') {code}
Here is the format received by google-mail component for example:
{code:java}
// code placeholder
{
"historyId": "",
"id": "",
"internalDate": "",
"labelIds": [ ],
"payload": {
"body": {
"size": 0
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": "",
"parts": [
{
"body": {
"data": "",
"size": 241
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": ""
},
{
"body": {
"data": "",
"size": 2519
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": ""
}
]
},
"sizeEstimate": 3513,
"snippet": "",
"threadId": ""
}
{code}
What do you think?
was:
Hello,
In *google-mail-stream* component, the mail body is displayed as plain text and
is not easy to manipulate the data.
The component should add the possibility to change this behavior and displayed
a standardize object (JSON or other).
{code:java}
// code placeholder
from('google-mail-stream:index?' +
'applicationName={{camel-app-name}}&' +
'accessToken={{gmail.client.access.token}}&' +
'refreshToken={{gmail.client.access.refresh.token}}&' +
'clientId={{gmail.client.id}}&' +
'query=is:unread&' +
'clientSecret={{gmail.client.secret}}')
.log('${body}') {code}
Here is the format received by google-mail component for example:
{code:java}
// code placeholder
{
"historyId": "",
"id": "",
"internalDate": "",
"labelIds": [ ],
"payload": {
"body": {
"size": 0
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": "",
"parts": [
{
"body": {
"data": "",
"size": 241
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": ""
},
{
"body": {
"data": "",
"size": 2519
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": ""
}
]
},
"sizeEstimate": 3513,
"snippet": "",
"threadId": ""
}
{code}
What do you think?
> google-mail-stream
> --
>
> Key: CAMEL-18326
> URL: https://issues.apache.org/jira/browse/CAMEL-18326
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-mail-stream
>Affects Versions: 3.16.0
>Reporter: Jérôme GARCIA
>Priority: Minor
> Labels: camel-core, google
>
> Hello,
>
> In *google-mail-stream* component, the mail body is displayed as plain text
> and is not easy to manipulate the data.
> The component should add the possibility to change this behavior and
> displayed a standardize object (JSON or other).
>
> {code:java}
> // code placeholder
> from('google-mail-stream:index?' +
> 'applicationName={{camel-app-name}}&' +
> 'accessToken={{gmail.client.access.token}}&' +
> 'refreshToken={{gmail.client.access.refresh.token}}&' +
> 'clientId={{gmail.client.id}}&' +
> 'query=is:unread&' +
> 'clientSecret={{gmail.client.secret}}')
> .log('body: ${body}') {code}
>
> Here is the format received by google-mail component for example:
>
> {code:java}
> // code placeholder
> {
> "historyId": "",
> "id": "",
> "internalDate": "",
> "labelIds": [ ],
> "payload": {
> "body": {
> "size": 0
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": "",
> "parts": [
> {
> "body": {
> "data": "",
> "size": 241
> },
>
[jira] [Comment Edited] (CAMEL-18326) google-mail-stream
[
https://issues.apache.org/jira/browse/CAMEL-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573056#comment-17573056
]
Jérôme GARCIA edited comment on CAMEL-18326 at 7/29/22 4:35 PM:
Sure but today the data format as a plain text cannot be transform at all, it
should be a standard and not an already formatted data.
Here is an example of the actual data provided by the component :
{code:java}
// code placeholder
body: test
[1] [image: Bashroom]
[1] * Jérôme x *
[1] Bashroom's R Engineer & Software Architect
[1]
{code}
It's not usable to manipulate it.
was (Author: JIRAUSER293631):
Sure but today the data format as a plain text cannot be transform at all, it
should be a standard and not an already formatted data.
Here is an example of the actual data provided by the component :
{code:java}
// code placeholder
body: test
[1] [image: Bashroom]
[1] * Jérôme x *
[1] Bashroom's R Engineer & Software Architect
[1]
{code}
It's not usable to manipulate it.
> google-mail-stream
> --
>
> Key: CAMEL-18326
> URL: https://issues.apache.org/jira/browse/CAMEL-18326
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-mail-stream
>Affects Versions: 3.16.0
>Reporter: Jérôme GARCIA
>Priority: Minor
> Labels: camel-core, google
>
> Hello,
>
> In *google-mail-stream* component, the mail body is displayed as plain text
> and is not easy to manipulate the data.
> The component should add the possibility to change this behavior and
> displayed a standardize object (JSON or other).
>
> {code:java}
> // code placeholder
> from('google-mail-stream:index?' +
> 'applicationName={{camel-app-name}}&' +
> 'accessToken={{gmail.client.access.token}}&' +
> 'refreshToken={{gmail.client.access.refresh.token}}&' +
> 'clientId={{gmail.client.id}}&' +
> 'query=is:unread&' +
> 'clientSecret={{gmail.client.secret}}')
> .log('${body}') {code}
>
> Here is the format received by google-mail component for example:
>
> {code:java}
> // code placeholder
> {
> "historyId": "",
> "id": "",
> "internalDate": "",
> "labelIds": [ ],
> "payload": {
> "body": {
> "size": 0
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": "",
> "parts": [
> {
> "body": {
> "data": "",
> "size": 241
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": ""
> },
> {
> "body": {
> "data": "",
> "size": 2519
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": ""
> }
> ]
> },
> "sizeEstimate": 3513,
> "snippet": "",
> "threadId": ""
> }
> {code}
>
> What do you think?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18326) google-mail-stream
[
https://issues.apache.org/jira/browse/CAMEL-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573056#comment-17573056
]
Jérôme GARCIA commented on CAMEL-18326:
---
Sure but today the data format as a plain text cannot be transform at all, it
should be a standard and not an already formatted data.
Here is an example of the actual data provided by the component :
{code:java}
// code placeholder
body: test
[1] [image: Bashroom]
[1] * Jérôme x *
[1] Bashroom's R Engineer & Software Architect
[1]
{code}
It's not usable to manipulate it.
> google-mail-stream
> --
>
> Key: CAMEL-18326
> URL: https://issues.apache.org/jira/browse/CAMEL-18326
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-mail-stream
>Affects Versions: 3.16.0
>Reporter: Jérôme GARCIA
>Priority: Minor
> Labels: camel-core, google
>
> Hello,
>
> In *google-mail-stream* component, the mail body is displayed as plain text
> and is not easy to manipulate the data.
> The component should add the possibility to change this behavior and
> displayed a standardize object (JSON or other).
>
> {code:java}
> // code placeholder
> from('google-mail-stream:index?' +
> 'applicationName={{camel-app-name}}&' +
> 'accessToken={{gmail.client.access.token}}&' +
> 'refreshToken={{gmail.client.access.refresh.token}}&' +
> 'clientId={{gmail.client.id}}&' +
> 'query=is:unread&' +
> 'clientSecret={{gmail.client.secret}}')
> .log('${body}') {code}
>
> Here is the format received by google-mail component for example:
>
> {code:java}
> // code placeholder
> {
> "historyId": "",
> "id": "",
> "internalDate": "",
> "labelIds": [ ],
> "payload": {
> "body": {
> "size": 0
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": "",
> "parts": [
> {
> "body": {
> "data": "",
> "size": 241
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": ""
> },
> {
> "body": {
> "data": "",
> "size": 2519
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": ""
> }
> ]
> },
> "sizeEstimate": 3513,
> "snippet": "",
> "threadId": ""
> }
> {code}
>
> What do you think?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18326) google-mail-stream
[
https://issues.apache.org/jira/browse/CAMEL-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jérôme GARCIA updated CAMEL-18326:
--
Description:
Hello,
In *google-mail-stream* component, the mail body is displayed as plain text and
is not easy to manipulate the data.
The component should add the possibility to change this behavior and displayed
a standardize object (JSON or other).
{code:java}
// code placeholder
from('google-mail-stream:index?' +
'applicationName={{camel-app-name}}&' +
'accessToken={{gmail.client.access.token}}&' +
'refreshToken={{gmail.client.access.refresh.token}}&' +
'clientId={{gmail.client.id}}&' +
'query=is:unread&' +
'clientSecret={{gmail.client.secret}}')
.log('${body}') {code}
Here is the format received by google-mail component for example:
{code:java}
// code placeholder
{
"historyId": "",
"id": "",
"internalDate": "",
"labelIds": [ ],
"payload": {
"body": {
"size": 0
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": "",
"parts": [
{
"body": {
"data": "",
"size": 241
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": ""
},
{
"body": {
"data": "",
"size": 2519
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": ""
}
]
},
"sizeEstimate": 3513,
"snippet": "",
"threadId": ""
}
{code}
What do you think?
was:
Hello,
In *google-mail-stream* component, the mail body is displayed as plain text and
is not easy to manipulate the data.
The component should add the possibility to change this behavior and displayed
a standardize object (JSON or other).
{code:java}
// code placeholder
from('google-mail-stream:index?' +
'applicationName={{camel-app-name}}&' +
'accessToken={{gmail.client.access.token}}&' +
'refreshToken={{gmail.client.access.refresh.token}}&' +
'clientId={{gmail.client.id}}&' +
'query=is:unread&' +
'clientSecret={{gmail.client.secret}}')
.log('${body}') {code}
Here is the format received by google-mail component for example:
{code:java}
// code placeholder
{
"historyId": "",
"id": "",
"internalDate": "",
"labelIds": [ ],
"payload": {
"body": {
"size": 0
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": "",
"parts": [
{
"body": {
"data": "",
"size": 241
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": ""
},
{
"body": {
"data": "",
"size": 2519
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": ""
}
]
},
"sizeEstimate": 3513,
"snippet": "",
"threadId": ""
}
{code}
What do you think?
> google-mail-stream
> --
>
> Key: CAMEL-18326
> URL: https://issues.apache.org/jira/browse/CAMEL-18326
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-mail-stream
>Affects Versions: 3.16.0
>Reporter: Jérôme GARCIA
>Priority: Minor
> Labels: camel-core, google
>
> Hello,
>
> In *google-mail-stream* component, the mail body is displayed as plain text
> and is not easy to manipulate the data.
> The component should add the possibility to change this behavior and
> displayed a standardize object (JSON or other).
>
> {code:java}
> // code placeholder
> from('google-mail-stream:index?' +
> 'applicationName={{camel-app-name}}&' +
> 'accessToken={{gmail.client.access.token}}&' +
> 'refreshToken={{gmail.client.access.refresh.token}}&' +
> 'clientId={{gmail.client.id}}&' +
> 'query=is:unread&' +
> 'clientSecret={{gmail.client.secret}}')
> .log('${body}') {code}
>
> Here is the format received by google-mail
[jira] [Updated] (CAMEL-18326) google-mail-stream
[
https://issues.apache.org/jira/browse/CAMEL-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jérôme GARCIA updated CAMEL-18326:
--
Description:
Hello,
In *google-mail-stream* component, the mail body is displayed as plain text and
is not easy to manipulate the data.
The component should add the possibility to change this behavior and displayed
a standardize object (JSON or other).
{code:java}
// code placeholder
from('google-mail-stream:index?' +
'applicationName={{camel-app-name}}&' +
'accessToken={{gmail.client.access.token}}&' +
'refreshToken={{gmail.client.access.refresh.token}}&' +
'clientId={{gmail.client.id}}&' +
'query=is:unread&' +
'clientSecret={{gmail.client.secret}}')
.log('${body}') {code}
Here is the format received by google-mail component for example:
{code:java}
// code placeholder
{
"historyId": "",
"id": "",
"internalDate": "",
"labelIds": [ ],
"payload": {
"body": {
"size": 0
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": "",
"parts": [
{
"body": {
"data": "",
"size": 241
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": ""
},
{
"body": {
"data": "",
"size": 2519
},
"filename": "",
"headers": [
{
"name": "",
"value": ""
},
{
"name": "",
"value": ""
}
],
"mimeType": "",
"partId": ""
}
]
},
"sizeEstimate": 3513,
"snippet": "",
"threadId": ""
}
{code}
What do you think?
was:
Hello,
In *google-mail-stream* component, the mail body is displayed as plain text and
is not easy to manipulate the data.
The component should add the possibility to change this behavior and displayed
a standardize object (JSON or other).
{code:java}
// code placeholder
from('google-mail-stream:index?' +
'applicationName={{camel-app-name}}&' +
'accessToken={{gmail.client.access.token}}&' +
'refreshToken={{gmail.client.access.refresh.token}}&' +
'clientId={{gmail.client.id}}&' +
'query=is:unread&' +
'clientSecret={{gmail.client.secret}}')
.log('${body}') {code}
What do you think?
> google-mail-stream
> --
>
> Key: CAMEL-18326
> URL: https://issues.apache.org/jira/browse/CAMEL-18326
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-mail-stream
>Affects Versions: 3.16.0
>Reporter: Jérôme GARCIA
>Priority: Minor
> Labels: camel-core, google
>
> Hello,
>
> In *google-mail-stream* component, the mail body is displayed as plain text
> and is not easy to manipulate the data.
> The component should add the possibility to change this behavior and
> displayed a standardize object (JSON or other).
>
> {code:java}
> // code placeholder
> from('google-mail-stream:index?' +
> 'applicationName={{camel-app-name}}&' +
> 'accessToken={{gmail.client.access.token}}&' +
> 'refreshToken={{gmail.client.access.refresh.token}}&' +
> 'clientId={{gmail.client.id}}&' +
> 'query=is:unread&' +
> 'clientSecret={{gmail.client.secret}}')
> .log('${body}') {code}
>
> Here is the format received by google-mail component for example:
>
> {code:java}
> // code placeholder
> {
> "historyId": "",
> "id": "",
> "internalDate": "",
> "labelIds": [ ],
> "payload": {
> "body": {
> "size": 0
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> },
> {
> "name": "",
> "value": ""
> },
> {
> "name": "",
> "value": ""
> },
> {
> "name": "",
> "value": ""
> },
> {
> "name": "",
> "value": ""
> },
> {
> "name": "",
> "value": ""
> },
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": "",
> "parts": [
> {
> "body": {
> "data": "",
> "size": 241
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
>
[jira] [Commented] (CAMEL-18326) google-mail-stream
[
https://issues.apache.org/jira/browse/CAMEL-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573052#comment-17573052
]
Andrea Cosentino commented on CAMEL-18326:
--
I think you could use any dataformat immediately after consuming and transform
the body in the format you want to display or consume. There is no advantages
in adding an option to choose the output, because what you would do in the
component, it is what the dataformat would do immediately after consuming the
message.
> google-mail-stream
> --
>
> Key: CAMEL-18326
> URL: https://issues.apache.org/jira/browse/CAMEL-18326
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-mail-stream
>Affects Versions: 3.16.0
>Reporter: Jérôme GARCIA
>Priority: Minor
> Labels: camel-core, google
>
> Hello,
>
> In *google-mail-stream* component, the mail body is displayed as plain text
> and is not easy to manipulate the data.
> The component should add the possibility to change this behavior and
> displayed a standardize object (JSON or other).
>
> {code:java}
> // code placeholder
> from('google-mail-stream:index?' +
> 'applicationName={{camel-app-name}}&' +
> 'accessToken={{gmail.client.access.token}}&' +
> 'refreshToken={{gmail.client.access.refresh.token}}&' +
> 'clientId={{gmail.client.id}}&' +
> 'query=is:unread&' +
> 'clientSecret={{gmail.client.secret}}')
> .log('${body}') {code}
>
> What do you think?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18326) google-mail-stream
Jérôme GARCIA created CAMEL-18326:
-
Summary: google-mail-stream
Key: CAMEL-18326
URL: https://issues.apache.org/jira/browse/CAMEL-18326
Project: Camel
Issue Type: Improvement
Components: camel-google-mail-stream
Affects Versions: 3.16.0
Reporter: Jérôme GARCIA
Hello,
In *google-mail-stream* component, the mail body is displayed as plain text and
is not easy to manipulate the data.
The component should add the possibility to change this behavior and displayed
a standardize object (JSON or other).
{code:java}
// code placeholder
from('google-mail-stream:index?' +
'applicationName={{camel-app-name}}&' +
'accessToken={{gmail.client.access.token}}&' +
'refreshToken={{gmail.client.access.refresh.token}}&' +
'clientId={{gmail.client.id}}&' +
'query=is:unread&' +
'clientSecret={{gmail.client.secret}}')
.log('${body}') {code}
What do you think?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18294) upgrade to spring boot 2.7.2
[ https://issues.apache.org/jira/browse/CAMEL-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572994#comment-17572994 ] Federico Mariani commented on CAMEL-18294: -- I'm sorry I lost your comment! but it seems like you have already cherry-picked the changes: [https://github.com/apache/camel-spring-boot/commit/30f9372a0b3403cb97bf8e86a6435bc8bd5d3f95] [https://github.com/apache/camel/commit/3e19071aab18efab0e1de15eacdcfbc2eb931c50] next time I'll update the current LTS too > upgrade to spring boot 2.7.2 > > > Key: CAMEL-18294 > URL: https://issues.apache.org/jira/browse/CAMEL-18294 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Affects Versions: 3.18.0 >Reporter: Federico Mariani >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > https://github.com/spring-projects/spring-boot/releases/tag/v2.7.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18325) camel-hyperledger-aries - Add support for /credentials endpoint
[ https://issues.apache.org/jira/browse/CAMEL-18325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572978#comment-17572978 ] Thomas Diesler commented on CAMEL-18325: PR: https://github.com/apache/camel/pull/8078 > camel-hyperledger-aries - Add support for /credentials endpoint > --- > > Key: CAMEL-18325 > URL: https://issues.apache.org/jira/browse/CAMEL-18325 > Project: Camel > Issue Type: Improvement >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-15566) Create a AWS Cloudtrail component
[ https://issues.apache.org/jira/browse/CAMEL-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-15566. -- Resolution: Fixed > Create a AWS Cloudtrail component > - > > Key: CAMEL-15566 > URL: https://issues.apache.org/jira/browse/CAMEL-15566 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-15566) Create a AWS Cloudtrail component
[ https://issues.apache.org/jira/browse/CAMEL-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572976#comment-17572976 ] Andrea Cosentino commented on CAMEL-15566: -- Initial implementation pushed. > Create a AWS Cloudtrail component > - > > Key: CAMEL-15566 > URL: https://issues.apache.org/jira/browse/CAMEL-15566 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (CAMEL-17675) Rest DSL - Removed inlined routes
[ https://issues.apache.org/jira/browse/CAMEL-17675 ] Chris deleted comment on CAMEL-17675: --- was (Author: cwild): With this change, how would you set the response code and message? Before it we could just set it in the route via the header _Exchange.HTTP_RESPONSE_CODE_ and the message body, but this doesn't work anymore. Furthermore it seems when an Exception is thrown in the called route the api will still return 200. How can we propage errors to the caller? > Rest DSL - Removed inlined routes > - > > Key: CAMEL-17675 > URL: https://issues.apache.org/jira/browse/CAMEL-17675 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > > In the Rest DSL you can inline a route but that was a mistake. > I made a mistake when rest-dsl was created that you could embed a route > inside it > that is bad, instead its better as it was a facade to a route which you link > via direct. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18325) camel-hyperledger-aries - Add support for /credentials endpoint
Thomas Diesler created CAMEL-18325: -- Summary: camel-hyperledger-aries - Add support for /credentials endpoint Key: CAMEL-18325 URL: https://issues.apache.org/jira/browse/CAMEL-18325 Project: Camel Issue Type: Improvement Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18322) Camel-Jbang export copy properties erroneously
[
https://issues.apache.org/jira/browse/CAMEL-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18322:
Fix Version/s: 3.18.1
3.19.0
> Camel-Jbang export copy properties erroneously
> --
>
> Key: CAMEL-18322
> URL: https://issues.apache.org/jira/browse/CAMEL-18322
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.18.0
>Reporter: Marat Gubaidullin
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> jbang -Dcamel.jbang.version=3.18.0 camel@apache/camel export
> for application.properties
> {code:java}
> camel.jbang.project-id=use-case-1
> camel.jbang.project-name=use-case-1
> camel.jbang.project-description=Salesforce to ServiceNow
> camel.jbang.gav=org.camel.karavan.demo:use-case-1:1.0.0
> camel.jbang.runtime=quarkus
> camel.jbang.quarkusVersion=2.11.1.Final
> camel.jbang.dependencies=mvn:io.quarkus:quarkus-container-image-jib,mvn:org.apache.camel.quarkus:camel-quarkus-microprofile-health,mvn:io.quarkus:quarkus-openshift,mvn:org.apache.camel:camel-salesforce:3.18.0
> camel.health.enabled=true
> camel.health.exposure-level=full
> quarkus.kubernetes-client.trust-certs=true
> quarkus.container-image.builder=jib
> quarkus.container-image.group=karavan
> quarkus.container-image.name=use-case-1
> quarkus.openshift.route.expose=false
> quarkus.openshift.part-of=use-case-1
> quarkus.openshift.replicas=1
> {code}
> creates quarkus project with the following application.properties
> {code:java}
> camel.health.enabled=true
> camel.health.exposureLevel=full
> quarkus.kubernetesClient.trustCerts=true
> quarkus.containerImage.builder=jib
> quarkus.containerImage.group=karavan
> quarkus.containerImage.name=use-case-1
> quarkus.openshift.route.expose=false
> quarkus.openshift.partOf=use-case-1
> quarkus.openshift.replicas=1
> camel.main.sourceLocationEnabled=true
> camel.main.tracing=false
> {code}
> Some properties are missing and some of them converted from kebab based to
> camel based and this not supported by Quarkus
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-18322) Camel-Jbang export copy properties erroneously
[
https://issues.apache.org/jira/browse/CAMEL-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-18322:
---
Assignee: Claus Ibsen
> Camel-Jbang export copy properties erroneously
> --
>
> Key: CAMEL-18322
> URL: https://issues.apache.org/jira/browse/CAMEL-18322
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.18.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> jbang -Dcamel.jbang.version=3.18.0 camel@apache/camel export
> for application.properties
> {code:java}
> camel.jbang.project-id=use-case-1
> camel.jbang.project-name=use-case-1
> camel.jbang.project-description=Salesforce to ServiceNow
> camel.jbang.gav=org.camel.karavan.demo:use-case-1:1.0.0
> camel.jbang.runtime=quarkus
> camel.jbang.quarkusVersion=2.11.1.Final
> camel.jbang.dependencies=mvn:io.quarkus:quarkus-container-image-jib,mvn:org.apache.camel.quarkus:camel-quarkus-microprofile-health,mvn:io.quarkus:quarkus-openshift,mvn:org.apache.camel:camel-salesforce:3.18.0
> camel.health.enabled=true
> camel.health.exposure-level=full
> quarkus.kubernetes-client.trust-certs=true
> quarkus.container-image.builder=jib
> quarkus.container-image.group=karavan
> quarkus.container-image.name=use-case-1
> quarkus.openshift.route.expose=false
> quarkus.openshift.part-of=use-case-1
> quarkus.openshift.replicas=1
> {code}
> creates quarkus project with the following application.properties
> {code:java}
> camel.health.enabled=true
> camel.health.exposureLevel=full
> quarkus.kubernetesClient.trustCerts=true
> quarkus.containerImage.builder=jib
> quarkus.containerImage.group=karavan
> quarkus.containerImage.name=use-case-1
> quarkus.openshift.route.expose=false
> quarkus.openshift.partOf=use-case-1
> quarkus.openshift.replicas=1
> camel.main.sourceLocationEnabled=true
> camel.main.tracing=false
> {code}
> Some properties are missing and some of them converted from kebab based to
> camel based and this not supported by Quarkus
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18324) camel-core - Exception during preparing exchange task can block thread
[ https://issues.apache.org/jira/browse/CAMEL-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18324. - Resolution: Fixed > camel-core - Exception during preparing exchange task can block thread > -- > > Key: CAMEL-18324 > URL: https://issues.apache.org/jira/browse/CAMEL-18324 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.4, 3.18.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.14.5, 3.18.1, 3.19.0 > > > Reported in CAMEL-18270 but this is a general problem in the routing engine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18264) Camel SFTP: Cannot configure JSch client to use ssh-dss key
[
https://issues.apache.org/jira/browse/CAMEL-18264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572863#comment-17572863
]
Konrad Stachera commented on CAMEL-18264:
-
I'll open PR for this today
> Camel SFTP: Cannot configure JSch client to use ssh-dss key
> ---
>
> Key: CAMEL-18264
> URL: https://issues.apache.org/jira/browse/CAMEL-18264
> Project: Camel
> Issue Type: Improvement
> Components: camel-sftp
> Environment: Tested with Apache Camel 3.17.0 and 3.18.0
>Reporter: Konrad Stachera
>Priority: Major
> Fix For: 3.19.0
>
> Attachments: image-2022-07-11-10-34-58-099.png
>
>
> When server requires ssh-dss host key algorithm it is not possible to
> configure sFTP camel component to use such key type, therefore connecting
> fails with "com.jcraft.jsch.JSchException: Algorithm negotiation fail".
> When these two properties are added in debug mode:
> {code:java}
> session.setConfig("server_host_key", session.getConfig("server_host_key") +
> ",ssh-dss")
> session.setConfig("PubkeyAcceptedAlgorithms",
> session.getConfig("PubkeyAcceptedAlgorithms") + ",ssh-dss") {code}
> in SftpOperations class:
> !image-2022-07-11-10-34-58-099.png!
> the connection is established successfully.
> It should be possible to configure "server_host_key" and
> "PubkeyAcceptedAlgorithms" in camel sFTP component.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18270) IMAP skipFailedMessage=true, but route blocked if mail is moved while download
[
https://issues.apache.org/jira/browse/CAMEL-18270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18270:
Fix Version/s: 3.14.5
> IMAP skipFailedMessage=true, but route blocked if mail is moved while download
> --
>
> Key: CAMEL-18270
> URL: https://issues.apache.org/jira/browse/CAMEL-18270
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.18.0
>Reporter: Florian Fiby
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.14.5, 3.18.1, 3.19.0
>
>
>
> Our imap mail route on the production system gets blocked when someone or an
> other systems moves / deletes an email from the inbox, while the camel mail
> route is loading the mail. As we do not have full control on the mailboxes we
> enabled skipFailedMessage but the issue remains.
> The following exception is written is the log, but the mail consumer is
> blocked. The issue can only be resolved by a restart of the service.
> {code:java}
> 2022-07-14 09:17:28.714 WARN 5465 --- [fice365.com:993]
> o.a.c.i.engine.DefaultReactiveExecutor : Error executing reactive work due
> to Error accessing headers due to: Cannot load header. This exception is
> ignored.
> org.apache.camel.RuntimeCamelException: Error accessing headers due to:
> Cannot load header
> at
> org.apache.camel.component.mail.MailMessage.populateInitialHeaders(MailMessage.java:107)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.DefaultMessage.createHeaders(DefaultMessage.java:331)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.DefaultMessage.hasHeaders(DefaultMessage.java:305)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.AbstractExchange.copy(AbstractExchange.java:140)
> ~[camel-support-3.18.0.jar:3.18.0]
> at org.apache.camel.support.DefaultExchange.copy(DefaultExchange.java:27)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ExchangeHelper.createCopy(ExchangeHelper.java:322)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.defensiveCopyExchangeIfNeeded(RedeliveryErrorHandler.java:304)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.prepare(RedeliveryErrorHandler.java:680)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.PrototypeTaskFactory.acquire(PrototypeTaskFactory.java:29)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:210)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:109)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:189)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:61)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:184)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:83)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:41)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.processExchange(MailConsumer.java:451)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.processBatch(MailConsumer.java:260)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:165)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:202)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:116)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> ~[na:na]
> at
> java.base/java.util.concurrent.FutureTask.runAndReset$$$capture(FutureTask.java:305)
> ~[na:na]
> at
[jira] [Created] (CAMEL-18324) camel-core - Exception during preparing exchange task can block thread
Claus Ibsen created CAMEL-18324: --- Summary: camel-core - Exception during preparing exchange task can block thread Key: CAMEL-18324 URL: https://issues.apache.org/jira/browse/CAMEL-18324 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 3.18.0, 3.14.4 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.14.5, 3.18.1, 3.19.0 Reported in CAMEL-18270 but this is a general problem in the routing engine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18270) IMAP skipFailedMessage=true, but route blocked if mail is moved while download
[
https://issues.apache.org/jira/browse/CAMEL-18270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18270.
-
Resolution: Fixed
Thanks this will be fixed by the linked ticket
> IMAP skipFailedMessage=true, but route blocked if mail is moved while download
> --
>
> Key: CAMEL-18270
> URL: https://issues.apache.org/jira/browse/CAMEL-18270
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.18.0
>Reporter: Florian Fiby
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
>
> Our imap mail route on the production system gets blocked when someone or an
> other systems moves / deletes an email from the inbox, while the camel mail
> route is loading the mail. As we do not have full control on the mailboxes we
> enabled skipFailedMessage but the issue remains.
> The following exception is written is the log, but the mail consumer is
> blocked. The issue can only be resolved by a restart of the service.
> {code:java}
> 2022-07-14 09:17:28.714 WARN 5465 --- [fice365.com:993]
> o.a.c.i.engine.DefaultReactiveExecutor : Error executing reactive work due
> to Error accessing headers due to: Cannot load header. This exception is
> ignored.
> org.apache.camel.RuntimeCamelException: Error accessing headers due to:
> Cannot load header
> at
> org.apache.camel.component.mail.MailMessage.populateInitialHeaders(MailMessage.java:107)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.DefaultMessage.createHeaders(DefaultMessage.java:331)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.DefaultMessage.hasHeaders(DefaultMessage.java:305)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.AbstractExchange.copy(AbstractExchange.java:140)
> ~[camel-support-3.18.0.jar:3.18.0]
> at org.apache.camel.support.DefaultExchange.copy(DefaultExchange.java:27)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ExchangeHelper.createCopy(ExchangeHelper.java:322)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.defensiveCopyExchangeIfNeeded(RedeliveryErrorHandler.java:304)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.prepare(RedeliveryErrorHandler.java:680)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.PrototypeTaskFactory.acquire(PrototypeTaskFactory.java:29)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:210)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:109)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:189)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:61)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:184)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:83)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:41)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.processExchange(MailConsumer.java:451)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.processBatch(MailConsumer.java:260)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:165)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:202)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:116)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> ~[na:na]
> at
>
[jira] [Updated] (CAMEL-18323) camel-jpa: introduce a transaction strategy
[ https://issues.apache.org/jira/browse/CAMEL-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Feng updated CAMEL-18323: --- Fix Version/s: 3.18.1 > camel-jpa: introduce a transaction strategy > --- > > Key: CAMEL-18323 > URL: https://issues.apache.org/jira/browse/CAMEL-18323 > Project: Camel > Issue Type: Improvement > Components: camel-jpa >Reporter: Zheng Feng >Assignee: Zheng Feng >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > Currently camel-jpa depends on spring transaction template to run the > operations in the transaction, I'd like to introduce a new option with > TransactionStrategy which could be used to replace the spring transaction > template. And for example, camel-quarkus could leverage on TX APIs provided > by quarkus-narayana-jta -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18323) camel-jpa: introduce a transaction strategy
[ https://issues.apache.org/jira/browse/CAMEL-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Feng resolved CAMEL-18323. Resolution: Fixed > camel-jpa: introduce a transaction strategy > --- > > Key: CAMEL-18323 > URL: https://issues.apache.org/jira/browse/CAMEL-18323 > Project: Camel > Issue Type: Improvement > Components: camel-jpa >Reporter: Zheng Feng >Assignee: Zheng Feng >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > Currently camel-jpa depends on spring transaction template to run the > operations in the transaction, I'd like to introduce a new option with > TransactionStrategy which could be used to replace the spring transaction > template. And for example, camel-quarkus could leverage on TX APIs provided > by quarkus-narayana-jta -- This message was sent by Atlassian Jira (v8.20.10#820010)
