[jira] [Commented] (CAMEL-13565) Why TracingInterceptor has been deprecated?
[ https://issues.apache.org/jira/browse/CAMEL-13565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847958#comment-16847958 ] Andrea Cosentino commented on CAMEL-13565: -- This kind of question should be done on dev mailing list. This is for tracking issues. > Why TracingInterceptor has been deprecated? > --- > > Key: CAMEL-13565 > URL: https://issues.apache.org/jira/browse/CAMEL-13565 > Project: Camel > Issue Type: Wish > Components: came-core >Reporter: Pedro Henrique Calais Guerra >Priority: Major > > [https://camel.apache.org/tracer.html] > "Implementing custom tracing via TracingInterceptor has been deprecated." > Being able to customize and personalize the tracing logs seemed like a very > useful capability. Can anyone explain this decision? Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13483) File Component: Add option to fail startup when not having read permission on folder
[ https://issues.apache.org/jira/browse/CAMEL-13483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847850#comment-16847850 ] Roberto Flores commented on CAMEL-13483: Hi. I have just sent a PR for this issue. I added a new option called startingDirectoryMustHaveAccess similar to startingDirectoryMustExist. It checks that the directory has read and write permissions. Could you please give it a look. Best, Roberto. > File Component: Add option to fail startup when not having read permission on > folder > > > Key: CAMEL-13483 > URL: https://issues.apache.org/jira/browse/CAMEL-13483 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.22.4 >Reporter: Chris >Priority: Major > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > When starting a file consumer you configure a folder to poll. > When the camel context does not have read access on the folder, there is no > error (or even warning), that route just starts. > But when saving files into the folder, they are not picked up and there is no > further message. > This issue was raised on stackoverflow: > [https://stackoverflow.com/questions/55920217/camel-file-consumer-when-folder-is-not-accessible] > > Ideally, the file consumer would check at startup if it has access to the > folder (we should propably check for write access here, but read access could > also be enough?) > If the component (/context) does not have the required access to the folder, > it should throw the error and exit the context (so it isn't started in a > failure state). > This option should be disabled by default. > Also we should think about a way to configure the behavior: > 1. For what permission should the consumer check (read / read-write) > 2. What should happen when the permission is not given? (just an error / > error + stop route / error + stop context) > As always, we should make this configurable via a custom bean. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13483) File Component: Add option to fail startup when not having read permission on folder
[ https://issues.apache.org/jira/browse/CAMEL-13483?focusedWorklogId=248241=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-248241 ] ASF GitHub Bot logged work on CAMEL-13483: -- Author: ASF GitHub Bot Created on: 24/May/19 19:33 Start Date: 24/May/19 19:33 Worklog Time Spent: 10m Work Description: betoflowv93 commented on pull request #2947: CAMEL-13483 File Component: Add option to fail startup when not having read permission on folder URL: https://github.com/apache/camel/pull/2947 Changes: -add option startingDirectoryMustHaveAccess (checks read and write permission) -add a new test Your feedback would be appreciated :) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 248241) Time Spent: 10m Remaining Estimate: 0h > File Component: Add option to fail startup when not having read permission on > folder > > > Key: CAMEL-13483 > URL: https://issues.apache.org/jira/browse/CAMEL-13483 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.22.4 >Reporter: Chris >Priority: Major > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > When starting a file consumer you configure a folder to poll. > When the camel context does not have read access on the folder, there is no > error (or even warning), that route just starts. > But when saving files into the folder, they are not picked up and there is no > further message. > This issue was raised on stackoverflow: > [https://stackoverflow.com/questions/55920217/camel-file-consumer-when-folder-is-not-accessible] > > Ideally, the file consumer would check at startup if it has access to the > folder (we should propably check for write access here, but read access could > also be enough?) > If the component (/context) does not have the required access to the folder, > it should throw the error and exit the context (so it isn't started in a > failure state). > This option should be disabled by default. > Also we should think about a way to configure the behavior: > 1. For what permission should the consumer check (read / read-write) > 2. What should happen when the permission is not given? (just an error / > error + stop route / error + stop context) > As always, we should make this configurable via a custom bean. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13577) Salesforce component 403::unknown client error
Senthil created CAMEL-13577: --- Summary: Salesforce component 403::unknown client error Key: CAMEL-13577 URL: https://issues.apache.org/jira/browse/CAMEL-13577 Project: Camel Issue Type: Bug Components: camel-salesforce Affects Versions: 2.23.2 Reporter: Senthil Attachments: Salesforce-Error.txt We are using camel-salesforce components to subscribe Salesforce Platform events. We are using the springboot configurations. Initial startup it is connecting to all the platform event routes, after a while ( 3 ro 4 hours), it is failed to reconnect and throwing 403::Unknown client. We made some changes based on the thread https://issues.apache.org/jira/browse/CAMEL-12484 but still having the same issues. We tried disabling the Salesforce in-app notification and httpClientProperties.idletimeout options. but still having same issue. Could you please help resolve this issue. I have attached our logs for your reference here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13402) Update to Californium 2.0.x and support DTLS
[ https://issues.apache.org/jira/browse/CAMEL-13402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-13402: Fix Version/s: 2.25.0 > Update to Californium 2.0.x and support DTLS > > > Key: CAMEL-13402 > URL: https://issues.apache.org/jira/browse/CAMEL-13402 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 3.0.0-M3, 2.25.0 > > > This task is to update to Californium 2.0.x and support DTLS in the > camel-coap component. Currently we only support plain UDP and not UDP / TLS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13565) Why TracingInterceptor has been deprecated?
[ https://issues.apache.org/jira/browse/CAMEL-13565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pedro Henrique Calais Guerra updated CAMEL-13565: - Description: [https://camel.apache.org/tracer.html] "Implementing custom tracing via TracingInterceptor has been deprecated." Being able to customize and personalize the tracing logs seemed like a very useful capability. Can anyone explain this decision? Thanks! was: [https://camel.apache.org/tracer.html] "Implementing custom tracing via TracingInterceptor has been deprecated." Being able to customize and persoanlize the tracing logs seemed like a very useful capability. Can anyone explain this decision? Thanks! > Why TracingInterceptor has been deprecated? > --- > > Key: CAMEL-13565 > URL: https://issues.apache.org/jira/browse/CAMEL-13565 > Project: Camel > Issue Type: Wish > Components: came-core >Reporter: Pedro Henrique Calais Guerra >Priority: Major > > [https://camel.apache.org/tracer.html] > "Implementing custom tracing via TracingInterceptor has been deprecated." > Being able to customize and personalize the tracing logs seemed like a very > useful capability. Can anyone explain this decision? Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13576) avoid adding cxf message context map into camel exchange
[ https://issues.apache.org/jira/browse/CAMEL-13576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13576. -- Resolution: Fixed Fix Version/s: 2.25.0 2.24.1 2.22.5 2.23.3 3.0.0 > avoid adding cxf message context map into camel exchange > > > Key: CAMEL-13576 > URL: https://issues.apache.org/jira/browse/CAMEL-13576 > Project: Camel > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.22.5, 2.24.1, 2.25.0 > > > which can easily cause ConcurrentModificationException under high load -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13576) avoid adding cxf message context map into camel exchange
[ https://issues.apache.org/jira/browse/CAMEL-13576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13576: Assignee: Freeman Fang > avoid adding cxf message context map into camel exchange > > > Key: CAMEL-13576 > URL: https://issues.apache.org/jira/browse/CAMEL-13576 > Project: Camel > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > which can easily cause ConcurrentModificationException under high load -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13576) avoid adding cxf message context map into camel exchange
Freeman Fang created CAMEL-13576: Summary: avoid adding cxf message context map into camel exchange Key: CAMEL-13576 URL: https://issues.apache.org/jira/browse/CAMEL-13576 Project: Camel Issue Type: Bug Reporter: Freeman Fang which can easily cause ConcurrentModificationException under high load -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13560) Mail component is not reading attachments
[
https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamil updated CAMEL-13560:
--
Description:
I have such route (taken from
[documentation|https://camel.apache.org/mail.html]):
{code:java}
@Override
public void configure() throws Exception {
from("imaps://login@host:993?password=pass=true")
.process(new Processor() {
@Override
public void process(final Exchange exchange) throws Exception {
final Message in = exchange.getIn();
Map attachments = in.getAttachments();
System.out.println("ATTACHMENTS: "+attachments.size());
}
});
}
{code}
When I sent email with images.jpg attachment, email is read, but attachment Map
is empty.
Debug shows:
{code:java}
DEBUG: setDebug: JavaMail version 1.6.1
DEBUG: getProvider() returning
javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
DEBUG IMAPS: mail.imap.fetchsize: 16384
DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
DEBUG IMAPS: mail.imap.appendbuffersize: -1
DEBUG IMAPS: mail.imap.minidletime: 10
DEBUG IMAPS: closeFoldersOnStoreFailure
DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
* OK IMAP4 ready
A0 CAPABILITY
* CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
XAOL-MOVE AUTH=PLAIN
A0 OK completed
DEBUG IMAPS: AUTH: PLAIN
DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
password=
DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
A2 CAPABILITY
* CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
XAOL-MOVE
A2 OK CAPABILITY completed
A3 LIST "" INBOX
* LIST (\Noinferiors) "/" "INBOX"
A3 OK List completed
DEBUG IMAPS: connection available -- size: 1
A4 SELECT INBOX
* 13 EXISTS
* 0 RECENT
* OK [UNSEEN 13] UIDs valid
* OK [UIDVALIDITY 1549376878] UIDs valid
* OK [UIDNEXT 36] Predicted next UID
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
* OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
A4 OK [READ-WRITE] SELECT completed
A5 SEARCH UNSEEN 1:13
* SEARCH 13
A5 OK Search completed
A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
* 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
)
A6 OK Fetch completed
A7 FETCH 13 (FLAGS)
* 13 FETCH (FLAGS ())
A7 OK Fetch completed
A8 FETCH 13 (BODYSTRUCTURE)
* 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
"flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name" "images.jpg")
NIL NIL "base64" 16794 NIL ("attachment" ("filename" "images.jpg")) NIL)
"mixed" ("boundary" "53A9AD932142735A4433B153") NIL NIL))
A8 OK Fetch completed
A9 FETCH 13 (BODY.PEEK[HEADER])
* 13 FETCH (BODY[HEADER] {3286}
Return-Path:
Delivered-To: xxx...@xx.com
Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
16:14:00 +0200
Received: from mail-XXX.google.com ([209.85.167.54])
(envelope-sender )
by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
SMTP
for ; 22 May 2019 16:14:00 +0200
Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=XXX.gappssmtp.com; s=XXX;
h=to:from:subject:message-id:date:user-agent:mime-version
:content-language;
bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:to:from:subject:message-id:date:user-agent
:mime-version:content-language;
bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
b=F1EsLfk3qaiJXiNX0XXX==
X-Gm-Message-State: APXX=
X-Google-Smtp-Source: APXvXWYQ==
X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
Wed, 22 May 2019 07:13:59 -0700 (PDT)
Return-Path:
Received: from [XX] (host-XX.com. [XX])
by smtp.gmail.com with ESMTPSA id
for
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 22 May 2019 07:13:59 -0700 (PDT)
To: xxx...@xx.com
From: =?UTF-8?Q?XXX=c5=9bXX?=
Subject: Test attachment
Message-ID: <175c8cc9-xx...@xx.com>
Date: Wed, 22 May 2019 16:13:58 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101
Thunderbird/60.6.1
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="53A9AD932142735A4433B153"
Content-Language: pl
X-WP-DKIM-Status: good (id: XX.com.gappssmtp.c)
X-WP-MailID: 3f705f51c9402ad04c3cda34f72497b2
X-WP-SPAM: NO (U9) 0W0001A [0QMk]
[jira] [Commented] (CAMEL-13560) Imaps is not reading attachments
[
https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847630#comment-16847630
]
Kamil commented on CAMEL-13560:
---
[~acosentino], yes, I've checked:
* imap on 143
* imaps on 993
* pop3 on 110
* pop3s on 995
non of them returned attachmets
> Imaps is not reading attachments
>
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
> Wed, 22 May 2019 07:13:59 -0700 (PDT)
> Return-Path:
>
[jira] [Updated] (CAMEL-13570) Camel AWS-SQS: Make the autocreation of the queue configurable
[ https://issues.apache.org/jira/browse/CAMEL-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13570: - Fix Version/s: 3.0.0-M3 3.0.0 > Camel AWS-SQS: Make the autocreation of the queue configurable > -- > > Key: CAMEL-13570 > URL: https://issues.apache.org/jira/browse/CAMEL-13570 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > > We can leave the behavior as the older, but make it possible to avoid the > autocreation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13570) Camel AWS-SQS: Make the autocreation of the queue configurable
[ https://issues.apache.org/jira/browse/CAMEL-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13570. -- Resolution: Fixed > Camel AWS-SQS: Make the autocreation of the queue configurable > -- > > Key: CAMEL-13570 > URL: https://issues.apache.org/jira/browse/CAMEL-13570 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > > We can leave the behavior as the older, but make it possible to avoid the > autocreation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13575) The RedeliveryPolicyDefinition has 2 fields that are enums instead of strings and thus can not be used with placeholders
Guillaume Nodet created CAMEL-13575: --- Summary: The RedeliveryPolicyDefinition has 2 fields that are enums instead of strings and thus can not be used with placeholders Key: CAMEL-13575 URL: https://issues.apache.org/jira/browse/CAMEL-13575 Project: Camel Issue Type: Improvement Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 3.0.0, 3.0.0.M4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13560) Imaps is not reading attachments
[
https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847527#comment-16847527
]
Andrea Cosentino commented on CAMEL-13560:
--
Did you try with the other available protocol in the component?
> Imaps is not reading attachments
>
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
> Wed, 22 May 2019 07:13:59 -0700 (PDT)
> Return-Path:
> Received: from [XX] (host-XX.com.
[jira] [Commented] (CAMEL-13574) marshalling data to csv with header
[ https://issues.apache.org/jira/browse/CAMEL-13574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847528#comment-16847528 ] Claus Ibsen commented on CAMEL-13574: - See the docs, there are options to control headers. So go try this out first https://github.com/apache/camel/blob/master/components/camel-csv/src/main/docs/csv-dataformat.adoc > marshalling data to csv with header > --- > > Key: CAMEL-13574 > URL: https://issues.apache.org/jira/browse/CAMEL-13574 > Project: Camel > Issue Type: Wish > Components: camel-csv >Affects Versions: 2.21.5 >Reporter: Matteo Redaelli >Priority: Minor > > I would like to export some database tables to csv files with the header > using database column names. > > But using camel-jdbc and camel-csv I haven't found a solution... > > It seems you have to manually concatenate the he header and the rows ... > It would be nice to have an option to switch header on/off when marshalling > to csv ... > > See > [https://stackoverflow.com/questions/31865928/output-csv-column-headers-in-apache-camel] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13574) marshalling data to csv with header
[ https://issues.apache.org/jira/browse/CAMEL-13574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13574: Issue Type: Wish (was: Bug) > marshalling data to csv with header > --- > > Key: CAMEL-13574 > URL: https://issues.apache.org/jira/browse/CAMEL-13574 > Project: Camel > Issue Type: Wish > Components: camel-csv >Affects Versions: 2.21.5 >Reporter: Matteo Redaelli >Priority: Major > > I would like to export some database tables to csv files with the header > using database column names. > > But using camel-jdbc and camel-csv I haven't found a solution... > > It seems you have to manually concatenate the he header and the rows ... > It would be nice to have an option to switch header on/off when marshalling > to csv ... > > See > [https://stackoverflow.com/questions/31865928/output-csv-column-headers-in-apache-camel] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13574) marshalling data to csv with header
[ https://issues.apache.org/jira/browse/CAMEL-13574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13574: Priority: Minor (was: Major) > marshalling data to csv with header > --- > > Key: CAMEL-13574 > URL: https://issues.apache.org/jira/browse/CAMEL-13574 > Project: Camel > Issue Type: Wish > Components: camel-csv >Affects Versions: 2.21.5 >Reporter: Matteo Redaelli >Priority: Minor > > I would like to export some database tables to csv files with the header > using database column names. > > But using camel-jdbc and camel-csv I haven't found a solution... > > It seems you have to manually concatenate the he header and the rows ... > It would be nice to have an option to switch header on/off when marshalling > to csv ... > > See > [https://stackoverflow.com/questions/31865928/output-csv-column-headers-in-apache-camel] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13560) Imaps is not reading attachments
[
https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847525#comment-16847525
]
Kamil commented on CAMEL-13560:
---
[~davsclaus] - I'm not asking for "prioritzed help". It just seemed like rather
serious issue.
I've tested different email and they're the same.
I'm eager to help. I can share my email account together with invalid emails.
Please email me at
https://onetimesecret.com/secret/aeh0sz191vpi7vrtt4xfez8g9omeouf
> Imaps is not reading attachments
>
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
>
[jira] [Commented] (CAMEL-13560) Imaps is not reading attachments
[
https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847512#comment-16847512
]
Claus Ibsen commented on CAMEL-13560:
-
It works for many others, its hard to reproduce as mail servers and whatnot can
be different, and I suggest you investigate yourself on your system, by
debugging the camel-mail and see if you can spot a problem.
If you want prioritzed help then ask the commercial vendors
> Imaps is not reading attachments
>
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source:
[jira] [Comment Edited] (CAMEL-13560) Imaps is not reading attachments
[
https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847508#comment-16847508
]
Kamil edited comment on CAMEL-13560 at 5/24/19 12:27 PM:
-
[~acosentino] thanks for clarification. Could you please point me to the proper
component/scheme which can download email with attachments (without deleting
the email from inbox)?
was (Author: eximius):
[~acosentino] thanks for clarification. Could you please point me to the proper
component/scheme which can download email with attachments?
> Imaps is not reading attachments
>
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
>
[jira] [Commented] (CAMEL-13560) Imaps is not reading attachments
[
https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847508#comment-16847508
]
Kamil commented on CAMEL-13560:
---
[~acosentino] thanks for clarification. Could you please point me to the proper
component/scheme which can download email with attachments?
> Imaps is not reading attachments
>
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
> Wed, 22 May 2019 07:13:59 -0700 (PDT)
>
[jira] [Comment Edited] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847442#comment-16847442
]
Claus Ibsen edited comment on CAMEL-13557 at 5/24/19 12:26 PM:
---
Okay big work has been merged on master.
There are two nice things still to do
- support for list/map in keys
- auto configure singleton beans from registry on camel components on their
nested properties (eg amazon s3 client etc) *DONE*
was (Author: davsclaus):
Okay big work has been merged on master.
There are two nice things still to do
- support for list/map in keys
- auto configure singleton beans from registry on camel components on their
nested properties (eg amazon s3 client etc)
> Support for nested properties binding
> -
>
> Key: CAMEL-13557
> URL: https://issues.apache.org/jira/browse/CAMEL-13557
> Project: Camel
> Issue Type: New Feature
> Components: came-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>
> As today properties binding does not work for nested objects so assuming I
> have a class like:
> {code:java}
> class MyComponent {
>
> public void setFoo(String foo) {
> this.foo = foo;
> }
> public String getFoo() {
> return foo;
> }
> public void setConfiguration(Configuration conf) {
> this.conf = conf;
> }
> public Configuration getConfiguration() {
> return conf;
> }
> static class Configuration {
>
> public void setBar(String bar) {
> this.bar = bar
> }
> public String getBar() {
> return bar
> }
> }
> }
> {code}
> And a set of properties like:
> {code}
> myComponent.foo = "foo"
> myComponent.conf.bar = "bar"
> {code}
> Then only MyComponent.foo will be set but it would be nice if the binding
> framework could navigate the property using dot notation and set any
> dependent object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13574) marshalling data to csv with header
Matteo Redaelli created CAMEL-13574: --- Summary: marshalling data to csv with header Key: CAMEL-13574 URL: https://issues.apache.org/jira/browse/CAMEL-13574 Project: Camel Issue Type: Bug Components: camel-csv Affects Versions: 2.21.5 Reporter: Matteo Redaelli I would like to export some database tables to csv files with the header using database column names. But using camel-jdbc and camel-csv I haven't found a solution... It seems you have to manually concatenate the he header and the rows ... It would be nice to have an option to switch header on/off when marshalling to csv ... See [https://stackoverflow.com/questions/31865928/output-csv-column-headers-in-apache-camel] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13560) Imaps is not reading attachments
[
https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847497#comment-16847497
]
Andrea Cosentino commented on CAMEL-13560:
--
You have other possibilities with other components and other scheme. That's why
is a minor.
> Imaps is not reading attachments
>
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
> Wed, 22 May 2019 07:13:59 -0700 (PDT)
> Return-Path:
> Received: from
[jira] [Updated] (CAMEL-13573) Parquet Dataformat: supporting parquet files in marshal / unmarshal
[ https://issues.apache.org/jira/browse/CAMEL-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13573: - Summary: Parquet Dataformat: supporting parquet files in marshal / unmarshal (was: supporting parquet files in marshal / unmarshal) > Parquet Dataformat: supporting parquet files in marshal / unmarshal > --- > > Key: CAMEL-13573 > URL: https://issues.apache.org/jira/browse/CAMEL-13573 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Matteo Redaelli >Priority: Minor > > It would be useweful to read / store data (marshal / unmarshal) in parquet > format ([https://parquet.apache.org/]). > It is widely used in bigdata projects / datalakes > > I did not found any info about it in the documentation... > > Thanks > Matteo -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13573) Parquet Dataformat: supporting parquet files in marshal / unmarshal
[ https://issues.apache.org/jira/browse/CAMEL-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13573: - Fix Version/s: 3.0.0 > Parquet Dataformat: supporting parquet files in marshal / unmarshal > --- > > Key: CAMEL-13573 > URL: https://issues.apache.org/jira/browse/CAMEL-13573 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Matteo Redaelli >Priority: Minor > Fix For: 3.0.0 > > > It would be useweful to read / store data (marshal / unmarshal) in parquet > format ([https://parquet.apache.org/]). > It is widely used in bigdata projects / datalakes > > I did not found any info about it in the documentation... > > Thanks > Matteo -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13573) supporting parquet files in marshal / unmarshal
Matteo Redaelli created CAMEL-13573: --- Summary: supporting parquet files in marshal / unmarshal Key: CAMEL-13573 URL: https://issues.apache.org/jira/browse/CAMEL-13573 Project: Camel Issue Type: New Feature Components: camel-core Reporter: Matteo Redaelli It would be useweful to read / store data (marshal / unmarshal) in parquet format ([https://parquet.apache.org/]). It is widely used in bigdata projects / datalakes I did not found any info about it in the documentation... Thanks Matteo -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13560) Imaps is not reading attachments
[
https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847477#comment-16847477
]
Kamil commented on CAMEL-13560:
---
[~cib...@e-ma.net], not being able to fetch attachments is rather serious
issue...
> Imaps is not reading attachments
>
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
> Wed, 22 May 2019 07:13:59 -0700 (PDT)
> Return-Path:
> Received: from [XX] (host-XX.com.
[jira] [Commented] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847442#comment-16847442
]
Claus Ibsen commented on CAMEL-13557:
-
Okay big work has been merged on master.
There are two nice things still to do
- support for list/map in keys
- auto configure singleton beans from registry on camel components on their
nested properties (eg amazon s3 client etc)
> Support for nested properties binding
> -
>
> Key: CAMEL-13557
> URL: https://issues.apache.org/jira/browse/CAMEL-13557
> Project: Camel
> Issue Type: New Feature
> Components: came-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>
> As today properties binding does not work for nested objects so assuming I
> have a class like:
> {code:java}
> class MyComponent {
>
> public void setFoo(String foo) {
> this.foo = foo;
> }
> public String getFoo() {
> return foo;
> }
> public void setConfiguration(Configuration conf) {
> this.conf = conf;
> }
> public Configuration getConfiguration() {
> return conf;
> }
> static class Configuration {
>
> public void setBar(String bar) {
> this.bar = bar
> }
> public String getBar() {
> return bar
> }
> }
> }
> {code}
> And a set of properties like:
> {code}
> myComponent.foo = "foo"
> myComponent.conf.bar = "bar"
> {code}
> Then only MyComponent.foo will be set but it would be nice if the binding
> framework could navigate the property using dot notation and set any
> dependent object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13566) IntrospectionSupport - Remove old legacy JDK PropertyEditor
[ https://issues.apache.org/jira/browse/CAMEL-13566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13566. - Resolution: Fixed > IntrospectionSupport - Remove old legacy JDK PropertyEditor > --- > > Key: CAMEL-13566 > URL: https://issues.apache.org/jira/browse/CAMEL-13566 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > > There is some old code using JDK > PropertyEditor editor = PropertyEditorManager.findEditor(type); > But this is no longer in use as we really use camel's type converter. That > above is also slow and not thread safe and was intended for java swing/beans > stuff and some cruft from very old times. Lets try to get rid of it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13569) JndiContext - Remove old bean binding
[ https://issues.apache.org/jira/browse/CAMEL-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13569. - Resolution: Fixed > JndiContext - Remove old bean binding > - > > Key: CAMEL-13569 > URL: https://issues.apache.org/jira/browse/CAMEL-13569 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > > There is some old code that allows to define in jndi.properties beans with > .class etc to create these beans via basic class loading that was from Camel > 1.x time and nobody uses. > This should be removed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13572) Message body ignored in DefaultNettyHttpBinding::toNettyResponse
[
https://issues.apache.org/jira/browse/CAMEL-13572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-13572:
--
Affects Version/s: 3.0.0-M3
> Message body ignored in DefaultNettyHttpBinding::toNettyResponse
>
>
> Key: CAMEL-13572
> URL: https://issues.apache.org/jira/browse/CAMEL-13572
> Project: Camel
> Issue Type: Bug
> Components: camel-netty4-http
>Affects Versions: 3.0.0-M3
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0-M3
>
>
> The last optimization that returned the {{HttpResponse}} in case that the
> exchange's message is a {{NettyHttpMessage}} resulted in any changes to the
> body of the message being ignored. The optimization should have checked if
> the body is set and only return the already created {{HttpResponse}} in case
> the message body is {{null}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13572) Message body ignored in DefaultNettyHttpBinding::toNettyResponse
[
https://issues.apache.org/jira/browse/CAMEL-13572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-13572.
---
Resolution: Fixed
> Message body ignored in DefaultNettyHttpBinding::toNettyResponse
>
>
> Key: CAMEL-13572
> URL: https://issues.apache.org/jira/browse/CAMEL-13572
> Project: Camel
> Issue Type: Bug
> Components: camel-netty4-http
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0-M3
>
>
> The last optimization that returned the {{HttpResponse}} in case that the
> exchange's message is a {{NettyHttpMessage}} resulted in any changes to the
> body of the message being ignored. The optimization should have checked if
> the body is set and only return the already created {{HttpResponse}} in case
> the message body is {{null}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13560) Imaps is not reading attachments
[
https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13560:
Priority: Minor (was: Major)
> Imaps is not reading attachments
>
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
> Wed, 22 May 2019 07:13:59 -0700 (PDT)
> Return-Path:
> Received: from [XX] (host-XX.com. [XX])
> by smtp.gmail.com with ESMTPSA id
> for
>
[jira] [Commented] (CAMEL-13561) camel-hystrix - HystrixBadRequestException is swallowed
[ https://issues.apache.org/jira/browse/CAMEL-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847406#comment-16847406 ] Claus Ibsen commented on CAMEL-13561: - Can you provide a PR and/our unit test or something to help point out your point what you want/say > camel-hystrix - HystrixBadRequestException is swallowed > --- > > Key: CAMEL-13561 > URL: https://issues.apache.org/jira/browse/CAMEL-13561 > Project: Camel > Issue Type: Bug > Components: camel-hystrix >Reporter: christian ohr >Priority: Major > > CAMEL-13066 fixed a problem that HystrixBadRequestExceptions caused the > fallback processor being executed. > However, it seems that due to this fix the exception is simply thrown away > and the route proceeds as if no error has occurred. This is certainly not the > intended behavior. > As I understand it, the HystrixBadRequestExceptions should simply be thrown > out of the HystrixProcessor, but without any fallback processor being > triggered or circuit being opened -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13572) Message body ignored in DefaultNettyHttpBinding::toNettyResponse
[
https://issues.apache.org/jira/browse/CAMEL-13572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-13572:
--
Fix Version/s: 3.0.0-M3
> Message body ignored in DefaultNettyHttpBinding::toNettyResponse
>
>
> Key: CAMEL-13572
> URL: https://issues.apache.org/jira/browse/CAMEL-13572
> Project: Camel
> Issue Type: Bug
> Components: camel-netty4-http
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0-M3
>
>
> The last optimization that returned the {{HttpResponse}} in case that the
> exchange's message is a {{NettyHttpMessage}} resulted in any changes to the
> body of the message being ignored. The optimization should have checked if
> the body is set and only return the already created {{HttpResponse}} in case
> the message body is {{null}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13572) Message body ignored in DefaultNettyHttpBinding::toNettyResponse
Zoran Regvart created CAMEL-13572:
-
Summary: Message body ignored in
DefaultNettyHttpBinding::toNettyResponse
Key: CAMEL-13572
URL: https://issues.apache.org/jira/browse/CAMEL-13572
Project: Camel
Issue Type: Bug
Components: camel-netty4-http
Reporter: Zoran Regvart
Assignee: Zoran Regvart
The last optimization that returned the {{HttpResponse}} in case that the
exchange's message is a {{NettyHttpMessage}} resulted in any changes to the
body of the message being ignored. The optimization should have checked if the
body is set and only return the already created {{HttpResponse}} in case the
message body is {{null}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846973#comment-16846973
]
Claus Ibsen edited comment on CAMEL-13557 at 5/24/19 9:18 AM:
--
Got the CXF error fixed.
We should add option on component/endpoint to turn this on|off, as this can
also be used to configure endpoints with nested options. *DONE*
was (Author: davsclaus):
Got the CXF error fixed.
We should add option on component/endpoint to turn this on|off, as this can
also be used to configure endpoints with nested options.
> Support for nested properties binding
> -
>
> Key: CAMEL-13557
> URL: https://issues.apache.org/jira/browse/CAMEL-13557
> Project: Camel
> Issue Type: New Feature
> Components: came-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>
> As today properties binding does not work for nested objects so assuming I
> have a class like:
> {code:java}
> class MyComponent {
>
> public void setFoo(String foo) {
> this.foo = foo;
> }
> public String getFoo() {
> return foo;
> }
> public void setConfiguration(Configuration conf) {
> this.conf = conf;
> }
> public Configuration getConfiguration() {
> return conf;
> }
> static class Configuration {
>
> public void setBar(String bar) {
> this.bar = bar
> }
> public String getBar() {
> return bar
> }
> }
> }
> {code}
> And a set of properties like:
> {code}
> myComponent.foo = "foo"
> myComponent.conf.bar = "bar"
> {code}
> Then only MyComponent.foo will be set but it would be nice if the binding
> framework could navigate the property using dot notation and set any
> dependent object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13571) Camel AWS-SNS: Make the autocreation of the topic configurable
Andrea Cosentino created CAMEL-13571: Summary: Camel AWS-SNS: Make the autocreation of the topic configurable Key: CAMEL-13571 URL: https://issues.apache.org/jira/browse/CAMEL-13571 Project: Camel Issue Type: New Feature Components: camel-aws-sqs Reporter: Andrea Cosentino Assignee: Andrea Cosentino We can leave the behavior as the older, but we can make it configurable to avoid autocreation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13570) Camel AWS-SQS: Make the autocreation of the queue configurable
Andrea Cosentino created CAMEL-13570: Summary: Camel AWS-SQS: Make the autocreation of the queue configurable Key: CAMEL-13570 URL: https://issues.apache.org/jira/browse/CAMEL-13570 Project: Camel Issue Type: New Feature Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino We can leave the behavior as the older, but make it possible to avoid the autocreation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13569) JndiContext - Remove old bean binding
Claus Ibsen created CAMEL-13569: --- Summary: JndiContext - Remove old bean binding Key: CAMEL-13569 URL: https://issues.apache.org/jira/browse/CAMEL-13569 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.0.0, 3.0.0-M3 There is some old code that allows to define in jndi.properties beans with .class etc to create these beans via basic class loading that was from Camel 1.x time and nobody uses. This should be removed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847327#comment-16847327 ] Andrea Cosentino commented on CAMEL-13563: -- The first attempt breaks cometd and salesforce Karaf feature, we need to take care of them, but for M4 > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 3.0.0.M4 > > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13563: - Fix Version/s: 3.0.0.M4 > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 3.0.0.M4 > > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13568) Create archetype for releases
[ https://issues.apache.org/jira/browse/CAMEL-13568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-13568: -- Issue Type: Sub-task (was: Task) Parent: CAMEL-11492 > Create archetype for releases > - > > Key: CAMEL-13568 > URL: https://issues.apache.org/jira/browse/CAMEL-13568 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > > I think a separate archetype for releases would be a good idea. We can also > make this archetype data-driven from JIRA issues, so list of > enhancements/fixes can be incorporated within it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13568) Create archetype for releases
[ https://issues.apache.org/jira/browse/CAMEL-13568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-13568: -- Issue Type: Task (was: Bug) > Create archetype for releases > - > > Key: CAMEL-13568 > URL: https://issues.apache.org/jira/browse/CAMEL-13568 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Priority: Major > > I think a separate archetype for releases would be a good idea. We can also > make this archetype data-driven from JIRA issues, so list of > enhancements/fixes can be incorporated within it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13568) Create archetype for releases
Zoran Regvart created CAMEL-13568: - Summary: Create archetype for releases Key: CAMEL-13568 URL: https://issues.apache.org/jira/browse/CAMEL-13568 Project: Camel Issue Type: Bug Components: website Reporter: Zoran Regvart I think a separate archetype for releases would be a good idea. We can also make this archetype data-driven from JIRA issues, so list of enhancements/fixes can be incorporated within it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13567) Create archetype for blog/news section of the site
Zoran Regvart created CAMEL-13567: - Summary: Create archetype for blog/news section of the site Key: CAMEL-13567 URL: https://issues.apache.org/jira/browse/CAMEL-13567 Project: Camel Issue Type: Sub-task Components: website Reporter: Zoran Regvart We need to add a Hugo archetype for creating news or blog entries on the website. We should also consider migrating existing blog entries to Markdown in the format of this new archetype. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-8047) Replace BundleDelegatingClassLoader with BundleWiring
[ https://issues.apache.org/jira/browse/CAMEL-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned CAMEL-8047: --- Assignee: Jean-Baptiste Onofré > Replace BundleDelegatingClassLoader with BundleWiring > - > > Key: CAMEL-8047 > URL: https://issues.apache.org/jira/browse/CAMEL-8047 > Project: Camel > Issue Type: Improvement > Components: osgi >Affects Versions: 2.14.0 >Reporter: Christian Schneider >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: Future > > > I found we have the class BundleDelegatingClassLoader in camel-core-osgi. I > wonder if the same could be achieved by > bundle.adapt(BundleWiring.class).getClassLoder ? > As we use the OSGi spec 4.3.1 now I think we can replace this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-9627) Splitup camel-cxf into modules so REST dont pull in old SOAP stuff
[ https://issues.apache.org/jira/browse/CAMEL-9627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned CAMEL-9627: --- Assignee: Jean-Baptiste Onofré > Splitup camel-cxf into modules so REST dont pull in old SOAP stuff > -- > > Key: CAMEL-9627 > URL: https://issues.apache.org/jira/browse/CAMEL-9627 > Project: Camel > Issue Type: Improvement > Components: karaf, osgi >Reporter: Claus Ibsen >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: Future > > > To make camel-cxf feature less bloated and not include this seldom used > component which you can install as its own feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-10943) Karaf 4.1.0 dont work with some Camel examples
[ https://issues.apache.org/jira/browse/CAMEL-10943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847287#comment-16847287 ] Jean-Baptiste Onofré commented on CAMEL-10943: -- I'm reviewing the examples and eventually fix. > Karaf 4.1.0 dont work with some Camel examples > -- > > Key: CAMEL-10943 > URL: https://issues.apache.org/jira/browse/CAMEL-10943 > Project: Camel > Issue Type: Task > Components: examples, karaf >Reporter: Claus Ibsen >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: Future > > > More OSGi pain with this new release. > For example > http://stackoverflow.com/questions/42608617/apache-camel-on-karaf-with-spring-dsl-osgi/42609554#42609554 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-8047) Replace BundleDelegatingClassLoader with BundleWiring
[ https://issues.apache.org/jira/browse/CAMEL-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847288#comment-16847288 ] Jean-Baptiste Onofré commented on CAMEL-8047: - Resuming to see if this Jira still makes sense. > Replace BundleDelegatingClassLoader with BundleWiring > - > > Key: CAMEL-8047 > URL: https://issues.apache.org/jira/browse/CAMEL-8047 > Project: Camel > Issue Type: Improvement > Components: osgi >Affects Versions: 2.14.0 >Reporter: Christian Schneider >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: Future > > > I found we have the class BundleDelegatingClassLoader in camel-core-osgi. I > wonder if the same could be achieved by > bundle.adapt(BundleWiring.class).getClassLoder ? > As we use the OSGi spec 4.3.1 now I think we can replace this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-11877) OsgiServiceRegistry might use stale Services
[ https://issues.apache.org/jira/browse/CAMEL-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned CAMEL-11877: Assignee: Jean-Baptiste Onofré > OsgiServiceRegistry might use stale Services > > > Key: CAMEL-11877 > URL: https://issues.apache.org/jira/browse/CAMEL-11877 > Project: Camel > Issue Type: Improvement > Components: osgi >Reporter: Christoph Läubrich >Assignee: Jean-Baptiste Onofré >Priority: Major > > OsgiServiceRegistry uses raw ServiceReferences to obtain a Servie Object. > Once the Object is fetched it is cached and reused. THis can lead to the > state, that cmael uses outdated services (e.g. the service get > updated/replaced). > To prevent this, Camel should use ServiceTracker instead, this would make > fetching services much more easier and roboust because ServiceTracker will > handle all the dynamic parts and can simply be queried for a Service. > The ServiceTraker Objects itself can then be cached and simply closed > onContextStop -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-10943) Karaf 4.1.0 dont work with some Camel examples
[ https://issues.apache.org/jira/browse/CAMEL-10943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned CAMEL-10943: Assignee: Jean-Baptiste Onofré > Karaf 4.1.0 dont work with some Camel examples > -- > > Key: CAMEL-10943 > URL: https://issues.apache.org/jira/browse/CAMEL-10943 > Project: Camel > Issue Type: Task > Components: examples, karaf >Reporter: Claus Ibsen >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: Future > > > More OSGi pain with this new release. > For example > http://stackoverflow.com/questions/42608617/apache-camel-on-karaf-with-spring-dsl-osgi/42609554#42609554 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13566) IntrospectionSupport - Remove old legacy JDK PropertyEditor
[ https://issues.apache.org/jira/browse/CAMEL-13566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-13566: --- Assignee: Claus Ibsen > IntrospectionSupport - Remove old legacy JDK PropertyEditor > --- > > Key: CAMEL-13566 > URL: https://issues.apache.org/jira/browse/CAMEL-13566 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > > There is some old code using JDK > PropertyEditor editor = PropertyEditorManager.findEditor(type); > But this is no longer in use as we really use camel's type converter. That > above is also slow and not thread safe and was intended for java swing/beans > stuff and some cruft from very old times. Lets try to get rid of it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13566) IntrospectionSupport - Remove old legacy JDK PropertyEditor
Claus Ibsen created CAMEL-13566: --- Summary: IntrospectionSupport - Remove old legacy JDK PropertyEditor Key: CAMEL-13566 URL: https://issues.apache.org/jira/browse/CAMEL-13566 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 3.0.0, 3.0.0-M3 There is some old code using JDK PropertyEditor editor = PropertyEditorManager.findEditor(type); But this is no longer in use as we really use camel's type converter. That above is also slow and not thread safe and was intended for java swing/beans stuff and some cruft from very old times. Lets try to get rid of it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
