[jira] [Created] (CAMEL-12963) camel-salesforce-maven-plugin generates code that does not compile
Boris Daich created CAMEL-12963:
---
Summary: camel-salesforce-maven-plugin generates code that does
not compile
Key: CAMEL-12963
URL: https://issues.apache.org/jira/browse/CAMEL-12963
Project: Camel
Issue Type: Bug
Components: camel-salesforce
Affects Versions: 2.22.2
Environment: windows 10 64bit Pro
Java 10 same with Java 8
Reporter: Boris Daich
when running pom.xml with
{code:java}
org.apache.camel.maven
camel-salesforce-maven-plugin
2.22.2
camel-sforce
generate-sources
generate
${project.basedir}/src/main/java
44.0
${my.clientId}
${my.clientSecret}
${my.username}
${my.password}
${my.loginUrl}
com.my.entities4camel
Task
{code}
the generated code does not compile because of the code like
{code:java}
private Account_Lookup What;
@JsonProperty("What")
public Account_Lookup getWhat() {
return this.What;
}
@JsonProperty("What")
public void setWhat(Account_Lookup What) {
this.What = What;
}
private rtms__CarrierPayment__c_Lookup What;
@JsonProperty("What")
public rtms__CarrierPayment__c_Lookup getWhat() {
return this.What;
}
@JsonProperty("What")
public void setWhat(rtms__CarrierPayment__c_Lookup What) {
this.What = What;
}
{code}
it seems that any field that has Salesforce "polymorphism" (able to reference
any type of Entity) causes the issue.
{{Task}} just simplest example.
Another thing that might be important: I run on top of an installed package the
fields with prefix {{rtms__}} are from the managed package.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12962) Allow from and size for SearchSource / SearchRequest to be set via URI
[ https://issues.apache.org/jira/browse/CAMEL-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek White updated CAMEL-12962: Description: There is currently no straightforward way that I know of to request more than the first 10 search results. Please allow from and size for SearchSource / SearchRequest to be set via URI. To add, since the ElasticsearchActionRequestConverter actually pulls the root node of the Query DSL, setting from and size in the request body string or Map is actually ignored. was:There is currently no straightforward way that I know of to request more than the first 10 search results. Please allow from and size for SearchSource / SearchRequest to be set via URI. > Allow from and size for SearchSource / SearchRequest to be set via URI > -- > > Key: CAMEL-12962 > URL: https://issues.apache.org/jira/browse/CAMEL-12962 > Project: Camel > Issue Type: Improvement > Components: camel-elasticsearch-rest >Affects Versions: 2.22.1 >Reporter: Derek White >Priority: Minor > > There is currently no straightforward way that I know of to request more than > the first 10 search results. Please allow from and size for SearchSource / > SearchRequest to be set via URI. > To add, since the ElasticsearchActionRequestConverter actually pulls the root > node of the Query DSL, setting from and size in the request body string or > Map is actually ignored. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12919) Camel AWS-SQS: Creating Amazon SQS Queue with Server-Side Encryption
[ https://issues.apache.org/jira/browse/CAMEL-12919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-12919: Assignee: Andrea Cosentino > Camel AWS-SQS: Creating Amazon SQS Queue with Server-Side Encryption > > > Key: CAMEL-12919 > URL: https://issues.apache.org/jira/browse/CAMEL-12919 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > > Amazon SQS Queues can be created with Server-Side Encryption. The two > attributes that exists to set that up are KmsMasterKeyId and > KmsDataKeyReusePeriodSeconds -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12958) Wrong camel context bound in service registry of jbpm/Kie Server
[ https://issues.apache.org/jira/browse/CAMEL-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12958. -- Resolution: Fixed > Wrong camel context bound in service registry of jbpm/Kie Server > > > Key: CAMEL-12958 > URL: https://issues.apache.org/jira/browse/CAMEL-12958 > Project: Camel > Issue Type: Bug > Components: camel-jbpm >Affects Versions: 2.23.0 >Reporter: Maciej Swiderski >Assignee: Maciej Swiderski >Priority: Major > Fix For: 2.24.0, 2.23.1 > > > Wrong camel context is set in the ServiceRegistry of jBPM when creating kie > container specific camel context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12962) Allow from and size for SearchSource / SearchRequest to be set via URI
Derek White created CAMEL-12962: --- Summary: Allow from and size for SearchSource / SearchRequest to be set via URI Key: CAMEL-12962 URL: https://issues.apache.org/jira/browse/CAMEL-12962 Project: Camel Issue Type: Improvement Components: camel-elasticsearch-rest Affects Versions: 2.22.1 Reporter: Derek White There is currently no straightforward way that I know of to request more than the first 10 search results. Please allow from and size for SearchSource / SearchRequest to be set via URI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12948) Download file version
[ https://issues.apache.org/jira/browse/CAMEL-12948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700696#comment-16700696 ] Vladimir commented on CAMEL-12948: -- I think there is problem with the mapping. BoxFileMenagerApiMethod have property : DOWNLOADPREVIOUSFILEVERSION with atribute "downloadPreviousFileVersion" BoxApiCollection creates map with endpoint names and instead of downloadPreviousFileVersion it adds downloadPreviousFileVersions (plural) to the map. > Download file version > - > > Key: CAMEL-12948 > URL: https://issues.apache.org/jira/browse/CAMEL-12948 > Project: Camel > Issue Type: Bug > Components: camel-box >Affects Versions: 2.22.1 >Reporter: Vladimir >Priority: Major > > Provided endpoint is not functional. > Exception : Failed to resolve endpoint: box://files/downloadVersion due to: > No matching method for files/downloadVersion, with arguments []. > The issue is explained here : > [http://camel.465427.n5.nabble.com/Camel-box-download-file-version-td5825974.html] > > -- 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=16700672#comment-16700672
]
ASF GitHub Bot commented on CAMEL-12605:
oscerd closed pull request #2639: [CAMEL-12605] Added support for compression
URL: https://github.com/apache/camel/pull/2639
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/entity/ApplicationPkcs7MimeCompressedDataEntity.java
b/components/camel-as2/camel-as2-api/src/main/java/org/apache/camel/component/as2/api/entity/ApplicationPkcs7MimeCompressedDataEntity.java
new file mode 100644
index 000..7a88761f3a3
--- /dev/null
+++
b/components/camel-as2/camel-as2-api/src/main/java/org/apache/camel/component/as2/api/entity/ApplicationPkcs7MimeCompressedDataEntity.java
@@ -0,0 +1,120 @@
+/**
+ * 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.entity;
+
+import java.io.ByteArrayOutputStream;
+import java.io.IOException;
+import java.io.OutputStream;
+
+import org.apache.camel.component.as2.api.AS2Charset;
+import org.apache.camel.component.as2.api.AS2Header;
+import org.apache.camel.component.as2.api.CanonicalOutputStream;
+import org.apache.camel.component.as2.api.util.EntityUtils;
+import org.apache.http.Header;
+import org.apache.http.HeaderIterator;
+import org.apache.http.HttpException;
+import org.apache.http.entity.ContentType;
+import org.apache.http.message.BasicNameValuePair;
+import org.apache.http.util.Args;
+import org.bouncycastle.cms.CMSCompressedData;
+import org.bouncycastle.cms.CMSCompressedDataGenerator;
+import org.bouncycastle.cms.CMSProcessableByteArray;
+import org.bouncycastle.cms.CMSTypedData;
+import org.bouncycastle.operator.InputExpanderProvider;
+import org.bouncycastle.operator.OutputCompressor;
+
+public class ApplicationPkcs7MimeCompressedDataEntity extends MimeEntity {
+
+private static final String CONTENT_DISPOSITION = "attachment;
filename=\"smime.p7z\"";
+
+private byte[] compressedData;
+
+public ApplicationPkcs7MimeCompressedDataEntity(MimeEntity entity2Encrypt,
+CMSCompressedDataGenerator
dataGenerator,
+OutputCompressor
compressor,
+String
compressedContentTransferEncoding,
+boolean isMainBody)
+throws HttpException {
+setContentType(ContentType.create("application/pkcs7-mime", new
BasicNameValuePair("smime-type", "compressed-data"),
+new BasicNameValuePair("name", "smime.p7z")));
+setContentTransferEncoding(compressedContentTransferEncoding);
+addHeader(AS2Header.CONTENT_DISPOSITION, CONTENT_DISPOSITION);
+setMainBody(isMainBody);
+try {
+this.compressedData = createCompressedData(entity2Encrypt,
dataGenerator, compressor);
+} catch (Exception e) {
+throw new HttpException("Failed to create encrypted data");
+}
+}
+
+public ApplicationPkcs7MimeCompressedDataEntity(byte[] compressedData,
String compressedContentTransferEncoding, boolean isMainBody) {
+this.compressedData = Args.notNull(compressedData, "encryptedData");
+
+setContentType(ContentType.create("application/pkcs7-mime", new
BasicNameValuePair("smime-type", "compressed-datat"),
+new BasicNameValuePair("name", "smime.p7z")));
+setContentTransferEncoding(compressedContentTransferEncoding);
+addHeader(AS2Header.CONTENT_DISPOSITION, CONTENT_DISPOSITION);
+setMainBody(isMainBody);
+}
+
+@Override
+public void writeTo(OutputStream outstream) throws IOException {
+NoCloseOutputStream ncos = new
[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=16700671#comment-16700671 ] ASF GitHub Bot commented on CAMEL-12605: oscerd commented on issue #2639: [CAMEL-12605] Added support for compression URL: https://github.com/apache/camel/pull/2639#issuecomment-442123446 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)
[jira] [Updated] (CAMEL-12961) Support Transactions
[ https://issues.apache.org/jira/browse/CAMEL-12961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J Jenkins updated CAMEL-12961: -- Description: As of 0.11, Kafka supports transnational semantics. Also, Spring has introduced a transaction manager for Kafka (under spring-kafka). Being able to transactionally consume and produce messages (within kafka) or consume/produce to some other system (jms,database,etc.) within Camel would be very useful. (was: The current implementation of camel-kafka is coded to use consumer.subscribe. This tends to be the default for most Kafka consumer use-cases, however, there are times when you may not want some of the features that come with subscription (such as automatic re-balancing). Kafka allows for more control in this situations by using the consumer.assign api. Would be great if we can extend camel-kafka to pass in some additional flags and required fields for using assign instead of subscribe.) > Support Transactions > > > Key: CAMEL-12961 > URL: https://issues.apache.org/jira/browse/CAMEL-12961 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: J Jenkins >Priority: Minor > Fix For: Future > > > As of 0.11, Kafka supports transnational semantics. Also, Spring has > introduced a transaction manager for Kafka (under spring-kafka). Being able > to transactionally consume and produce messages (within kafka) or > consume/produce to some other system (jms,database,etc.) within Camel would > be very useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12961) Support Transactions
J Jenkins created CAMEL-12961: - Summary: Support Transactions Key: CAMEL-12961 URL: https://issues.apache.org/jira/browse/CAMEL-12961 Project: Camel Issue Type: New Feature Components: camel-kafka Reporter: J Jenkins Fix For: Future The current implementation of camel-kafka is coded to use consumer.subscribe. This tends to be the default for most Kafka consumer use-cases, however, there are times when you may not want some of the features that come with subscription (such as automatic re-balancing). Kafka allows for more control in this situations by using the consumer.assign api. Would be great if we can extend camel-kafka to pass in some additional flags and required fields for using assign instead of subscribe. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11541) Telegram Button / Keyboard / Position
[ https://issues.apache.org/jira/browse/CAMEL-11541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700526#comment-16700526 ] VINEET GANDHI commented on CAMEL-11541: --- Hi Camel team, Has some one started working on this? I wanted to contribute and found this in Contributing.md link as starter bug. Should I start working on this? > Telegram Button / Keyboard / Position > - > > Key: CAMEL-11541 > URL: https://issues.apache.org/jira/browse/CAMEL-11541 > Project: Camel > Issue Type: Improvement > Components: camel-telegram >Reporter: Fabrizio Spataro >Priority: Minor > > Telegram component manage a basic type of message (text, video, image, audio) > but there are any functionalities not implemeted yet. > For example: Keyboards, buttons, Positions (lat/lon) etc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12951) Camel-AHC-WS: reconnect exception is not passed to exception handler
[
https://issues.apache.org/jira/browse/CAMEL-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-12951:
-
Fix Version/s: 2.24.0
> Camel-AHC-WS: reconnect exception is not passed to exception handler
>
>
> Key: CAMEL-12951
> URL: https://issues.apache.org/jira/browse/CAMEL-12951
> Project: Camel
> Issue Type: Bug
> Components: camel-ahc-ws
>Affects Versions: 2.22.2
>Reporter: Jukka Aalto
>Priority: Minor
> Fix For: 2.24.0
>
>
> When WsEndPoint reconnect-method fails in line 172 to create connection it
> throws an exception which is logged but it should also be given to exception
> handler.
> This kind of situation happens when server is shut down while connection is
> open. First client tries to reconnect but when reconnect fails, client stops
> trying.
> I'm trying to implement a feature which tries continuously to reconnect to
> server when the server is down. Connection state (open, disconnected or
> trying to connect) should also be indicated.
> If exception is passed to exception handler then it would be possible to
> register exception handler outside Camel. The purpose of this exception
> handler is to shut down Camel context and recreate it again in order to
> reconnect. With this kind of setup I can continuously try to reconnect and
> also figure out the current connection state.
>
> [https://github.com/apache/camel/blob/master/components/camel-ahc-ws/src/main/java/org/apache/camel/component/ahc/ws/WsEndpoint.java]
>
> {code:java}
> @Override
> public void onClose(WebSocket websocket, int code, String reason) {
>LOG.debug("websocket closed - reconnecting");
>try {
> reConnect();
>} catch (Exception e) {
> LOG.warn("Error re-connecting to websocket", e);
>}
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12958) Wrong camel context bound in service registry of jbpm/Kie Server
[
https://issues.apache.org/jira/browse/CAMEL-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700182#comment-16700182
]
ASF GitHub Bot commented on CAMEL-12958:
oscerd closed pull request #2637: CAMEL-12958 - Wrong camel context bound in
service registry of jbpm/K…
URL: https://github.com/apache/camel/pull/2637
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-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java
b/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java
index fbc4448d59c..0e297bece0f 100644
---
a/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java
+++
b/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java
@@ -117,7 +117,7 @@ public void createContainer(String id, KieContainerInstance
kieContainerInstance
context.start();
camelContexts.put(id, context);
-ServiceRegistry.get().register(id + "_CamelService",
this.camel);
+ServiceRegistry.get().register(id + "_CamelService", context);
}
} catch (Exception e) {
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
> Wrong camel context bound in service registry of jbpm/Kie Server
>
>
> Key: CAMEL-12958
> URL: https://issues.apache.org/jira/browse/CAMEL-12958
> Project: Camel
> Issue Type: Bug
> Components: camel-jbpm
>Affects Versions: 2.23.0
>Reporter: Maciej Swiderski
>Assignee: Maciej Swiderski
>Priority: Major
> Fix For: 2.24.0, 2.23.1
>
>
> Wrong camel context is set in the ServiceRegistry of jBPM when creating kie
> container specific camel context.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12958) Wrong camel context bound in service registry of jbpm/Kie Server
[ https://issues.apache.org/jira/browse/CAMEL-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-12958: - Fix Version/s: 2.24.0 2.23.1 > Wrong camel context bound in service registry of jbpm/Kie Server > > > Key: CAMEL-12958 > URL: https://issues.apache.org/jira/browse/CAMEL-12958 > Project: Camel > Issue Type: Bug > Components: camel-jbpm >Affects Versions: 2.23.0 >Reporter: Maciej Swiderski >Assignee: Maciej Swiderski >Priority: Major > Fix For: 2.24.0, 2.23.1 > > > Wrong camel context is set in the ServiceRegistry of jBPM when creating kie > container specific camel context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12958) Wrong camel context bound in service registry of jbpm/Kie Server
[ https://issues.apache.org/jira/browse/CAMEL-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700181#comment-16700181 ] ASF GitHub Bot commented on CAMEL-12958: oscerd commented on issue #2637: CAMEL-12958 - Wrong camel context bound in service registry of jbpm/K… URL: https://github.com/apache/camel/pull/2637#issuecomment-442006129 Pushed on master and 2.23.x, thanks @mswiderski 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 > Wrong camel context bound in service registry of jbpm/Kie Server > > > Key: CAMEL-12958 > URL: https://issues.apache.org/jira/browse/CAMEL-12958 > Project: Camel > Issue Type: Bug > Components: camel-jbpm >Affects Versions: 2.23.0 >Reporter: Maciej Swiderski >Assignee: Maciej Swiderski >Priority: Major > Fix For: 2.24.0, 2.23.1 > > > Wrong camel context is set in the ServiceRegistry of jBPM when creating kie > container specific camel context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12958) Wrong camel context bound in service registry of jbpm/Kie Server
[ https://issues.apache.org/jira/browse/CAMEL-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700178#comment-16700178 ] ASF GitHub Bot commented on CAMEL-12958: mswiderski commented on issue #2637: CAMEL-12958 - Wrong camel context bound in service registry of jbpm/K… URL: https://github.com/apache/camel/pull/2637#issuecomment-442005974 sounds good, 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 > Wrong camel context bound in service registry of jbpm/Kie Server > > > Key: CAMEL-12958 > URL: https://issues.apache.org/jira/browse/CAMEL-12958 > Project: Camel > Issue Type: Bug > Components: camel-jbpm >Affects Versions: 2.23.0 >Reporter: Maciej Swiderski >Assignee: Maciej Swiderski >Priority: Major > Fix For: 2.24.0, 2.23.1 > > > Wrong camel context is set in the ServiceRegistry of jBPM when creating kie > container specific camel context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12958) Wrong camel context bound in service registry of jbpm/Kie Server
[ https://issues.apache.org/jira/browse/CAMEL-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700177#comment-16700177 ] ASF GitHub Bot commented on CAMEL-12958: oscerd commented on issue #2637: CAMEL-12958 - Wrong camel context bound in service registry of jbpm/K… URL: https://github.com/apache/camel/pull/2637#issuecomment-442005440 It's under vote, it will be in 2.23.1 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 > Wrong camel context bound in service registry of jbpm/Kie Server > > > Key: CAMEL-12958 > URL: https://issues.apache.org/jira/browse/CAMEL-12958 > Project: Camel > Issue Type: Bug > Components: camel-jbpm >Affects Versions: 2.23.0 >Reporter: Maciej Swiderski >Assignee: Maciej Swiderski >Priority: Major > Fix For: 2.24.0, 2.23.1 > > > Wrong camel context is set in the ServiceRegistry of jBPM when creating kie > container specific camel context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12958) Wrong camel context bound in service registry of jbpm/Kie Server
[ https://issues.apache.org/jira/browse/CAMEL-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700175#comment-16700175 ] ASF GitHub Bot commented on CAMEL-12958: mswiderski commented on issue #2637: CAMEL-12958 - Wrong camel context bound in service registry of jbpm/K… URL: https://github.com/apache/camel/pull/2637#issuecomment-442005294 I see that pom.xml is still pointing to 2.23.0-SNAPSHOT so was wondering if this has any chance to be in 2.23.0 release or is it too late? 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 > Wrong camel context bound in service registry of jbpm/Kie Server > > > Key: CAMEL-12958 > URL: https://issues.apache.org/jira/browse/CAMEL-12958 > Project: Camel > Issue Type: Bug > Components: camel-jbpm >Affects Versions: 2.23.0 >Reporter: Maciej Swiderski >Assignee: Maciej Swiderski >Priority: Major > > Wrong camel context is set in the ServiceRegistry of jBPM when creating kie > container specific camel context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12954) Add a camel-websocket component 100% using only JSR356
[ https://issues.apache.org/jira/browse/CAMEL-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700169#comment-16700169 ] ASF GitHub Bot commented on CAMEL-12954: oscerd commented on issue #2631: CAMEL-12954 adding camel-websocket-jsr356 module URL: https://github.com/apache/camel/pull/2631#issuecomment-442004053 I'll take a look this week :-) 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 > Add a camel-websocket component 100% using only JSR356 > -- > > Key: CAMEL-12954 > URL: https://issues.apache.org/jira/browse/CAMEL-12954 > Project: Camel > Issue Type: New Feature >Reporter: Romain Manni-Bucau >Priority: Major > Fix For: Future > > > Goal is to rely on the standard javax specification and not require to setup > Atmosphere in containers which now support it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work stopped] (CAMEL-12951) Camel-AHC-WS: reconnect exception is not passed to exception handler
[
https://issues.apache.org/jira/browse/CAMEL-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-12951 stopped by Andrea Cosentino.
> Camel-AHC-WS: reconnect exception is not passed to exception handler
>
>
> Key: CAMEL-12951
> URL: https://issues.apache.org/jira/browse/CAMEL-12951
> Project: Camel
> Issue Type: Bug
> Components: camel-ahc-ws
>Affects Versions: 2.22.2
>Reporter: Jukka Aalto
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.24.0
>
>
> When WsEndPoint reconnect-method fails in line 172 to create connection it
> throws an exception which is logged but it should also be given to exception
> handler.
> This kind of situation happens when server is shut down while connection is
> open. First client tries to reconnect but when reconnect fails, client stops
> trying.
> I'm trying to implement a feature which tries continuously to reconnect to
> server when the server is down. Connection state (open, disconnected or
> trying to connect) should also be indicated.
> If exception is passed to exception handler then it would be possible to
> register exception handler outside Camel. The purpose of this exception
> handler is to shut down Camel context and recreate it again in order to
> reconnect. With this kind of setup I can continuously try to reconnect and
> also figure out the current connection state.
>
> [https://github.com/apache/camel/blob/master/components/camel-ahc-ws/src/main/java/org/apache/camel/component/ahc/ws/WsEndpoint.java]
>
> {code:java}
> @Override
> public void onClose(WebSocket websocket, int code, String reason) {
>LOG.debug("websocket closed - reconnecting");
>try {
> reConnect();
>} catch (Exception e) {
> LOG.warn("Error re-connecting to websocket", e);
>}
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-12951) Camel-AHC-WS: reconnect exception is not passed to exception handler
[
https://issues.apache.org/jira/browse/CAMEL-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-12951:
Assignee: Andrea Cosentino
> Camel-AHC-WS: reconnect exception is not passed to exception handler
>
>
> Key: CAMEL-12951
> URL: https://issues.apache.org/jira/browse/CAMEL-12951
> Project: Camel
> Issue Type: Bug
> Components: camel-ahc-ws
>Affects Versions: 2.22.2
>Reporter: Jukka Aalto
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.24.0
>
>
> When WsEndPoint reconnect-method fails in line 172 to create connection it
> throws an exception which is logged but it should also be given to exception
> handler.
> This kind of situation happens when server is shut down while connection is
> open. First client tries to reconnect but when reconnect fails, client stops
> trying.
> I'm trying to implement a feature which tries continuously to reconnect to
> server when the server is down. Connection state (open, disconnected or
> trying to connect) should also be indicated.
> If exception is passed to exception handler then it would be possible to
> register exception handler outside Camel. The purpose of this exception
> handler is to shut down Camel context and recreate it again in order to
> reconnect. With this kind of setup I can continuously try to reconnect and
> also figure out the current connection state.
>
> [https://github.com/apache/camel/blob/master/components/camel-ahc-ws/src/main/java/org/apache/camel/component/ahc/ws/WsEndpoint.java]
>
> {code:java}
> @Override
> public void onClose(WebSocket websocket, int code, String reason) {
>LOG.debug("websocket closed - reconnecting");
>try {
> reConnect();
>} catch (Exception e) {
> LOG.warn("Error re-connecting to websocket", e);
>}
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12951) Camel-AHC-WS: reconnect exception is not passed to exception handler
[
https://issues.apache.org/jira/browse/CAMEL-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-12951.
--
Resolution: Fixed
> Camel-AHC-WS: reconnect exception is not passed to exception handler
>
>
> Key: CAMEL-12951
> URL: https://issues.apache.org/jira/browse/CAMEL-12951
> Project: Camel
> Issue Type: Bug
> Components: camel-ahc-ws
>Affects Versions: 2.22.2
>Reporter: Jukka Aalto
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.24.0
>
>
> When WsEndPoint reconnect-method fails in line 172 to create connection it
> throws an exception which is logged but it should also be given to exception
> handler.
> This kind of situation happens when server is shut down while connection is
> open. First client tries to reconnect but when reconnect fails, client stops
> trying.
> I'm trying to implement a feature which tries continuously to reconnect to
> server when the server is down. Connection state (open, disconnected or
> trying to connect) should also be indicated.
> If exception is passed to exception handler then it would be possible to
> register exception handler outside Camel. The purpose of this exception
> handler is to shut down Camel context and recreate it again in order to
> reconnect. With this kind of setup I can continuously try to reconnect and
> also figure out the current connection state.
>
> [https://github.com/apache/camel/blob/master/components/camel-ahc-ws/src/main/java/org/apache/camel/component/ahc/ws/WsEndpoint.java]
>
> {code:java}
> @Override
> public void onClose(WebSocket websocket, int code, String reason) {
>LOG.debug("websocket closed - reconnecting");
>try {
> reConnect();
>} catch (Exception e) {
> LOG.warn("Error re-connecting to websocket", e);
>}
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12952) Camel-AHC-WS: does not send response to ping frame
[ https://issues.apache.org/jira/browse/CAMEL-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12952. -- Resolution: Fixed > Camel-AHC-WS: does not send response to ping frame > -- > > Key: CAMEL-12952 > URL: https://issues.apache.org/jira/browse/CAMEL-12952 > Project: Camel > Issue Type: Bug > Components: camel-ahc-ws >Reporter: Jukka Aalto >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 2.24.0 > > > Websocket client should send response to ping frame. See document > [https://tools.ietf.org/html/rfc6455#page-37] > Client should send pong response. > The fix should be trivial because WsListener has empty default onPing-method. > The implementation of this method should call webSocket sendPong. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (CAMEL-12951) Camel-AHC-WS: reconnect exception is not passed to exception handler
[
https://issues.apache.org/jira/browse/CAMEL-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-12951 started by Andrea Cosentino.
> Camel-AHC-WS: reconnect exception is not passed to exception handler
>
>
> Key: CAMEL-12951
> URL: https://issues.apache.org/jira/browse/CAMEL-12951
> Project: Camel
> Issue Type: Bug
> Components: camel-ahc-ws
>Affects Versions: 2.22.2
>Reporter: Jukka Aalto
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.24.0
>
>
> When WsEndPoint reconnect-method fails in line 172 to create connection it
> throws an exception which is logged but it should also be given to exception
> handler.
> This kind of situation happens when server is shut down while connection is
> open. First client tries to reconnect but when reconnect fails, client stops
> trying.
> I'm trying to implement a feature which tries continuously to reconnect to
> server when the server is down. Connection state (open, disconnected or
> trying to connect) should also be indicated.
> If exception is passed to exception handler then it would be possible to
> register exception handler outside Camel. The purpose of this exception
> handler is to shut down Camel context and recreate it again in order to
> reconnect. With this kind of setup I can continuously try to reconnect and
> also figure out the current connection state.
>
> [https://github.com/apache/camel/blob/master/components/camel-ahc-ws/src/main/java/org/apache/camel/component/ahc/ws/WsEndpoint.java]
>
> {code:java}
> @Override
> public void onClose(WebSocket websocket, int code, String reason) {
>LOG.debug("websocket closed - reconnecting");
>try {
> reConnect();
>} catch (Exception e) {
> LOG.warn("Error re-connecting to websocket", e);
>}
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12952) Camel-AHC-WS: does not send response to ping frame
[ https://issues.apache.org/jira/browse/CAMEL-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-12952: - Fix Version/s: 2.24.0 > Camel-AHC-WS: does not send response to ping frame > -- > > Key: CAMEL-12952 > URL: https://issues.apache.org/jira/browse/CAMEL-12952 > Project: Camel > Issue Type: Bug > Components: camel-ahc-ws >Reporter: Jukka Aalto >Priority: Minor > Fix For: 2.24.0 > > > Websocket client should send response to ping frame. See document > [https://tools.ietf.org/html/rfc6455#page-37] > Client should send pong response. > The fix should be trivial because WsListener has empty default onPing-method. > The implementation of this method should call webSocket sendPong. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12952) Camel-AHC-WS: does not send response to ping frame
[ https://issues.apache.org/jira/browse/CAMEL-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-12952: Assignee: Andrea Cosentino > Camel-AHC-WS: does not send response to ping frame > -- > > Key: CAMEL-12952 > URL: https://issues.apache.org/jira/browse/CAMEL-12952 > Project: Camel > Issue Type: Bug > Components: camel-ahc-ws >Reporter: Jukka Aalto >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 2.24.0 > > > Websocket client should send response to ping frame. See document > [https://tools.ietf.org/html/rfc6455#page-37] > Client should send pong response. > The fix should be trivial because WsListener has empty default onPing-method. > The implementation of this method should call webSocket sendPong. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
