[jira] [Resolved] (CAMEL-7282) onException should enable backoff if backOffMultiplier is in use - just as errorHandler does
[ https://issues.apache.org/jira/browse/CAMEL-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7282. Resolution: Fixed onException should enable backoff if backOffMultiplier is in use - just as errorHandler does Key: CAMEL-7282 URL: https://issues.apache.org/jira/browse/CAMEL-7282 Project: Camel Issue Type: Bug Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.13.0 Lets keep this change on the new release only. See nabble http://camel.465427.n5.nabble.com/diagnosing-onException-problem-tp5748474.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7283) PGP Data Format: Signature Verification Options
[ https://issues.apache.org/jira/browse/CAMEL-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13930109#comment-13930109 ] Franz Forsthofer commented on CAMEL-7283: - I also made a minor refactoring in PGPDataFormatUtil. PGP Data Format: Signature Verification Options --- Key: CAMEL-7283 URL: https://issues.apache.org/jira/browse/CAMEL-7283 Project: Camel Issue Type: Improvement Components: camel-crypto Reporter: Franz Forsthofer Fix For: 2.13.0, 2.13.1, 2.14.0 Attachments: 0001-pgp-signature-verification-options.patch The current PGP Data Format does verify a signature if the PGP message does contain one and it does execute no verification if the PGP message does not contain a signature. There is a use case where a signature verification is always required because the receiver wants to check that the message came from a specific sender. In this case PGP messages not containing a signature should be rejected. I added the new parameter signatureVerificationOption so that you now can specify if a signature is requried, optional, or no signature is allowed during the decryption process. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7283) PGP Data Format: Signature Verification Options
[ https://issues.apache.org/jira/browse/CAMEL-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franz Forsthofer updated CAMEL-7283: Attachment: 0001-pgp-signature-verification-options.patch PGP Data Format: Signature Verification Options --- Key: CAMEL-7283 URL: https://issues.apache.org/jira/browse/CAMEL-7283 Project: Camel Issue Type: Improvement Components: camel-crypto Reporter: Franz Forsthofer Fix For: 2.13.0, 2.13.1, 2.14.0 Attachments: 0001-pgp-signature-verification-options.patch The current PGP Data Format does verify a signature if the PGP message does contain one and it does execute no verification if the PGP message does not contain a signature. There is a use case where a signature verification is always required because the receiver wants to check that the message came from a specific sender. In this case PGP messages not containing a signature should be rejected. I added the new parameter signatureVerificationOption so that you now can specify if a signature is requried, optional, or no signature is allowed during the decryption process. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7249) Upgrade Camel-HDFS component to be compatible with Apache Hadoop 2.x
[ https://issues.apache.org/jira/browse/CAMEL-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13930132#comment-13930132 ] Grzegorz Grzybek commented on CAMEL-7249: - I just stopped because of [this|http://blog.osgi.org/2013/02/javautilserviceloader-in-osgi.html]... Upgrade Camel-HDFS component to be compatible with Apache Hadoop 2.x Key: CAMEL-7249 URL: https://issues.apache.org/jira/browse/CAMEL-7249 Project: Camel Issue Type: New Feature Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Currently camel-hdfs depends on hadoop-core:1.2.1. Make (working name) {{camel-hdfs2}} component using newest (hadoop 2.3.0) libraries. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7281) Add support for certAlias in SSLContextParameters
[ https://issues.apache.org/jira/browse/CAMEL-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13930259#comment-13930259 ] Colm O hEigeartaigh commented on CAMEL-7281: Documentation updated... Colm. Add support for certAlias in SSLContextParameters --- Key: CAMEL-7281 URL: https://issues.apache.org/jira/browse/CAMEL-7281 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Colm O hEigeartaigh Assignee: Claus Ibsen Fix For: 2.13.0 Attachments: camel-7281.patch, localhost-alias.ks There is no support for a certAlias type parameters in SSLContextParameters, as in CXF. This means that it's not possible to use Keystores with more than one entry for TLS. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7281) Add support for certAlias in SSLContextParameters
[ https://issues.apache.org/jira/browse/CAMEL-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7281. Resolution: Fixed Add support for certAlias in SSLContextParameters --- Key: CAMEL-7281 URL: https://issues.apache.org/jira/browse/CAMEL-7281 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Colm O hEigeartaigh Assignee: Claus Ibsen Fix For: 2.13.0 Attachments: camel-7281.patch, localhost-alias.ks There is no support for a certAlias type parameters in SSLContextParameters, as in CXF. This means that it's not possible to use Keystores with more than one entry for TLS. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CAMEL-7283) PGP Data Format: Signature Verification Options
[ https://issues.apache.org/jira/browse/CAMEL-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea reassigned CAMEL-7283: -- Assignee: Hadrian Zbarcea PGP Data Format: Signature Verification Options --- Key: CAMEL-7283 URL: https://issues.apache.org/jira/browse/CAMEL-7283 Project: Camel Issue Type: Improvement Components: camel-crypto Reporter: Franz Forsthofer Assignee: Hadrian Zbarcea Fix For: 2.13.0, 2.13.1, 2.14.0 Attachments: 0001-pgp-signature-verification-options.patch The current PGP Data Format does verify a signature if the PGP message does contain one and it does execute no verification if the PGP message does not contain a signature. There is a use case where a signature verification is always required because the receiver wants to check that the message came from a specific sender. In this case PGP messages not containing a signature should be rejected. I added the new parameter signatureVerificationOption so that you now can specify if a signature is requried, optional, or no signature is allowed during the decryption process. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7249) Upgrade Camel-HDFS component to be compatible with Apache Hadoop 2.x
[ https://issues.apache.org/jira/browse/CAMEL-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13930278#comment-13930278 ] Grzegorz Grzybek commented on CAMEL-7249: - The problem is this hadoop code: {code:java} private static void loadFileSystems() { synchronized (FileSystem.class) { if (!FILE_SYSTEMS_LOADED) { ServiceLoaderFileSystem serviceLoader = ServiceLoader.load(FileSystem.class); for (FileSystem fs : serviceLoader) { SERVICE_FILE_SYSTEMS.put(fs.getScheme(), fs.getClass()); } FILE_SYSTEMS_LOADED = true; } } } ... public static Class? extends FileSystem getFileSystemClass(String scheme, Configuration conf) throws IOException { if (!FILE_SYSTEMS_LOADED) { loadFileSystems(); } Class? extends FileSystem clazz = null; if (conf != null) { clazz = (Class? extends FileSystem) conf.getClass(fs. + scheme + .impl, null); } if (clazz == null) { clazz = SERVICE_FILE_SYSTEMS.get(scheme); } if (clazz == null) { throw new IOException(No FileSystem for scheme: + scheme); } return clazz; } {code} which uses either {{java.util.ServiceLoader}} (doesn't work in OSGi) or {{fs.scheme.impl}} configuration properties. OK. If I create routes manually, I can do the following: {code:java} org.apache.hadoop.conf.Configuration conf = new org.apache.hadoop.conf.Configuration(); conf.setClass(fs.file.impl, org.apache.hadoop.fs.LocalFileSystem.class, FileSystem.class); conf.setClass(fs.hdfs.impl, org.apache.hadoop.hdfs.DistributedFileSystem.class, FileSystem.class); FileSystem.get(file:///, conf) {code} which caches the mapping {{file: - org.apache.hadoop.fs.LocalFileSystem.class}} in current classloader (static field {{org.apache.hadoop.fs.FileSystem.CACHE}}). But it's not that easy with Blueprint based routes... OK. I'll work more on ways to configure {{HdfsComponent}}. Upgrade Camel-HDFS component to be compatible with Apache Hadoop 2.x Key: CAMEL-7249 URL: https://issues.apache.org/jira/browse/CAMEL-7249 Project: Camel Issue Type: New Feature Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Currently camel-hdfs depends on hadoop-core:1.2.1. Make (working name) {{camel-hdfs2}} component using newest (hadoop 2.3.0) libraries. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7227) Create camel-kafka feature
[ https://issues.apache.org/jira/browse/CAMEL-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7227. Resolution: Fixed Fix Version/s: (was: 2.13.1) 2.13.0 Assignee: Claus Ibsen (was: Jean-Baptiste Onofré) We have a camel-kafka feature now. Create camel-kafka feature -- Key: CAMEL-7227 URL: https://issues.apache.org/jira/browse/CAMEL-7227 Project: Camel Issue Type: Task Components: karaf Reporter: Willem Jiang Assignee: Claus Ibsen Fix For: 2.13.0 We need to wrap a kafka OSGi bundle first, then create a feature for it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7227) Create camel-kafka feature
[ https://issues.apache.org/jira/browse/CAMEL-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-7227: --- Component/s: karaf Create camel-kafka feature -- Key: CAMEL-7227 URL: https://issues.apache.org/jira/browse/CAMEL-7227 Project: Camel Issue Type: Task Components: karaf Reporter: Willem Jiang Assignee: Claus Ibsen Fix For: 2.13.0 We need to wrap a kafka OSGi bundle first, then create a feature for it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7284) Missing setter for ApnsDelegate
marcin arciuch created CAMEL-7284: - Summary: Missing setter for ApnsDelegate Key: CAMEL-7284 URL: https://issues.apache.org/jira/browse/CAMEL-7284 Project: Camel Issue Type: Improvement Components: camel-apns Reporter: marcin arciuch Priority: Minor Hello, there's a slight problem in the ApnsServiceFactory in that there's a missing setter for ApnsDelegate. The ability to wire one in is important, as java-apns uses it as a destination of send acks/errors, and without it there's no way to diagnose or react to them. thanks, Marcin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7284) Missing setter for ApnsDelegate
[ https://issues.apache.org/jira/browse/CAMEL-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13930745#comment-13930745 ] ASF GitHub Bot commented on CAMEL-7284: --- GitHub user marcin-a opened a pull request: https://github.com/apache/camel/pull/109 Missing setter for ApnsDelegate in ApnsServiceFactory Hello, this resolves https://issues.apache.org/jira/browse/CAMEL-7284 You can merge this pull request into a Git repository by running: $ git pull https://github.com/marcin-a/camel CAMEL-7284 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/109.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #109 commit 50f122a1608cc95fd42e70a29964347f208abd09 Author: Marcin Arciuch marcin.arci...@gmail.com Date: 2014-03-11T18:35:42Z adding missing setter for ApnsDelegate Missing setter for ApnsDelegate --- Key: CAMEL-7284 URL: https://issues.apache.org/jira/browse/CAMEL-7284 Project: Camel Issue Type: Improvement Components: camel-apns Reporter: marcin arciuch Priority: Minor Hello, there's a slight problem in the ApnsServiceFactory in that there's a missing setter for ApnsDelegate. The ability to wire one in is important, as java-apns uses it as a destination of send acks/errors, and without it there's no way to diagnose or react to them. thanks, Marcin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7286) amazonSNSEndpoint option is ignored
Willem Jiang created CAMEL-7286: --- Summary: amazonSNSEndpoint option is ignored Key: CAMEL-7286 URL: https://issues.apache.org/jira/browse/CAMEL-7286 Project: Camel Issue Type: Bug Components: camel-aws Affects Versions: 2.12.3, 2.11.4 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.12.4, 2.13.0, 2.11.5 I just got [an user complain|http://camel.465427.n5.nabble.com/AWS-SNS-Camel-amazonSNSEndpoint-being-ignored-tp5748651.html ] that the amazonSNSEndpoint option of aws-sns was ignored. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CAMEL-7284) Missing setter for ApnsDelegate
[ https://issues.apache.org/jira/browse/CAMEL-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-7284: --- Assignee: Willem Jiang Missing setter for ApnsDelegate --- Key: CAMEL-7284 URL: https://issues.apache.org/jira/browse/CAMEL-7284 Project: Camel Issue Type: Improvement Components: camel-apns Reporter: marcin arciuch Assignee: Willem Jiang Priority: Minor Hello, there's a slight problem in the ApnsServiceFactory in that there's a missing setter for ApnsDelegate. The ability to wire one in is important, as java-apns uses it as a destination of send acks/errors, and without it there's no way to diagnose or react to them. thanks, Marcin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7285) Upgrade Apache Jackrabbit Library for camel-jcr Component
[ https://issues.apache.org/jira/browse/CAMEL-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregor Zurowski updated CAMEL-7285: --- Assignee: Gregor Zurowski Upgrade Apache Jackrabbit Library for camel-jcr Component - Key: CAMEL-7285 URL: https://issues.apache.org/jira/browse/CAMEL-7285 Project: Camel Issue Type: Improvement Components: camel-jcr Reporter: Gregor Zurowski Assignee: Gregor Zurowski Priority: Minor Upgrade the Apache Jackrabbit library for the camel-jcr component to the latest stable release (2.6.5). Currently Camel still uses the older 2.2.12 version of Jackrabbit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7285) Upgrade Apache Jackrabbit Library for camel-jcr Component
[ https://issues.apache.org/jira/browse/CAMEL-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13931261#comment-13931261 ] Willem Jiang commented on CAMEL-7285: - I'm not sure if the new related Jackrabbit is OSGi ready, we may need to update the camel karaf feature as well. Upgrade Apache Jackrabbit Library for camel-jcr Component - Key: CAMEL-7285 URL: https://issues.apache.org/jira/browse/CAMEL-7285 Project: Camel Issue Type: Improvement Components: camel-jcr Reporter: Gregor Zurowski Assignee: Gregor Zurowski Priority: Minor Upgrade the Apache Jackrabbit library for the camel-jcr component to the latest stable release (2.6.5). Currently Camel still uses the older 2.2.12 version of Jackrabbit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7227) Create camel-kafka feature
[ https://issues.apache.org/jira/browse/CAMEL-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13931195#comment-13931195 ] Damien Claveau commented on CAMEL-7227: --- Congratulations ! Good to read that news. We were waiting for this must-have feature. It can probably be announced on that page https://camel.apache.org/camel-2130-release.html Create camel-kafka feature -- Key: CAMEL-7227 URL: https://issues.apache.org/jira/browse/CAMEL-7227 Project: Camel Issue Type: Task Components: karaf Reporter: Willem Jiang Assignee: Claus Ibsen Fix For: 2.13.0 We need to wrap a kafka OSGi bundle first, then create a feature for it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7249) Upgrade Camel-HDFS component to be compatible with Apache Hadoop 2.x
[ https://issues.apache.org/jira/browse/CAMEL-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13931295#comment-13931295 ] liugang commented on CAMEL-7249: I'm not sure who's in charge of camel-hdfs feature on Karaf. it seems have the same problem to load the default configuration core-default.xml file, so we have to add this fine into each route bundle to make it work. and this is not easy for blueprint file case, because it requires to change the auto-generated bundle manually. do you will also care about that? (but I prefer to use this camel-hdfs2 component once it presents) Thanks. Upgrade Camel-HDFS component to be compatible with Apache Hadoop 2.x Key: CAMEL-7249 URL: https://issues.apache.org/jira/browse/CAMEL-7249 Project: Camel Issue Type: New Feature Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Currently camel-hdfs depends on hadoop-core:1.2.1. Make (working name) {{camel-hdfs2}} component using newest (hadoop 2.3.0) libraries. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7285) Upgrade Apache Jackrabbit Library for camel-jcr Component
Gregor Zurowski created CAMEL-7285: -- Summary: Upgrade Apache Jackrabbit Library for camel-jcr Component Key: CAMEL-7285 URL: https://issues.apache.org/jira/browse/CAMEL-7285 Project: Camel Issue Type: Improvement Components: camel-jcr Reporter: Gregor Zurowski Priority: Minor Upgrade the Apache Jackrabbit library for the camel-jcr component to the latest stable release (2.6.5). Currently Camel still uses the older 2.2.12 version of Jackrabbit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7284) Missing setter for ApnsDelegate
[ https://issues.apache.org/jira/browse/CAMEL-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7284. - Resolution: Fixed Fix Version/s: 2.11.5 2.13.0 2.12.4 Applied the patch into master, camel-2.12.x and camel-2.11.x branches with thanks to Marcin. Missing setter for ApnsDelegate --- Key: CAMEL-7284 URL: https://issues.apache.org/jira/browse/CAMEL-7284 Project: Camel Issue Type: Improvement Components: camel-apns Reporter: marcin arciuch Assignee: Willem Jiang Priority: Minor Fix For: 2.12.4, 2.13.0, 2.11.5 Hello, there's a slight problem in the ApnsServiceFactory in that there's a missing setter for ApnsDelegate. The ability to wire one in is important, as java-apns uses it as a destination of send acks/errors, and without it there's no way to diagnose or react to them. thanks, Marcin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7286) amazonSNSEndpoint option is ignored
[ https://issues.apache.org/jira/browse/CAMEL-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7286. - Resolution: Fixed Applied patch into master, camel-2.12.x and camel-2.11.x branches. amazonSNSEndpoint option is ignored --- Key: CAMEL-7286 URL: https://issues.apache.org/jira/browse/CAMEL-7286 Project: Camel Issue Type: Bug Components: camel-aws Affects Versions: 2.11.4, 2.12.3 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.12.4, 2.13.0, 2.11.5 I just got [an user complain|http://camel.465427.n5.nabble.com/AWS-SNS-Camel-amazonSNSEndpoint-being-ignored-tp5748651.html ] that the amazonSNSEndpoint option of aws-sns was ignored. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7214) Upgrade to elasticsearch 1.0
[ https://issues.apache.org/jira/browse/CAMEL-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7214. - Resolution: Fixed Fix Version/s: (was: 2.13.1) 2.13.0 Applied the patch into camel master branch. Upgrade to elasticsearch 1.0 Key: CAMEL-7214 URL: https://issues.apache.org/jira/browse/CAMEL-7214 Project: Camel Issue Type: Task Reporter: Claus Ibsen Assignee: Willem Jiang Fix For: 2.13.0 Its 1.0 now and we should upgrade. Not sure if we need an OSGi bundle from the SMX team? -- This message was sent by Atlassian JIRA (v6.2#6252)