[jira] [Commented] (CAMEL-11500) Create CI build for the website
[ https://issues.apache.org/jira/browse/CAMEL-11500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472735#comment-16472735 ] Simon IJskes commented on CAMEL-11500: -- maybe this can help: https://issues.apache.org/jira/browse/NETBEANS-522 > Create CI build for the website > --- > > Key: CAMEL-11500 > URL: https://issues.apache.org/jira/browse/CAMEL-11500 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > > Investigate git publishing with ASF, create CI build and perhaps a Docker > container for the build to run in. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12507) SqsProducer support for Number custom data types
[ https://issues.apache.org/jira/browse/CAMEL-12507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472678#comment-16472678 ] Craig commented on CAMEL-12507: --- https://github.com/apache/camel/pull/2337 > SqsProducer support for Number custom data types > > > Key: CAMEL-12507 > URL: https://issues.apache.org/jira/browse/CAMEL-12507 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Affects Versions: 2.20.3, 2.21.0 >Reporter: Craig >Priority: Major > > According to > [https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-message-attributes.html] > it is nice for SQS producers to use extended data types (ex "Number.int" > instead of just "Number"). > amazon-sqs-java-messaging-lib does this: > [https://github.com/awslabs/amazon-sqs-java-messaging-lib/blob/1.0.4/src/main/java/com/amazon/sqs/javamessaging/SQSMessagingClientConstants.java#L39] > Camel should as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12506) SqsProducer doesn't support Boolean attributes
[ https://issues.apache.org/jira/browse/CAMEL-12506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472674#comment-16472674 ] ASF GitHub Bot commented on CAMEL-12506: GitHub user candrews opened a pull request: https://github.com/apache/camel/pull/2337 CAMEL-12506 and CAMEL-12507: SQS support for boolean and custom number types https://issues.apache.org/jira/browse/CAMEL-12506 SqsProducer doesn't support Boolean attributes https://issues.apache.org/jira/browse/CAMEL-12507 SqsProducer support for Number custom data types You can merge this pull request into a Git repository by running: $ git pull https://github.com/candrews/camel patch-3 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2337.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2337 commit c13ea12e60c8a3b366a4a654a9371ad94ec3c1e6 Author: Craig Andrews Date: 2018-05-11T20:50:17Z CAMEL-12506: SQS Producer support for boolean attributes If a header of type `Boolean` is provided, map it to an SQS `MessageAttributeValue` of type "Number" with the`MessageAttributeValue`'s StringValue being "1" for true and "0" for false. This behavior matches that of amazon-sqs-java-messaging-lib: https://github.com/awslabs/amazon-sqs-java-messaging-lib/blob/1.0.4/src/main/java/com/amazon/sqs/javamessaging/message/SQSMessage.java#L1146 See https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-message-attributes.html commit 09ff0f0713f597c9b22714d843d2f5f5cf259340 Author: Craig Andrews Date: 2018-05-11T21:00:23Z CAMEL-12507: SQS Producer support for number custom types If a header of type `Number` is provided, set the dataType to "Number." + an appropriate identifier These dataType values match those used by amazon-sqs-java-messaging-lib: https://github.com/awslabs/amazon-sqs-java-messaging-lib/blob/1.0.4/src/main/java/com/amazon/sqs/javamessaging/SQSMessagingClientConstants.java#L39 See https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-message-attributes.html > SqsProducer doesn't support Boolean attributes > -- > > Key: CAMEL-12506 > URL: https://issues.apache.org/jira/browse/CAMEL-12506 > Project: Camel > Issue Type: Bug > Components: camel-aws >Affects Versions: 2.20.3, 2.21.0 >Reporter: Craig >Priority: Major > > SqsProducer doesn't support Boolean attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12506) SqsProducer doesn't support Boolean attributes
[ https://issues.apache.org/jira/browse/CAMEL-12506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472673#comment-16472673 ] ASF GitHub Bot commented on CAMEL-12506: candrews opened a new pull request #2337: CAMEL-12506 and CAMEL-12507: SQS support for boolean and custom number types URL: https://github.com/apache/camel/pull/2337 https://issues.apache.org/jira/browse/CAMEL-12506 SqsProducer doesn't support Boolean attributes https://issues.apache.org/jira/browse/CAMEL-12507 SqsProducer support for Number custom data types 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 > SqsProducer doesn't support Boolean attributes > -- > > Key: CAMEL-12506 > URL: https://issues.apache.org/jira/browse/CAMEL-12506 > Project: Camel > Issue Type: Bug > Components: camel-aws >Affects Versions: 2.20.3, 2.21.0 >Reporter: Craig >Priority: Major > > SqsProducer doesn't support Boolean attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12506) SqsProducer doesn't support Boolean attributes
[ https://issues.apache.org/jira/browse/CAMEL-12506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472677#comment-16472677 ] Craig commented on CAMEL-12506: --- https://github.com/apache/camel/pull/2337 > SqsProducer doesn't support Boolean attributes > -- > > Key: CAMEL-12506 > URL: https://issues.apache.org/jira/browse/CAMEL-12506 > Project: Camel > Issue Type: Bug > Components: camel-aws >Affects Versions: 2.20.3, 2.21.0 >Reporter: Craig >Priority: Major > > SqsProducer doesn't support Boolean attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12507) SqsProducer support for Number custom data types
Craig created CAMEL-12507: - Summary: SqsProducer support for Number custom data types Key: CAMEL-12507 URL: https://issues.apache.org/jira/browse/CAMEL-12507 Project: Camel Issue Type: Improvement Components: camel-aws Affects Versions: 2.21.0, 2.20.3 Reporter: Craig According to [https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-message-attributes.html] it is nice for SQS producers to use extended data types (ex "Number.int" instead of just "Number"). amazon-sqs-java-messaging-lib does this: [https://github.com/awslabs/amazon-sqs-java-messaging-lib/blob/1.0.4/src/main/java/com/amazon/sqs/javamessaging/SQSMessagingClientConstants.java#L39] Camel should as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12506) SqsProducer doesn't support Boolean attributes
Craig created CAMEL-12506: - Summary: SqsProducer doesn't support Boolean attributes Key: CAMEL-12506 URL: https://issues.apache.org/jira/browse/CAMEL-12506 Project: Camel Issue Type: Bug Components: camel-aws Affects Versions: 2.21.0, 2.20.3 Reporter: Craig SqsProducer doesn't support Boolean attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11257) Provide AS2 component to support Business Data Interchange Using HTTP
[ https://issues.apache.org/jira/browse/CAMEL-11257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472172#comment-16472172 ] ASF GitHub Bot commented on CAMEL-11257: GitHub user punkhorn opened a pull request: https://github.com/apache/camel/pull/2336 [CAMEL-11257] Fixed deserialization of transfer encoded MIME entities You can merge this pull request into a Git repository by running: $ git pull https://github.com/punkhorn/camel-upstream master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2336.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2336 commit 822ed63890fbca33bb4ab95217cc377c7dc90d18 Author: William Collins Date: 2018-05-11T16:00:49Z [CAMEL-11257] Fixed deserialization of transfer encoded MIME entities > Provide AS2 component to support Business Data Interchange Using HTTP > - > > Key: CAMEL-11257 > URL: https://issues.apache.org/jira/browse/CAMEL-11257 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.19.1 >Reporter: William Collins >Assignee: William Collins >Priority: Major > Fix For: 2.22.0 > > > AS2 Camel component should provide MIME-Based Secure Peer-to-Peer Business > Data Interchange Using HTTP as per RFC4120 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11257) Provide AS2 component to support Business Data Interchange Using HTTP
[ https://issues.apache.org/jira/browse/CAMEL-11257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472171#comment-16472171 ] ASF GitHub Bot commented on CAMEL-11257: punkhorn opened a new pull request #2336: [CAMEL-11257] Fixed deserialization of transfer encoded MIME entities URL: https://github.com/apache/camel/pull/2336 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 > Provide AS2 component to support Business Data Interchange Using HTTP > - > > Key: CAMEL-11257 > URL: https://issues.apache.org/jira/browse/CAMEL-11257 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.19.1 >Reporter: William Collins >Assignee: William Collins >Priority: Major > Fix For: 2.22.0 > > > AS2 Camel component should provide MIME-Based Secure Peer-to-Peer Business > Data Interchange Using HTTP as per RFC4120 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-10803) Base undertow component on http-common
[ https://issues.apache.org/jira/browse/CAMEL-10803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471736#comment-16471736 ] ASF GitHub Bot commented on CAMEL-10803: zregvart closed pull request #1450: CAMEL-10803 Base undertow component on http-common URL: https://github.com/apache/camel/pull/1450 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-undertow/src/main/docs/undertow-component.adoc b/components/camel-undertow/src/main/docs/undertow-component.adoc index 68fdea4fde9..5de51f9bdf5 100644 --- a/components/camel-undertow/src/main/docs/undertow-component.adoc +++ b/components/camel-undertow/src/main/docs/undertow-component.adoc @@ -38,7 +38,7 @@ You can append query options to the URI in the following format, // component options: START -The Undertow component supports 4 options which are listed below. +The Undertow component supports 8 options which are listed below. @@ -48,6 +48,10 @@ The Undertow component supports 4 options which are listed below. | **undertowHttpBinding** (advanced) | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | | UndertowHttpBinding | **sslContextParameters** (security) | To configure security using SSLContextParameters | | SSLContextParameters | **hostOptions** (advanced) | To configure common options such as thread pools | | UndertowHostOptions +| **httpBinding** (advanced) | To use a custom HttpBinding to control the mapping between Camel message and HttpClient. | | HttpBinding +| **httpConfiguration** (advanced) | To use the shared HttpConfiguration as base configuration. | | HttpConfiguration +| **allowJavaSerialized Object** (advanced) | Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk. | false | boolean +| **headerFilterStrategy** (filter) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy | **resolveProperty Placeholders** (advanced) | Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. | true | boolean |=== // component options: END @@ -70,30 +74,63 @@ with the following path and query parameters: [width="100%",cols="2,5,^1,2",options="header"] |=== | Name | Description | Default | Type -| **httpURI** | *Required* The url of the HTTP endpoint to use. | | URI +| **httpUri** | *Required* The url of the HTTP endpoint to call. | | URI |=== - Query Parameters (17 parameters): + Query Parameters (50 parameters): [width="100%",cols="2,5,^1,2",options="header"] |=== | Name | Description | Default | Type +| **chunked** (common) | If this option is false the Servlet will disable the HTTP streaming and set the content-length header on the response | true | boolean +| **disableStreamCache** (common) | Determines whether or not the raw input stream from Servlet is cached or not (Camel will read the stream into a in memory/overflow to file Stream caching) cache. By default Camel will cache the Servlet input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this option to true when you for example need to access the raw stream such as streaming it directly to a file or other persistent store. DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support reading the stream multiple times. If you use Servlet to bridge/proxy an endpoint then consider enabling this option to improve performance in case you do not need to read the message payload multiple times. The http/http4 producer will by default cache the response body stream. If setting this option to true then the producers will not cache the response body stream but use the response stream as-is as the message body. | false | boolean +| **headerFilterStrategy** (common) | To use a custom HeaderFilterStrategy to filter header to and from Camel message. | | HeaderFilterStrategy +| **transferException** (common) | If enabled and an Exchange failed
[jira] [Commented] (CAMEL-10803) Base undertow component on http-common
[ https://issues.apache.org/jira/browse/CAMEL-10803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471737#comment-16471737 ] ASF GitHub Bot commented on CAMEL-10803: Github user zregvart closed the pull request at: https://github.com/apache/camel/pull/1450 > Base undertow component on http-common > -- > > Key: CAMEL-10803 > URL: https://issues.apache.org/jira/browse/CAMEL-10803 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Affects Versions: 2.19.0 >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > > To facilitate reuse, the Undertow component should be based on http-common > component. > The `UndertowComponent` should extend `HttpCommonComponent` and > `UndertowEndpoint` should extend `HttpCommonEndpoint`. > Following that options defined in the http-common component should be also > supported in the Undertow component. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-11888) cluster service : add a cluster service based on JGroups Raft
[ https://issues.apache.org/jira/browse/CAMEL-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471622#comment-16471622 ] Andrea Tarocchi edited comment on CAMEL-11888 at 5/11/18 8:42 AM: -- Hi [~lb], an implementation based on JGroups views would suffer the same limitations as the one based on JGroups Locks (i.e. not enforcing only one master in case of split brain); an implementation based on jgroups-raft would be more interesting in that regards adding a new option for the users to cope with spilt-brains situations. I'd love to implement it fi you are looking for volunteers. was (Author: valdar): Hi [~lb], an implementation based on JGroups views would suffer the same limitations as the one based on JGroups Locks (i.e. not enforcing only one master in case of split brain); an implementation based on jgroups-raft would be more interesting in that regards adding an new option for the users to cope with spilt-brains situations. I'd love to implement it fi you are looking for volunteers. > cluster service : add a cluster service based on JGroups Raft > - > > Key: CAMEL-11888 > URL: https://issues.apache.org/jira/browse/CAMEL-11888 > Project: Camel > Issue Type: New Feature > Components: camel-jgroups >Reporter: Luca Burgazzoli >Assignee: Andrea Tarocchi >Priority: Minor > Labels: clustering > Fix For: 2.22.0 > > > See http://belaban.github.io/jgroups-raft/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-11888) cluster service : add a cluster service based on JGroups Raft
[ https://issues.apache.org/jira/browse/CAMEL-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned CAMEL-11888: --- Assignee: Andrea Tarocchi > cluster service : add a cluster service based on JGroups Raft > - > > Key: CAMEL-11888 > URL: https://issues.apache.org/jira/browse/CAMEL-11888 > Project: Camel > Issue Type: New Feature > Components: camel-jgroups >Reporter: Luca Burgazzoli >Assignee: Andrea Tarocchi >Priority: Minor > Labels: clustering > Fix For: 2.22.0 > > > See http://belaban.github.io/jgroups-raft/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12503) Kafka component should be able to propagate camel headers to kafka
[
https://issues.apache.org/jira/browse/CAMEL-12503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471658#comment-16471658
]
ASF GitHub Bot commented on CAMEL-12503:
tdanylchuk commented on a change in pull request #2333: CAMEL-12503: added
support for propagating camel headers to kafka and vice versa
URL: https://github.com/apache/camel/pull/2333#discussion_r187551979
##
File path:
components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaProducer.java
##
@@ -214,15 +222,39 @@ public void remove() {
ProducerRecord record;
if (hasPartitionKey && hasMessageKey) {
-record = new ProducerRecord(topic, partitionKey, key, value);
+record = new ProducerRecord(topic, partitionKey, null, key, value,
propagatedHeaders);
} else if (hasMessageKey) {
-record = new ProducerRecord(topic, key, value);
+record = new ProducerRecord(topic, null, null, key, value,
propagatedHeaders);
} else {
-record = new ProducerRecord(topic, value);
+record = new ProducerRecord(topic, null, null, null, value,
propagatedHeaders);
}
return Collections.singletonList(record).iterator();
}
+private List getPropagatedHeaders(Exchange exchange,
HeaderFilterStrategy headerFilterStrategy) {
+return exchange.getIn().getHeaders().entrySet().stream()
+.filter(entry ->
!headerFilterStrategy.applyFilterToExternalHeaders(entry.getKey(),
entry.getValue(), exchange))
+.map(entry -> new RecordHeader(entry.getKey(),
getHeaderValue(entry.getValue(
+.collect(Collectors.toList());
+}
+
+private byte[] getHeaderValue(Object value) {
Review comment:
agree
+ added `warn` message
+ added `Double` support
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
> Kafka component should be able to propagate camel headers to kafka
> --
>
> Key: CAMEL-12503
> URL: https://issues.apache.org/jira/browse/CAMEL-12503
> Project: Camel
> Issue Type: New Feature
>Reporter: Taras Danylchuk
>Priority: Major
>
> Since 0.11.0 Kafka support headers, and it would be awesome to have such
> feature available also in camel component.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12503) Kafka component should be able to propagate camel headers to kafka
[
https://issues.apache.org/jira/browse/CAMEL-12503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471657#comment-16471657
]
ASF GitHub Bot commented on CAMEL-12503:
tdanylchuk commented on a change in pull request #2333: CAMEL-12503: added
support for propagating camel headers to kafka and vice versa
URL: https://github.com/apache/camel/pull/2333#discussion_r187551979
##
File path:
components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaProducer.java
##
@@ -214,15 +222,39 @@ public void remove() {
ProducerRecord record;
if (hasPartitionKey && hasMessageKey) {
-record = new ProducerRecord(topic, partitionKey, key, value);
+record = new ProducerRecord(topic, partitionKey, null, key, value,
propagatedHeaders);
} else if (hasMessageKey) {
-record = new ProducerRecord(topic, key, value);
+record = new ProducerRecord(topic, null, null, key, value,
propagatedHeaders);
} else {
-record = new ProducerRecord(topic, value);
+record = new ProducerRecord(topic, null, null, null, value,
propagatedHeaders);
}
return Collections.singletonList(record).iterator();
}
+private List getPropagatedHeaders(Exchange exchange,
HeaderFilterStrategy headerFilterStrategy) {
+return exchange.getIn().getHeaders().entrySet().stream()
+.filter(entry ->
!headerFilterStrategy.applyFilterToExternalHeaders(entry.getKey(),
entry.getValue(), exchange))
+.map(entry -> new RecordHeader(entry.getKey(),
getHeaderValue(entry.getValue(
+.collect(Collectors.toList());
+}
+
+private byte[] getHeaderValue(Object value) {
Review comment:
agree, added `warn` message
+ added `Double` support
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
> Kafka component should be able to propagate camel headers to kafka
> --
>
> Key: CAMEL-12503
> URL: https://issues.apache.org/jira/browse/CAMEL-12503
> Project: Camel
> Issue Type: New Feature
>Reporter: Taras Danylchuk
>Priority: Major
>
> Since 0.11.0 Kafka support headers, and it would be awesome to have such
> feature available also in camel component.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-10793) camel cloud: expose routes as a service
[
https://issues.apache.org/jira/browse/CAMEL-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli updated CAMEL-10793:
Priority: Minor (was: Major)
> camel cloud: expose routes as a service
> ---
>
> Key: CAMEL-10793
> URL: https://issues.apache.org/jira/browse/CAMEL-10793
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Labels: cloud
> Fix For: 2.22.0
>
>
> As today we have a ServiceCall EIP that makes it easy to call external
> services in a cloud environment leveraging external service registry such as
> kubernetes, consul, etcd, spring-cloud & co so It could make sense to add a
> way for a route to register itself in such registries and be available as a
> service for other to consume.
> Something like:
> {code:java}
> // programmatic config
> from("jetty:http://0.0.0.0:8001/service1";)
> .serviceRegistry()
> .name("service-1")
> .host("")
> .port(8001)
> .meta("camel.protocol", "http")
> .meta("camel.component", "jetty")
> .meta("camel.context.path", "/service1")
> .end()
> .to("direct:service-1")
> // Inherit from a global config and eventually override it
> from("jetty:http://0.0.0.0:8002/service2";)
> .serviceRegistry("service-2")
> .configRef("service-registry-conf")
> .port(8002)
> .to("direct:service-2")
> // Smart auto configuration
> // i.e. if the endpoint implements DiscoverableService
> from("jetty:http://0.0.0.0:8003/service3";)
> .serviceRegistry("service-3")
> .to("direct:service-3")
> {code}
> Beside making camel play better in cloud environment, you can use the
> service call to connect camel based micro services with minimal configuration
> as the registration may provide some additional meta data that the service
> call can use for auto-configuration (of course not all the registries can do
> it).
> The future Health API/Service may then also be configured to remove or
> invalidate the service if the route is reported as not healthy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12485) camel cloud : create camel-service component
[
https://issues.apache.org/jira/browse/CAMEL-12485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli updated CAMEL-12485:
Priority: Minor (was: Major)
> camel cloud : create camel-service component
>
>
> Key: CAMEL-12485
> URL: https://issues.apache.org/jira/browse/CAMEL-12485
> Project: Camel
> Issue Type: Sub-task
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Labels: cloud
> Fix For: 2.22.0
>
>
> We should create a camel-service component that like the camel-master
> component leverage a service to expose routes for discovery on consumer side
> and leverage Service Call EIP on producer side to invoke a service.
> Some thing like:
> {code:java}
>
> from("service:jetty:0.0.0.0:8081/exposedService?serviceRegistry=#myRegistry")
> .to("service:targetService?serviceDiscovery=#mydiscovery");
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work started] (CAMEL-12505) service-call : include ServiceDefinition metatdata when computing the final URI
[ https://issues.apache.org/jira/browse/CAMEL-12505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-12505 started by Luca Burgazzoli. --- > service-call : include ServiceDefinition metatdata when computing the final > URI > --- > > Key: CAMEL-12505 > URL: https://issues.apache.org/jira/browse/CAMEL-12505 > Project: Camel > Issue Type: Test > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Labels: cloud, service-call > Fix For: 2.22.0 > > > A ServiceDefinition may include info such as the context path of an http > request so we need to take ServiceDefinition meta data into account when > computing the final URI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12505) service-call : include ServiceDefinition metatdata when computing the final URI
Luca Burgazzoli created CAMEL-12505: --- Summary: service-call : include ServiceDefinition metatdata when computing the final URI Key: CAMEL-12505 URL: https://issues.apache.org/jira/browse/CAMEL-12505 Project: Camel Issue Type: Test Components: camel-core Reporter: Luca Burgazzoli Assignee: Luca Burgazzoli Fix For: 2.22.0 A ServiceDefinition may include info such as the context path of an http request so we need to take ServiceDefinition meta data into account when computing the final URI -- 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&focusedCommentId=16471629#comment-16471629 ] Ramu kakarla commented on CAMEL-12494: --- working on this > 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] [Assigned] (CAMEL-11888) cluster service : add a cluster service based on JGroups Raft
[ https://issues.apache.org/jira/browse/CAMEL-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned CAMEL-11888: --- Assignee: (was: Luca Burgazzoli) > cluster service : add a cluster service based on JGroups Raft > - > > Key: CAMEL-11888 > URL: https://issues.apache.org/jira/browse/CAMEL-11888 > Project: Camel > Issue Type: New Feature > Components: camel-jgroups >Reporter: Luca Burgazzoli >Priority: Minor > Labels: clustering > Fix For: 2.22.0 > > > See http://belaban.github.io/jgroups-raft/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-11888) cluster service : add a cluster service based on JGroups Raft
[ https://issues.apache.org/jira/browse/CAMEL-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned CAMEL-11888: --- Assignee: Luca Burgazzoli > cluster service : add a cluster service based on JGroups Raft > - > > Key: CAMEL-11888 > URL: https://issues.apache.org/jira/browse/CAMEL-11888 > Project: Camel > Issue Type: New Feature > Components: camel-jgroups >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Labels: clustering > Fix For: 2.22.0 > > > See http://belaban.github.io/jgroups-raft/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11888) cluster service : add a cluster service based on JGroups Raft
[ https://issues.apache.org/jira/browse/CAMEL-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated CAMEL-11888: Description: See http://belaban.github.io/jgroups-raft/ (was: See http://www.jgroups.org/javadoc/org/jgroups/View.html) > cluster service : add a cluster service based on JGroups Raft > - > > Key: CAMEL-11888 > URL: https://issues.apache.org/jira/browse/CAMEL-11888 > Project: Camel > Issue Type: New Feature > Components: camel-jgroups >Reporter: Luca Burgazzoli >Priority: Minor > Labels: clustering > Fix For: 2.22.0 > > > See http://belaban.github.io/jgroups-raft/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11888) cluster service : add a cluster service based on JGroups Raft
[ https://issues.apache.org/jira/browse/CAMEL-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471627#comment-16471627 ] Luca Burgazzoli commented on CAMEL-11888: - [~valdar] title updated, please go ahead :) > cluster service : add a cluster service based on JGroups Raft > - > > Key: CAMEL-11888 > URL: https://issues.apache.org/jira/browse/CAMEL-11888 > Project: Camel > Issue Type: New Feature > Components: camel-jgroups >Reporter: Luca Burgazzoli >Priority: Minor > Labels: clustering > Fix For: 2.22.0 > > > See http://belaban.github.io/jgroups-raft/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11888) cluster service : add a cluster service based on JGroups Raft
[ https://issues.apache.org/jira/browse/CAMEL-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated CAMEL-11888: Summary: cluster service : add a cluster service based on JGroups Raft (was: cluster service : add a cluster service based on JGroups View) > cluster service : add a cluster service based on JGroups Raft > - > > Key: CAMEL-11888 > URL: https://issues.apache.org/jira/browse/CAMEL-11888 > Project: Camel > Issue Type: New Feature > Components: camel-jgroups >Reporter: Luca Burgazzoli >Priority: Minor > Labels: clustering > Fix For: 2.22.0 > > > See http://www.jgroups.org/javadoc/org/jgroups/View.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11658) URISyntaxException in RestletProducer
[
https://issues.apache.org/jira/browse/CAMEL-11658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471623#comment-16471623
]
ASF GitHub Bot commented on CAMEL-11658:
zregvart commented on issue #1938: CAMEL-11658: test for RestletProducer
handling unencoded headers
URL: https://github.com/apache/camel/pull/1938#issuecomment-388291007
Sorry, got lost in my GitHub notifications. Seems to me that can either:
- encode the URL placeholder parameters and by that loose the ability to
specify query parameters in the placeholders. So you can't use something like
`http://example.com/{query}` and have `query` equal `?q=something`, and make
the users use `RAW(?q=something)`
- introduce a helper syntax similar to `RAW` but for encoding URL
parameters, something like `http://example.com/ENC({query})`
- leave as is and make the user URL encode the parameter as needed
Either way there are some cons and pros, we should think about not breaking
backward compatibility I think, so if we URL encoded before we can do that now.
2c
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-11888) cluster service : add a cluster service based on JGroups View
[ https://issues.apache.org/jira/browse/CAMEL-11888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471622#comment-16471622 ] Andrea Tarocchi commented on CAMEL-11888: - Hi [~lb], an implementation based on JGroups views would suffer the same limitations as the one based on JGroups Locks (i.e. not enforcing only one master in case of split brain); an implementation based on jgroups-raft would be more interesting in that regards adding an new option for the users to cope with spilt-brains situations. I'd love to implement it fi you are looking for volunteers. > cluster service : add a cluster service based on JGroups View > - > > Key: CAMEL-11888 > URL: https://issues.apache.org/jira/browse/CAMEL-11888 > Project: Camel > Issue Type: New Feature > Components: camel-jgroups >Reporter: Luca Burgazzoli >Priority: Minor > Labels: clustering > Fix For: 2.22.0 > > > See http://www.jgroups.org/javadoc/org/jgroups/View.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
