[jira] [Commented] (CAMEL-11658) URISyntaxException in RestletProducer
[
https://issues.apache.org/jira/browse/CAMEL-11658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469933#comment-16469933
]
ASF GitHub Bot commented on CAMEL-11658:
onderson commented on issue #1938: CAMEL-11658: test for RestletProducer
handling unencoded headers
URL: https://github.com/apache/camel/pull/1938#issuecomment-387953782
guys, any comment?
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
> URISyntaxException in RestletProducer
> -
>
> Key: CAMEL-11658
> URL: https://issues.apache.org/jira/browse/CAMEL-11658
> Project: Camel
> Issue Type: Bug
> Components: camel-restlet
>Affects Versions: 2.19.0
>Reporter: Anton Koscejev
>Priority: Minor
>
> CAMEL-10392 introduced session/cookie handling for camel-restlet. However,
> this also introduced a bug where new URI is created from resourceUri before
> it's encoded.
> Before this change the uri would be safely encoded within restlet's Request
> constructor.
> See this code in RestletProducer:
> {code}
> String resourceUri = buildUri(endpoint, exchange);
> URI uri = new URI(resourceUri); // <- causes exception on
> unencoded uri
> request = new Request(endpoint.getRestletMethod(), resourceUri);
> // <- will encode uri
> binding.populateRestletRequestFromExchange(request, exchange);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12494) spring-boot: use ApplicationContextRunner in spring-boot test to test AutoConfigurations
[ https://issues.apache.org/jira/browse/CAMEL-12494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469889#comment-16469889 ] Ramu kakarla commented on CAMEL-12494: --- looking > spring-boot: use ApplicationContextRunner in spring-boot test to test > AutoConfigurations > > > Key: CAMEL-12494 > URL: https://issues.apache.org/jira/browse/CAMEL-12494 > Project: Camel > Issue Type: Task > Components: camel-spring-boot, camel-spring-boot-starters >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 2.22.0 > > > We should migrate AutoConfigurations related test to use > ApplicationContextRunner, see: > https://spring.io/blog/2018/03/07/testing-auto-configurations-with-spring-boot-2-0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12501) Camel-Paho: add component verifier from Syndesis project
[ https://issues.apache.org/jira/browse/CAMEL-12501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12501. -- Resolution: Fixed > Camel-Paho: add component verifier from Syndesis project > > > Key: CAMEL-12501 > URL: https://issues.apache.org/jira/browse/CAMEL-12501 > Project: Camel > Issue Type: New Feature > Components: camel-paho >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.22.0 > > > Syndesis project aims to contribute some component verifiers upstream. > [https://github.com/syndesisio/syndesis/issues/2571] > A bunch of them are already in, I'm porting the mqtt/paho component verifier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12499) Spring Boot 2 - Quoting map keys no longer needed
[
https://issues.apache.org/jira/browse/CAMEL-12499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-12499:
--
Summary: Spring Boot 2 - Quoting map keys no longer needed (was: Quoting
map keys no longer needed)
> Spring Boot 2 - Quoting map keys no longer needed
> -
>
> Key: CAMEL-12499
> URL: https://issues.apache.org/jira/browse/CAMEL-12499
> Project: Camel
> Issue Type: Sub-task
> Components: camel-spring-boot-starters
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 2.22.0
>
>
> Spring Boot no longer requires that the map keys in the configuration
> properties are quoted, in 2.0 if the quotes are given they are taken
> literally. For example:
> {code:java}
> custom.map['key'] = value{code}
> populates the {{map}} property with key equal to {{"'key'"}}.
> The recommended way would be to use the dot notation, or in this example:
> {code:java}
> custom.map.key = value{code}
> The angle brackets syntax is supported and should work but users need to be
> aware that the content between the angle brackets is taken verbatim.
> There is a
> [test|https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/289/testReport/org.apache.camel.component.kubernetes.springboot.test.cluster/KubernetesClusterServiceAutoConfigurationTest/testPropertiesMapped/]
> in the {{camel-kubernetes-starter}} that failed on CI because of this change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12501) Camel-Paho: add component verifier from Syndesis project
Andrea Cosentino created CAMEL-12501: Summary: Camel-Paho: add component verifier from Syndesis project Key: CAMEL-12501 URL: https://issues.apache.org/jira/browse/CAMEL-12501 Project: Camel Issue Type: New Feature Components: camel-paho Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 2.22.0 Syndesis project aims to contribute some component verifiers upstream. [https://github.com/syndesisio/syndesis/issues/2571] A bunch of them are already in, I'm porting the mqtt/paho component verifier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (CAMEL-12499) Quoting map keys no longer needed
[
https://issues.apache.org/jira/browse/CAMEL-12499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-12499 started by Zoran Regvart.
-
> Quoting map keys no longer needed
> -
>
> Key: CAMEL-12499
> URL: https://issues.apache.org/jira/browse/CAMEL-12499
> Project: Camel
> Issue Type: Sub-task
> Components: camel-spring-boot-starters
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 2.22.0
>
>
> Spring Boot no longer requires that the map keys in the configuration
> properties are quoted, in 2.0 if the quotes are given they are taken
> literally. For example:
> {code:java}
> custom.map['key'] = value{code}
> populates the {{map}} property with key equal to {{"'key'"}}.
> The recommended way would be to use the dot notation, or in this example:
> {code:java}
> custom.map.key = value{code}
> The angle brackets syntax is supported and should work but users need to be
> aware that the content between the angle brackets is taken verbatim.
> There is a
> [test|https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/289/testReport/org.apache.camel.component.kubernetes.springboot.test.cluster/KubernetesClusterServiceAutoConfigurationTest/testPropertiesMapped/]
> in the {{camel-kubernetes-starter}} that failed on CI because of this change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12496) Spring Boot 2 - Fix Infinispan starter
[ https://issues.apache.org/jira/browse/CAMEL-12496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-12496: -- Summary: Spring Boot 2 - Fix Infinispan starter (was: Spring Boot 2: Fix Infinispan starter) > Spring Boot 2 - Fix Infinispan starter > -- > > Key: CAMEL-12496 > URL: https://issues.apache.org/jira/browse/CAMEL-12496 > Project: Camel > Issue Type: Sub-task > Components: camel-infinispan >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Fix For: 2.22.0 > > > One of the tests in Infinispan starter for Spring Boot indicates that a > Spring Boot 2.0 upgrade caused a regression. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12496) Spring Boot 2: Fix Infinispan starter
[ https://issues.apache.org/jira/browse/CAMEL-12496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-12496: -- Summary: Spring Boot 2: Fix Infinispan starter (was: Fix Infinispan starter) > Spring Boot 2: Fix Infinispan starter > - > > Key: CAMEL-12496 > URL: https://issues.apache.org/jira/browse/CAMEL-12496 > Project: Camel > Issue Type: Sub-task > Components: camel-infinispan >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Fix For: 2.22.0 > > > One of the tests in Infinispan starter for Spring Boot indicates that a > Spring Boot 2.0 upgrade caused a regression. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12500) Incorrect URL for AWS SQS queues
[
https://issues.apache.org/jira/browse/CAMEL-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468864#comment-16468864
]
ASF GitHub Bot commented on CAMEL-12500:
Github user oscerd closed the pull request at:
https://github.com/apache/camel/pull/2329
> Incorrect URL for AWS SQS queues
>
>
> Key: CAMEL-12500
> URL: https://issues.apache.org/jira/browse/CAMEL-12500
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
>Reporter: Craig
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 2.22.0
>
>
> There should be a . between the region and the host. The queueUrl is, for
> example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be
> {{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.
>
> This bug was caused by
> https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12500) Incorrect URL for AWS SQS queues
[
https://issues.apache.org/jira/browse/CAMEL-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468863#comment-16468863
]
ASF GitHub Bot commented on CAMEL-12500:
oscerd closed pull request #2329: CAMEL-12500: Add missing . between region and
host in SqsEndpoint
URL: https://github.com/apache/camel/pull/2329
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-aws/src/main/java/org/apache/camel/component/aws/sqs/SqsEndpoint.java
b/components/camel-aws/src/main/java/org/apache/camel/component/aws/sqs/SqsEndpoint.java
index 7f3ab4d203d..45067347daf 100644
---
a/components/camel-aws/src/main/java/org/apache/camel/component/aws/sqs/SqsEndpoint.java
+++
b/components/camel-aws/src/main/java/org/apache/camel/component/aws/sqs/SqsEndpoint.java
@@ -129,7 +129,7 @@ protected void doStart() throws Exception {
if (configuration.getRegion() != null &&
configuration.getQueueOwnerAWSAccountId() != null) {
String host = configuration.getAmazonAWSHost();
host = FileUtil.stripTrailingSeparator(host);
-queueUrl = "https://sqs.; + configuration.getRegion() + host +
"/"
+queueUrl = "https://sqs.; + configuration.getRegion() + "." +
host + "/"
+ configuration.getQueueOwnerAWSAccountId() + "/" +
configuration.getQueueName();
} else if (configuration.getQueueOwnerAWSAccountId() != null) {
GetQueueUrlRequest getQueueUrlRequest = new
GetQueueUrlRequest();
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
> Incorrect URL for AWS SQS queues
>
>
> Key: CAMEL-12500
> URL: https://issues.apache.org/jira/browse/CAMEL-12500
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
>Reporter: Craig
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 2.22.0
>
>
> There should be a . between the region and the host. The queueUrl is, for
> example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be
> {{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.
>
> This bug was caused by
> https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12500) Incorrect URL for AWS SQS queues
[
https://issues.apache.org/jira/browse/CAMEL-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-12500.
--
Resolution: Fixed
> Incorrect URL for AWS SQS queues
>
>
> Key: CAMEL-12500
> URL: https://issues.apache.org/jira/browse/CAMEL-12500
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
>Reporter: Craig
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 2.22.0
>
>
> There should be a . between the region and the host. The queueUrl is, for
> example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be
> {{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.
>
> This bug was caused by
> https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12500) Incorrect URL for AWS SQS queues
[
https://issues.apache.org/jira/browse/CAMEL-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-12500:
-
Affects Version/s: (was: 2.21.1)
(was: 2.21.0)
> Incorrect URL for AWS SQS queues
>
>
> Key: CAMEL-12500
> URL: https://issues.apache.org/jira/browse/CAMEL-12500
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
>Reporter: Craig
>Priority: Major
> Fix For: 2.22.0
>
>
> There should be a . between the region and the host. The queueUrl is, for
> example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be
> {{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.
>
> This bug was caused by
> https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-12500) Incorrect URL for AWS SQS queues
[
https://issues.apache.org/jira/browse/CAMEL-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-12500:
Assignee: Andrea Cosentino
> Incorrect URL for AWS SQS queues
>
>
> Key: CAMEL-12500
> URL: https://issues.apache.org/jira/browse/CAMEL-12500
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
>Reporter: Craig
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 2.22.0
>
>
> There should be a . between the region and the host. The queueUrl is, for
> example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be
> {{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.
>
> This bug was caused by
> https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12500) Incorrect URL for AWS SQS queues
[
https://issues.apache.org/jira/browse/CAMEL-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-12500:
-
Fix Version/s: 2.22.0
> Incorrect URL for AWS SQS queues
>
>
> Key: CAMEL-12500
> URL: https://issues.apache.org/jira/browse/CAMEL-12500
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
>Reporter: Craig
>Priority: Major
> Fix For: 2.22.0
>
>
> There should be a . between the region and the host. The queueUrl is, for
> example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be
> {{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.
>
> This bug was caused by
> https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12500) Incorrect URL for AWS SQS queues
[
https://issues.apache.org/jira/browse/CAMEL-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468843#comment-16468843
]
ASF GitHub Bot commented on CAMEL-12500:
oscerd commented on issue #2329: CAMEL-12500: Add missing . between region and
host in SqsEndpoint
URL: https://github.com/apache/camel/pull/2329#issuecomment-387741466
Thanks this has been merged on master
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
> Incorrect URL for AWS SQS queues
>
>
> Key: CAMEL-12500
> URL: https://issues.apache.org/jira/browse/CAMEL-12500
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
>Affects Versions: 2.21.0, 2.21.1
>Reporter: Craig
>Priority: Major
>
> There should be a . between the region and the host. The queueUrl is, for
> example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be
> {{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.
>
> This bug was caused by
> https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12500) Incorrect URL for AWS SQS queues
[
https://issues.apache.org/jira/browse/CAMEL-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-12500:
-
Affects Version/s: (was: 2.22.0)
2.21.1
2.21.0
> Incorrect URL for AWS SQS queues
>
>
> Key: CAMEL-12500
> URL: https://issues.apache.org/jira/browse/CAMEL-12500
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
>Affects Versions: 2.21.0, 2.21.1
>Reporter: Craig
>Priority: Major
>
> There should be a . between the region and the host. The queueUrl is, for
> example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be
> {{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.
>
> This bug was caused by
> https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12500) Incorrect URL for AWS SQS queues
[
https://issues.apache.org/jira/browse/CAMEL-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468833#comment-16468833
]
ASF GitHub Bot commented on CAMEL-12500:
oscerd commented on issue #2329: CAMEL-12500: Add missing . between region and
host in SqsEndpoint
URL: https://github.com/apache/camel/pull/2329#issuecomment-387737598
Thanks
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
> Incorrect URL for AWS SQS queues
>
>
> Key: CAMEL-12500
> URL: https://issues.apache.org/jira/browse/CAMEL-12500
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
>Affects Versions: 2.22.0
>Reporter: Craig
>Priority: Major
>
> There should be a . between the region and the host. The queueUrl is, for
> example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be
> {{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.
>
> This bug was caused by
> https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12500) Incorrect URL for AWS SQS queues
[
https://issues.apache.org/jira/browse/CAMEL-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468831#comment-16468831
]
ASF GitHub Bot commented on CAMEL-12500:
candrews commented on issue #2329: CAMEL-12500: Add missing . between region
and host in SqsEndpoint
URL: https://github.com/apache/camel/pull/2329#issuecomment-387736596
> We'll wait for the JIRA and the commit amend.
Done
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
> Incorrect URL for AWS SQS queues
>
>
> Key: CAMEL-12500
> URL: https://issues.apache.org/jira/browse/CAMEL-12500
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
>Affects Versions: 2.22.0
>Reporter: Craig
>Priority: Major
>
> There should be a . between the region and the host. The queueUrl is, for
> example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be
> {{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.
>
> This bug was caused by
> https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12499) Quoting map keys no longer needed
Zoran Regvart created CAMEL-12499:
-
Summary: Quoting map keys no longer needed
Key: CAMEL-12499
URL: https://issues.apache.org/jira/browse/CAMEL-12499
Project: Camel
Issue Type: Sub-task
Components: camel-spring-boot-starters
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Fix For: 2.22.0
Spring Boot no longer requires that the map keys in the configuration
properties are quoted, in 2.0 if the quotes are given they are taken literally.
For example:
{code:java}
custom.map['key'] = value{code}
populates the {{map}} property with key equal to {{"'key'"}}.
The recommended way would be to use the dot notation, or in this example:
{code:java}
custom.map.key = value{code}
The angle brackets syntax is supported and should work but users need to be
aware that the content between the angle brackets is taken verbatim.
There is a
[test|https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/289/testReport/org.apache.camel.component.kubernetes.springboot.test.cluster/KubernetesClusterServiceAutoConfigurationTest/testPropertiesMapped/]
in the {{camel-kubernetes-starter}} that failed on CI because of this change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12500) Incorrect URL for AWS SQS queues
Craig created CAMEL-12500:
-
Summary: Incorrect URL for AWS SQS queues
Key: CAMEL-12500
URL: https://issues.apache.org/jira/browse/CAMEL-12500
Project: Camel
Issue Type: Bug
Components: camel-aws
Affects Versions: 2.22.0
Reporter: Craig
There should be a . between the region and the host. The queueUrl is, for
example, {{https://sqs.sqs.us-gov-west-1amazonaws.com}} - it should be
{{https://sqs.sqs.us-gov-west-1.amazonaws.com}}.
This bug was caused by
https://github.com/apache/camel/commit/6bb9f5559145bfc1f9db6718192e86c2a09a4e07
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12498) One of the camel-jcache tests is failing
Zoran Regvart created CAMEL-12498: - Summary: One of the camel-jcache tests is failing Key: CAMEL-12498 URL: https://issues.apache.org/jira/browse/CAMEL-12498 Project: Camel Issue Type: Bug Components: camel-jcache Reporter: Zoran Regvart Assignee: Zoran Regvart Fix For: 2.22.0 Seems that one of camel-jcache tests started failing. [Test results|https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/289/testReport/org.apache.camel.component.jcache/JCacheConsumerTest/testFilters/] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (CAMEL-12498) One of the camel-jcache tests is failing
[ https://issues.apache.org/jira/browse/CAMEL-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-12498 started by Zoran Regvart. - > One of the camel-jcache tests is failing > > > Key: CAMEL-12498 > URL: https://issues.apache.org/jira/browse/CAMEL-12498 > Project: Camel > Issue Type: Bug > Components: camel-jcache >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Fix For: 2.22.0 > > > Seems that one of camel-jcache tests started failing. > [Test > results|https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/289/testReport/org.apache.camel.component.jcache/JCacheConsumerTest/testFilters/] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12497) Fix CXF-Blueprint tests
Zoran Regvart created CAMEL-12497:
-
Summary: Fix CXF-Blueprint tests
Key: CAMEL-12497
URL: https://issues.apache.org/jira/browse/CAMEL-12497
Project: Camel
Issue Type: Bug
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Fix For: 2.22.0
A number of tests in {{tests/camel-blueprint-cxf-test}} are failing on CI.
[Test
results|https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/289/testReport/]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work started] (CAMEL-12497) Fix CXF-Blueprint tests
[
https://issues.apache.org/jira/browse/CAMEL-12497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-12497 started by Zoran Regvart.
-
> Fix CXF-Blueprint tests
> ---
>
> Key: CAMEL-12497
> URL: https://issues.apache.org/jira/browse/CAMEL-12497
> Project: Camel
> Issue Type: Bug
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 2.22.0
>
>
> A number of tests in {{tests/camel-blueprint-cxf-test}} are failing on CI.
> [Test
> results|https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/289/testReport/]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work started] (CAMEL-12496) Fix Infinispan starter
[ https://issues.apache.org/jira/browse/CAMEL-12496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-12496 started by Zoran Regvart. - > Fix Infinispan starter > -- > > Key: CAMEL-12496 > URL: https://issues.apache.org/jira/browse/CAMEL-12496 > Project: Camel > Issue Type: Sub-task > Components: camel-infinispan >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Fix For: 2.22.0 > > > One of the tests in Infinispan starter for Spring Boot indicates that a > Spring Boot 2.0 upgrade caused a regression. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12496) Fix Infinispan starter
Zoran Regvart created CAMEL-12496: - Summary: Fix Infinispan starter Key: CAMEL-12496 URL: https://issues.apache.org/jira/browse/CAMEL-12496 Project: Camel Issue Type: Sub-task Components: camel-infinispan Reporter: Zoran Regvart Assignee: Zoran Regvart Fix For: 2.22.0 One of the tests in Infinispan starter for Spring Boot indicates that a Spring Boot 2.0 upgrade caused a regression. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12495) Camel-Slack: add component verifier from Syndesis project
[ https://issues.apache.org/jira/browse/CAMEL-12495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12495. -- Resolution: Fixed > Camel-Slack: add component verifier from Syndesis project > - > > Key: CAMEL-12495 > URL: https://issues.apache.org/jira/browse/CAMEL-12495 > Project: Camel > Issue Type: New Feature > Components: camel-slack >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.22.0 > > > Syndesis project aims to contribute some component verifiers upstream. > [https://github.com/syndesisio/syndesis/issues/2571] > A bunch of them are already in, I'm porting the slack component verifier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12495) Camel-Slack: add component verifier from Syndesis project
[ https://issues.apache.org/jira/browse/CAMEL-12495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-12495: - Fix Version/s: 2.22.0 > Camel-Slack: add component verifier from Syndesis project > - > > Key: CAMEL-12495 > URL: https://issues.apache.org/jira/browse/CAMEL-12495 > Project: Camel > Issue Type: New Feature > Components: camel-slack >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.22.0 > > > Syndesis project aims to contribute some component verifiers upstream. > [https://github.com/syndesisio/syndesis/issues/2571] > A bunch of them are already in, I'm porting the slack component verifier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12495) Camel-Slack: add component verifier from Syndesis project
Andrea Cosentino created CAMEL-12495: Summary: Camel-Slack: add component verifier from Syndesis project Key: CAMEL-12495 URL: https://issues.apache.org/jira/browse/CAMEL-12495 Project: Camel Issue Type: New Feature Components: camel-slack Reporter: Andrea Cosentino Assignee: Andrea Cosentino Syndesis project aims to contribute some component verifiers upstream. [https://github.com/syndesisio/syndesis/issues/2571] A bunch of them are already in, I'm porting the slack component verifier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12484) Camel-salesforce component does not try to reconnect on specific error
[
https://issues.apache.org/jira/browse/CAMEL-12484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468658#comment-16468658
]
Zoran Regvart commented on CAMEL-12484:
---
[~hemangajmera] can you provide details on how to reproduce this issue? I see
that you're getting a 403 error with unknown client, potentially in this case
until authentication information is updated reconnecting wont help.
> Camel-salesforce component does not try to reconnect on specific error
> --
>
> Key: CAMEL-12484
> URL: https://issues.apache.org/jira/browse/CAMEL-12484
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 2.21.0
>Reporter: Hemang Ajmera
>Priority: Major
>
> The issue is very much identical to CAMEL-10238 where camel component does
> not try to reconnect. It was resolved for that particular case, however there
> is additional scenario where we are facing exactly similar problem.
> Here is the key log message after which component stops retrying
> {{2018-05-03 17:19:50.257 WARN 7636 — [nt@911561694-23]
> o.a.c.c.s.i.s.SubscriptionHelper : Connect failure:
> {clientId=3qi3g4psrtqrntt15ockewu0a59q, advice=
> {reconnect=none, interval=0}
> , channel=/meta/connect, id=154, error=403::Unknown client,
> successful=false}}}
> Please note that we are getting Connect failure multiple times but it is able
> to reconnect where there is exception or when the advice is to do handshake
> again. Here are those sample which works...
> * The one with exceptions
> {quote}2018-05-03 17:19:17.965 WARN 7636 — [nt@911561694-23]
> o.a.c.c.s.i.s.SubscriptionHelper : Connect failure: {failure=
> Unknown macro: \{exception=java.io.EOFException}
> ],recv=HttpReceiverOverHTTP@144e8ebb(rsp=IDLE,failure=null)[HttpParser
> Unknown macro: \{s=CLOSED,0 of -1}
> ]]<-DecryptedEndPoint@245db684
> Unknown macro: \{telia-fi--dev.cs88.my.salesforce.com/85.222.137.144}
> ->HttpConnectionOverHTTP@69f41507(l:/0:0:0:0:0:0:0:1:60369 <->
> r:telia-fi--dev.cs88.my.salesforce.com/85.222.137.144:443,closed=false)=>HttpChannelOverHTTP@3109c579(exchange=HttpExchange@76b96e24
> req=TERMINATED/null@null
> res=PENDING/null@null)[send=HttpSenderOverHTTP@5d6efa04(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@43ac2f18
> Unknown macro: \{s=START}
> ],recv=HttpReceiverOverHTTP@144e8ebb(rsp=IDLE,failure=null)[HttpParser
> ]]->SocketChannelEndPoint@6b93b346
> Unknown macro: \{telia-fi--dev.cs88.my.salesforce.com/85.222.137.144}
> Unknown macro: \{io=0/0,kio=0,kro=1}
>
> ->SslConnection@53bc7193\{NEED_WRAP,eio=-1/-1,di=-1}=>HttpConnectionOverHTTP@69f41507(l:/0:0:0:0:0:0:0:1:60369
> <->
> r:telia-fi--dev.cs88.my.salesforce.com/85.222.137.144:443,closed=false)=>HttpChannelOverHTTP@3109c579(exchange=HttpExchange@76b96e24
> req=TERMINATED/null@null
> res=PENDING/null@null)[send=HttpSenderOverHTTP@5d6efa04(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@43ac2f18
> Unknown macro: \{s=START}
> ],recv=HttpReceiverOverHTTP@144e8ebb(rsp=IDLE,failure=null)[HttpParser
> Unknown macro: \{s=CLOSED,0 of -1}
> ]], message=\{clientId=3qi3g4psrtqrntt15ockewu0a59q, channel=/meta/connect,
> id=153, connectionType=long-polling}, connectionType=long-polling},
> channel=/meta/connect, id=153, successful=false}
> {quote}
>
> * The one with advice for new handshake
> {quote}2018-05-03 16:31:08.970 WARN 7636 — [nt@911561694-21]
> o.a.c.c.s.i.s.SubscriptionHelper : Connect failure:
> Unknown macro: \{advice=Unknown macro}
> , channel=/meta/connect, id=83, error=403::Unknown client, successful=false}
> {quote}
>
> One more thing, this log is coming from line 168 {{LOG.warn("Connect failure:
> {}", message);}} of the
> [https://github.com/apache/camel/blob/master/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/internal/streaming/SubscriptionHelper.java#L168].
> I see that there is no attempt to reconnect. If this information helps move
> things faster...
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12484) Camel-salesforce component does not try to reconnect on specific error
[
https://issues.apache.org/jira/browse/CAMEL-12484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468636#comment-16468636
]
Hemang Ajmera commented on CAMEL-12484:
---
[~dhirajsb], [~zregvart], can you please look into this one.
> Camel-salesforce component does not try to reconnect on specific error
> --
>
> Key: CAMEL-12484
> URL: https://issues.apache.org/jira/browse/CAMEL-12484
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 2.21.0
>Reporter: Hemang Ajmera
>Priority: Major
>
> The issue is very much identical to CAMEL-10238 where camel component does
> not try to reconnect. It was resolved for that particular case, however there
> is additional scenario where we are facing exactly similar problem.
> Here is the key log message after which component stops retrying
> {{2018-05-03 17:19:50.257 WARN 7636 — [nt@911561694-23]
> o.a.c.c.s.i.s.SubscriptionHelper : Connect failure:
> {clientId=3qi3g4psrtqrntt15ockewu0a59q, advice=
> {reconnect=none, interval=0}
> , channel=/meta/connect, id=154, error=403::Unknown client,
> successful=false}}}
> Please note that we are getting Connect failure multiple times but it is able
> to reconnect where there is exception or when the advice is to do handshake
> again. Here are those sample which works...
> * The one with exceptions
> {quote}2018-05-03 17:19:17.965 WARN 7636 — [nt@911561694-23]
> o.a.c.c.s.i.s.SubscriptionHelper : Connect failure: {failure=
> Unknown macro: \{exception=java.io.EOFException}
> ],recv=HttpReceiverOverHTTP@144e8ebb(rsp=IDLE,failure=null)[HttpParser
> Unknown macro: \{s=CLOSED,0 of -1}
> ]]<-DecryptedEndPoint@245db684
> Unknown macro: \{telia-fi--dev.cs88.my.salesforce.com/85.222.137.144}
> ->HttpConnectionOverHTTP@69f41507(l:/0:0:0:0:0:0:0:1:60369 <->
> r:telia-fi--dev.cs88.my.salesforce.com/85.222.137.144:443,closed=false)=>HttpChannelOverHTTP@3109c579(exchange=HttpExchange@76b96e24
> req=TERMINATED/null@null
> res=PENDING/null@null)[send=HttpSenderOverHTTP@5d6efa04(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@43ac2f18
> Unknown macro: \{s=START}
> ],recv=HttpReceiverOverHTTP@144e8ebb(rsp=IDLE,failure=null)[HttpParser
> ]]->SocketChannelEndPoint@6b93b346
> Unknown macro: \{telia-fi--dev.cs88.my.salesforce.com/85.222.137.144}
> Unknown macro: \{io=0/0,kio=0,kro=1}
>
> ->SslConnection@53bc7193\{NEED_WRAP,eio=-1/-1,di=-1}=>HttpConnectionOverHTTP@69f41507(l:/0:0:0:0:0:0:0:1:60369
> <->
> r:telia-fi--dev.cs88.my.salesforce.com/85.222.137.144:443,closed=false)=>HttpChannelOverHTTP@3109c579(exchange=HttpExchange@76b96e24
> req=TERMINATED/null@null
> res=PENDING/null@null)[send=HttpSenderOverHTTP@5d6efa04(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@43ac2f18
> Unknown macro: \{s=START}
> ],recv=HttpReceiverOverHTTP@144e8ebb(rsp=IDLE,failure=null)[HttpParser
> Unknown macro: \{s=CLOSED,0 of -1}
> ]], message=\{clientId=3qi3g4psrtqrntt15ockewu0a59q, channel=/meta/connect,
> id=153, connectionType=long-polling}, connectionType=long-polling},
> channel=/meta/connect, id=153, successful=false}
> {quote}
>
> * The one with advice for new handshake
> {quote}2018-05-03 16:31:08.970 WARN 7636 — [nt@911561694-21]
> o.a.c.c.s.i.s.SubscriptionHelper : Connect failure:
> Unknown macro: \{advice=Unknown macro}
> , channel=/meta/connect, id=83, error=403::Unknown client, successful=false}
> {quote}
>
> One more thing, this log is coming from line 168 {{LOG.warn("Connect failure:
> {}", message);}} of the
> [https://github.com/apache/camel/blob/master/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/internal/streaming/SubscriptionHelper.java#L168].
> I see that there is no attempt to reconnect. If this information helps move
> things faster...
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12478) camel-telegram - Allow use of custom keyboard
[ https://issues.apache.org/jira/browse/CAMEL-12478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468568#comment-16468568 ] ASF GitHub Bot commented on CAMEL-12478: oscerd commented on issue #2318: CAMEL-12478: Allow use of custom keyboard URL: https://github.com/apache/camel/pull/2318#issuecomment-387670017 Thanks, this has been merged on master. 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 > camel-telegram - Allow use of custom keyboard > - > > Key: CAMEL-12478 > URL: https://issues.apache.org/jira/browse/CAMEL-12478 > Project: Camel > Issue Type: New Feature > Components: camel-telegram >Reporter: Willian Antunes >Assignee: Andrea Cosentino >Priority: Major > Labels: features > Fix For: 2.22.0 > > Attachments: SNAG-0180.jpg > > > The component as we have nowadays does not support configuration of custom > keyboard, it only makes use of the standard one. > The method [sendMessage|https://core.telegram.org/bots/api#sendmessage] has > the field _reply_markup_ which allow the use of > [ReplyKeyboardMarkup|https://core.telegram.org/bots/api#replykeyboardmarkup] > to customize the standard keyboard. > Acceptance Criteria: > * Send message with custom keyboard to interact with the bot using its > buttons. > * Disable custom keyboard when is required during chat conversation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12478) camel-telegram - Allow use of custom keyboard
[
https://issues.apache.org/jira/browse/CAMEL-12478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468569#comment-16468569
]
ASF GitHub Bot commented on CAMEL-12478:
oscerd closed pull request #2318: CAMEL-12478: Allow use of custom keyboard
URL: https://github.com/apache/camel/pull/2318
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-telegram/src/main/docs/telegram-component.adoc
b/components/camel-telegram/src/main/docs/telegram-component.adoc
index b90f06c13e8..3ce6891e363 100644
--- a/components/camel-telegram/src/main/docs/telegram-component.adoc
+++ b/components/camel-telegram/src/main/docs/telegram-component.adoc
@@ -310,3 +310,60 @@
to("telegram:bots/123456789:AAE_dLq5C19xwGjw3yiC2NvEUrZcejK21-Q987654321:AAE_dLq
-
Note that the corresponding URI parameter is simply `chatId`.
+
+### Customizing keyboard
+
+You can customize the user keyboard instead of asking him to write an option.
`OutgoingTextMessage` has the property `ReplyKeyboardMarkup` which can be used
for such thing.
+
+[source,java]
+-
+from("telegram:bots/123456789:AAE_dLq5C19xwGjw3yiC2NvEUrZcejK21-Q987654321:AAE_dLq5C19xwOmg5yiC2NvSrkT3wj5Q1-L")
+.process(exchange -> {
+
+OutgoingTextMessage msg = new OutgoingTextMessage();
+msg.setText("Choose one option!");
+
+InlineKeyboardButton buttonOptionOneI = InlineKeyboardButton.builder()
+.text("Option One - I").build();
+
+InlineKeyboardButton buttonOptionOneII = InlineKeyboardButton.builder()
+.text("Option One - II").build();
+
+InlineKeyboardButton buttonOptionTwoI = InlineKeyboardButton.builder()
+.text("Option Two - I").build();
+
+ReplyKeyboardMarkup replyMarkup = ReplyKeyboardMarkup.builder()
+.keyboard()
+.addRow(Arrays.asList(buttonOptionOneI, buttonOptionOneII))
+.addRow(Arrays.asList(buttonOptionTwoI))
+.close()
+.oneTimeKeyboard(true)
+.build();
+
+msg.setReplyKeyboardMarkup(replyMarkup);
+
+exchange.getIn().setBody(msg);
+})
+
.to("telegram:bots/123456789:AAE_dLq5C19xwGjw3yiC2NvEUrZcejK21-Q987654321:AAE_dLq5C19xwOmg5yiC2NvSrkT3wj5Q1-L");
+-
+
+If you want to disable it the next message must have the property
`removeKeyboard` set on `ReplyKeyboardMarkup` object.
+
+[source,java]
+-
+from("telegram:bots/123456789:AAE_dLq5C19xwGjw3yiC2NvEUrZcejK21-Q987654321:AAE_dLq5C19xwOmg5yiC2NvSrkT3wj5Q1-L")
+.process(exchange -> {
+
+OutgoingTextMessage msg = new OutgoingTextMessage();
+msg.setText("Your answer was accepted!");
+
+ReplyKeyboardMarkup replyMarkup = ReplyKeyboardMarkup.builder()
+.removeKeyboard(true)
+.build();
+
+msg.setReplyKeyboardMarkup(replyMarkup);
+
+exchange.getIn().setBody(msg);
+})
+
.to("telegram:bots/123456789:AAE_dLq5C19xwGjw3yiC2NvEUrZcejK21-Q987654321:AAE_dLq5C19xwOmg5yiC2NvSrkT3wj5Q1-L");
+-
\ No newline at end of file
diff --git
a/components/camel-telegram/src/main/java/org/apache/camel/component/telegram/model/InlineKeyboardButton.java
b/components/camel-telegram/src/main/java/org/apache/camel/component/telegram/model/InlineKeyboardButton.java
new file mode 100644
index 000..f3f2b4fa9f9
--- /dev/null
+++
b/components/camel-telegram/src/main/java/org/apache/camel/component/telegram/model/InlineKeyboardButton.java
@@ -0,0 +1,69 @@
+/**
+ * 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
[jira] [Commented] (CAMEL-12478) camel-telegram - Allow use of custom keyboard
[ https://issues.apache.org/jira/browse/CAMEL-12478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468570#comment-16468570 ] ASF GitHub Bot commented on CAMEL-12478: Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/2318 > camel-telegram - Allow use of custom keyboard > - > > Key: CAMEL-12478 > URL: https://issues.apache.org/jira/browse/CAMEL-12478 > Project: Camel > Issue Type: New Feature > Components: camel-telegram >Reporter: Willian Antunes >Assignee: Andrea Cosentino >Priority: Major > Labels: features > Fix For: 2.22.0 > > Attachments: SNAG-0180.jpg > > > The component as we have nowadays does not support configuration of custom > keyboard, it only makes use of the standard one. > The method [sendMessage|https://core.telegram.org/bots/api#sendmessage] has > the field _reply_markup_ which allow the use of > [ReplyKeyboardMarkup|https://core.telegram.org/bots/api#replykeyboardmarkup] > to customize the standard keyboard. > Acceptance Criteria: > * Send message with custom keyboard to interact with the bot using its > buttons. > * Disable custom keyboard when is required during chat conversation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12478) camel-telegram - Allow use of custom keyboard
[ https://issues.apache.org/jira/browse/CAMEL-12478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12478. -- Resolution: Fixed > camel-telegram - Allow use of custom keyboard > - > > Key: CAMEL-12478 > URL: https://issues.apache.org/jira/browse/CAMEL-12478 > Project: Camel > Issue Type: New Feature > Components: camel-telegram >Reporter: Willian Antunes >Assignee: Andrea Cosentino >Priority: Major > Labels: features > Fix For: 2.22.0 > > Attachments: SNAG-0180.jpg > > > The component as we have nowadays does not support configuration of custom > keyboard, it only makes use of the standard one. > The method [sendMessage|https://core.telegram.org/bots/api#sendmessage] has > the field _reply_markup_ which allow the use of > [ReplyKeyboardMarkup|https://core.telegram.org/bots/api#replykeyboardmarkup] > to customize the standard keyboard. > Acceptance Criteria: > * Send message with custom keyboard to interact with the bot using its > buttons. > * Disable custom keyboard when is required during chat conversation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12478) camel-telegram - Allow use of custom keyboard
[ https://issues.apache.org/jira/browse/CAMEL-12478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-12478: Assignee: Andrea Cosentino > camel-telegram - Allow use of custom keyboard > - > > Key: CAMEL-12478 > URL: https://issues.apache.org/jira/browse/CAMEL-12478 > Project: Camel > Issue Type: New Feature > Components: camel-telegram >Reporter: Willian Antunes >Assignee: Andrea Cosentino >Priority: Major > Labels: features > Fix For: 2.22.0 > > Attachments: SNAG-0180.jpg > > > The component as we have nowadays does not support configuration of custom > keyboard, it only makes use of the standard one. > The method [sendMessage|https://core.telegram.org/bots/api#sendmessage] has > the field _reply_markup_ which allow the use of > [ReplyKeyboardMarkup|https://core.telegram.org/bots/api#replykeyboardmarkup] > to customize the standard keyboard. > Acceptance Criteria: > * Send message with custom keyboard to interact with the bot using its > buttons. > * Disable custom keyboard when is required during chat conversation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12478) camel-telegram - Allow use of custom keyboard
[ https://issues.apache.org/jira/browse/CAMEL-12478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-12478: - Fix Version/s: 2.22.0 > camel-telegram - Allow use of custom keyboard > - > > Key: CAMEL-12478 > URL: https://issues.apache.org/jira/browse/CAMEL-12478 > Project: Camel > Issue Type: New Feature > Components: camel-telegram >Reporter: Willian Antunes >Assignee: Andrea Cosentino >Priority: Major > Labels: features > Fix For: 2.22.0 > > Attachments: SNAG-0180.jpg > > > The component as we have nowadays does not support configuration of custom > keyboard, it only makes use of the standard one. > The method [sendMessage|https://core.telegram.org/bots/api#sendmessage] has > the field _reply_markup_ which allow the use of > [ReplyKeyboardMarkup|https://core.telegram.org/bots/api#replykeyboardmarkup] > to customize the standard keyboard. > Acceptance Criteria: > * Send message with custom keyboard to interact with the bot using its > buttons. > * Disable custom keyboard when is required during chat conversation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
