[jira] [Created] (CAMEL-12823) Create a LINE component
Tadayoshi Sato created CAMEL-12823: -- Summary: Create a LINE component Key: CAMEL-12823 URL: https://issues.apache.org/jira/browse/CAMEL-12823 Project: Camel Issue Type: New Feature Reporter: Tadayoshi Sato Assignee: Tadayoshi Sato [LINE|https://developers.line.me/en/] is the most popular mobile messaging service in Japan. I will try to create a component for handling the SDKs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12750) Expose OData4 based service as consumer endpoint
[ https://issues.apache.org/jira/browse/CAMEL-12750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620673#comment-16620673 ] Ramu commented on CAMEL-12750: -- Dmitry, Thanks for the clarification. yes I am going to work on this. Let me take a look at [Implementing an OData service with Olingo|https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/]. > Expose OData4 based service as consumer endpoint > > > Key: CAMEL-12750 > URL: https://issues.apache.org/jira/browse/CAMEL-12750 > Project: Camel > Issue Type: New Feature > Components: camel-olingo4 >Affects Versions: 2.22.0 >Reporter: Dmitry Volodin >Assignee: Ramu >Priority: Major > > Right now, only polling consumer is available for olingo4 component. It's > better to have a real listening consumer for this. > The method may have name like 'listen' to be able to create a listening > consumer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12750) Expose OData4 based service as consumer endpoint
[ https://issues.apache.org/jira/browse/CAMEL-12750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620627#comment-16620627 ] Dmitry Volodin commented on CAMEL-12750: Claus, I means that the new listening component will be use olingo4 consumer based on servlet implementation as described here [Implementing an OData service with Olingo|https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/]. I'm not sure, we can use async response options in Camel, but we would try to implement consumer. As a current component implementation based on Camel API component, it would be nice to use a separate schema for a listening implementation. I thought that component starts to use EDM build with Java class implementation and will use standard Camel exchange to manipulate data starting entity CRUD. [~ramu11] A you working on this issue? > Expose OData4 based service as consumer endpoint > > > Key: CAMEL-12750 > URL: https://issues.apache.org/jira/browse/CAMEL-12750 > Project: Camel > Issue Type: New Feature > Components: camel-olingo4 >Affects Versions: 2.22.0 >Reporter: Dmitry Volodin >Assignee: Ramu >Priority: Major > > Right now, only polling consumer is available for olingo4 component. It's > better to have a real listening consumer for this. > The method may have name like 'listen' to be able to create a listening > consumer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12750) Expose OData4 based service as consumer endpoint
[ https://issues.apache.org/jira/browse/CAMEL-12750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620627#comment-16620627 ] Dmitry Volodin edited comment on CAMEL-12750 at 9/19/18 1:59 PM: - Claus, I mean that the new listening component will be use olingo4 consumer based on servlet implementation as described here [Implementing an OData service with Olingo|https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/]. I'm not sure, we can use async response options in Camel, but we would try to implement consumer. As a current component implementation based on Camel API component, it would be nice to use a separate schema for a listening implementation. I thought that component starts to use EDM build with Java class implementation and will use standard Camel exchange to manipulate data starting entity CRUD. [~ramu11] A you working on this issue? was (Author: dmvolod): Claus, I means that the new listening component will be use olingo4 consumer based on servlet implementation as described here [Implementing an OData service with Olingo|https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/]. I'm not sure, we can use async response options in Camel, but we would try to implement consumer. As a current component implementation based on Camel API component, it would be nice to use a separate schema for a listening implementation. I thought that component starts to use EDM build with Java class implementation and will use standard Camel exchange to manipulate data starting entity CRUD. [~ramu11] A you working on this issue? > Expose OData4 based service as consumer endpoint > > > Key: CAMEL-12750 > URL: https://issues.apache.org/jira/browse/CAMEL-12750 > Project: Camel > Issue Type: New Feature > Components: camel-olingo4 >Affects Versions: 2.22.0 >Reporter: Dmitry Volodin >Assignee: Ramu >Priority: Major > > Right now, only polling consumer is available for olingo4 component. It's > better to have a real listening consumer for this. > The method may have name like 'listen' to be able to create a listening > consumer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12750) Expose OData4 based service as consumer endpoint
[ https://issues.apache.org/jira/browse/CAMEL-12750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620698#comment-16620698 ] Dmitry Volodin commented on CAMEL-12750: [~ramu11], thanks for going to work on issue. If you will have questions we can discuss the issue offline. > Expose OData4 based service as consumer endpoint > > > Key: CAMEL-12750 > URL: https://issues.apache.org/jira/browse/CAMEL-12750 > Project: Camel > Issue Type: New Feature > Components: camel-olingo4 >Affects Versions: 2.22.0 >Reporter: Dmitry Volodin >Assignee: Ramu >Priority: Major > > Right now, only polling consumer is available for olingo4 component. It's > better to have a real listening consumer for this. > The method may have name like 'listen' to be able to create a listening > consumer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12750) Expose OData4 based service as consumer endpoint
[ https://issues.apache.org/jira/browse/CAMEL-12750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620708#comment-16620708 ] Ramu commented on CAMEL-12750: -- Dmitry, sure > Expose OData4 based service as consumer endpoint > > > Key: CAMEL-12750 > URL: https://issues.apache.org/jira/browse/CAMEL-12750 > Project: Camel > Issue Type: New Feature > Components: camel-olingo4 >Affects Versions: 2.22.0 >Reporter: Dmitry Volodin >Assignee: Ramu >Priority: Major > > Right now, only polling consumer is available for olingo4 component. It's > better to have a real listening consumer for this. > The method may have name like 'listen' to be able to create a listening > consumer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12750) Expose OData4 based service as consumer endpoint
[ https://issues.apache.org/jira/browse/CAMEL-12750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620584#comment-16620584 ] Claus Ibsen commented on CAMEL-12750: - Dmitry, do you mean that a new event based consumer that uses a different name, oling4-listen (or something) that is not scheduled based as the current ones. And if so, what functionality / APIs of the existing one would it support? And is an event based possible? Does olingo4 have some APIs we can use to get noitifications when a new event happened. Maybe you can explain a bit more > Expose OData4 based service as consumer endpoint > > > Key: CAMEL-12750 > URL: https://issues.apache.org/jira/browse/CAMEL-12750 > Project: Camel > Issue Type: New Feature > Components: camel-olingo4 >Affects Versions: 2.22.0 >Reporter: Dmitry Volodin >Assignee: Ramu >Priority: Major > > Right now, only polling consumer is available for olingo4 component. It's > better to have a real listening consumer for this. > The method may have name like 'listen' to be able to create a listening > consumer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12822) camel-http4 - Expose connection pool stats in JMX
Claus Ibsen created CAMEL-12822: --- Summary: camel-http4 - Expose connection pool stats in JMX Key: CAMEL-12822 URL: https://issues.apache.org/jira/browse/CAMEL-12822 Project: Camel Issue Type: New Feature Components: camel-http4 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.23.0 So end users can track the stats of the client connection pool, for example to see when all connections are in use, or the number of idle connections and so on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12822) camel-http4 - Expose connection pool stats in JMX
[ https://issues.apache.org/jira/browse/CAMEL-12822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12822. - Resolution: Fixed You can now find such details on the http endpoint class and its JMX mbean. > camel-http4 - Expose connection pool stats in JMX > - > > Key: CAMEL-12822 > URL: https://issues.apache.org/jira/browse/CAMEL-12822 > Project: Camel > Issue Type: New Feature > Components: camel-http4 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.23.0 > > > So end users can track the stats of the client connection pool, for example > to see when all connections are in use, or the number of idle connections and > so on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
***UNCHECKED*** [jira] [Commented] (CAMEL-12605) Enhance the AS2 Component to send and receive encrypted AS2 messages
[
https://issues.apache.org/jira/browse/CAMEL-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620226#comment-16620226
]
ASF GitHub Bot commented on CAMEL-12605:
oscerd closed pull request #2524: [CAMEL-12605] Refactored encryption
algorithms and added tests for al…
URL: https://github.com/apache/camel/pull/2524
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/components/camel-as2/camel-as2-api/src/main/java/org/apache/camel/component/as2/api/AS2Algorithm.java
b/components/camel-as2/camel-as2-api/src/main/java/org/apache/camel/component/as2/api/AS2Algorithm.java
deleted file mode 100644
index 8e71f478ff2..000
---
a/components/camel-as2/camel-as2-api/src/main/java/org/apache/camel/component/as2/api/AS2Algorithm.java
+++ /dev/null
@@ -1,346 +0,0 @@
-/**
- * Licensed to the Apache Software Foundation (ASF) under one or more
- * contributor license agreements. See the NOTICE file distributed with
- * this work for additional information regarding copyright ownership.
- * The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
- * the License. You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-package org.apache.camel.component.as2.api;
-
-import org.bouncycastle.asn1.ASN1ObjectIdentifier;
-import org.bouncycastle.cms.CMSAlgorithm;
-
-interface AS2AlgorithmConstants {
-static final String DES_CBC = "DES_CBC";
-static final String DES_EDE3_CBC = "DES_EDE3_CBC";
-static final String RC2_CBC = "RC2_CBC";
-static final String IDEA_CBC = "IDEA_CBC";
-static final String CAST5_CBC = "CAST5_CBC";
-static final String AES128_CBC = "AES128_CBC";
-static final String AES192_CBC = "AES192_CBC";
-static final String AES256_CBC = "AES256_CBC";
-static final String AES128_CCM = "AES128_CCM";
-static final String AES192_CCM = "AES192_CCM";
-static final String AES256_CCM = "AES256_CCM";
-static final String AES128_GCM = "AES128_GCM";
-static final String AES192_GCM = "AES192_GCM";
-static final String AES256_GCM = "AES256_GCM";
-static final String CAMELLIA128_CBC = "CAMELLIA128_CBC";
-static final String CAMELLIA192_CBC = "CAMELLIA192_CBC";
-static final String CAMELLIA256_CBC = "CAMELLIA256_CBC";
-static final String GOST28147_GCFB = "GOST28147_GCFB";
-static final String SEED_CBC = "SEED_CBC";
-static final String DES_EDE3_WRAP = "DES_EDE3_WRAP";
-static final String AES128_WRAP = "AES128_WRAP";
-static final String AES192_WRAP = "AES192_WRAP";
-static final String AES256_WRAP = "AES256_WRAP";
-static final String CAMELLIA128_WRAP = "CAMELLIA128_WRAP";
-static final String CAMELLIA192_WRAP = "CAMELLIA192_WRAP";
-static final String CAMELLIA256_WRAP = "CAMELLIA256_WRAP";
-static final String SEED_WRAP = "SEED_WRAP";
-static final String GOST28147_WRAP = "GOST28147_WRAP";
-static final String GOST28147_CRYPTOPRO_WRAP = "GOST28147_CRYPTOPRO_WRAP";
-static final String ECDH_SHA1KDF = "ECDH_SHA1KDF";
-static final String ECCDH_SHA1KDF = "ECCDH_SHA1KDF";
-static final String ECMQV_SHA1KDF = "ECMQV_SHA1KDF";
-static final String ECDH_SHA224KDF = "ECDH_SHA224KDF";
-static final String ECCDH_SHA224KDF = "ECCDH_SHA224KDF";
-static final String ECMQV_SHA224KDF = "ECMQV_SHA224KDF";
-static final String ECDH_SHA256KDF = "ECDH_SHA256KDF";
-static final String ECCDH_SHA256KDF = "ECCDH_SHA256KDF";
-static final String ECMQV_SHA256KDF = "ECMQV_SHA256KDF";
-static final String ECDH_SHA384KDF = "ECDH_SHA384KDF";
-static final String ECCDH_SHA384KDF = "ECCDH_SHA384KDF";
-static final String ECMQV_SHA384KDF = "ECMQV_SHA384KDF";
-static final String ECDH_SHA512KDF = "ECDH_SHA512KDF";
-static final String ECCDH_SHA512KDF = "ECCDH_SHA512KDF";
-static final String ECMQV_SHA512KDF = "ECMQV_SHA512KDF";
-static final String ECDHGOST3410_2001 = "ECDHGOST3410_2001";
-static final String ECDHGOST3410_2012_256 = "ECDHGOST3410_2012_256";
-static final String ECDHGOST3410_2012_512 = "ECDHGOST3410_2012_512";
-static final String SHA1 = "SHA1";
-static final String SHA224 = "SHA224";
-static final String SHA256 = "SHA256";
-static final String SHA384 = "SHA384";
-
[jira] [Updated] (CAMEL-12821) Fix MQTT URI param typo
[ https://issues.apache.org/jira/browse/CAMEL-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12821: Fix Version/s: 2.23.0 2.22.2 2.21.3 > Fix MQTT URI param typo > --- > > Key: CAMEL-12821 > URL: https://issues.apache.org/jira/browse/CAMEL-12821 > Project: Camel > Issue Type: Bug > Components: camel-mqtt >Affects Versions: 2.22.1 >Reporter: Philippe Schaller >Priority: Trivial > Fix For: 2.21.3, 2.22.2, 2.23.0 > > > The URI params 'willQos' and 'qualityOfService' of the MQTT component have a > typo in their enum description. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12821) Fix MQTT URI param typo
[ https://issues.apache.org/jira/browse/CAMEL-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12821. - Resolution: Fixed Assignee: Claus Ibsen Thanks for the PR > Fix MQTT URI param typo > --- > > Key: CAMEL-12821 > URL: https://issues.apache.org/jira/browse/CAMEL-12821 > Project: Camel > Issue Type: Bug > Components: camel-mqtt >Affects Versions: 2.22.1 >Reporter: Philippe Schaller >Assignee: Claus Ibsen >Priority: Trivial > Fix For: 2.21.3, 2.22.2, 2.23.0 > > > The URI params 'willQos' and 'qualityOfService' of the MQTT component have a > typo in their enum description. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12810) [IPFS] Add support for IPFS
[ https://issues.apache.org/jira/browse/CAMEL-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620202#comment-16620202 ] Thomas Diesler commented on CAMEL-12810: Yes, this comes transitively though [nessus|https://github.com/tdiesler/nessus], which is a larger IPFS + Blockchain effort. It is the foundation of this prototype ... [https://ipfs.io/ipfs/QmPEs1wGUi75us4Qdr1bxfF9czNy4fNy3n1752yRKhQVbz/trail/] The Camel component is ready and waiting on the nessus release. https://github.com/tdiesler/camel/tree/CAMEL-12810 > [IPFS] Add support for IPFS > --- > > Key: CAMEL-12810 > URL: https://issues.apache.org/jira/browse/CAMEL-12810 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > > https://ipfs.io/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12605) Enhance the AS2 Component to send and receive encrypted AS2 messages
[ https://issues.apache.org/jira/browse/CAMEL-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620227#comment-16620227 ] ASF GitHub Bot commented on CAMEL-12605: Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/2524 > Enhance the AS2 Component to send and receive encrypted AS2 messages > > > Key: CAMEL-12605 > URL: https://issues.apache.org/jira/browse/CAMEL-12605 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.23.0 >Reporter: William Collins >Assignee: William Collins >Priority: Major > > Enhance the AS2 Component to support encrypted AS2 messages per RFC4130 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
***UNCHECKED*** [jira] [Commented] (CAMEL-12605) Enhance the AS2 Component to send and receive encrypted AS2 messages
[ https://issues.apache.org/jira/browse/CAMEL-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620225#comment-16620225 ] ASF GitHub Bot commented on CAMEL-12605: oscerd commented on issue #2524: [CAMEL-12605] Refactored encryption algorithms and added tests for al… URL: https://github.com/apache/camel/pull/2524#issuecomment-422686937 Merged. Thanks @punkhorn This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > Enhance the AS2 Component to send and receive encrypted AS2 messages > > > Key: CAMEL-12605 > URL: https://issues.apache.org/jira/browse/CAMEL-12605 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.23.0 >Reporter: William Collins >Assignee: William Collins >Priority: Major > > Enhance the AS2 Component to support encrypted AS2 messages per RFC4130 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
