[jira] [Created] (CAMEL-13525) camel - Only allow setting routeId once per route in Java DSL
Claus Ibsen created CAMEL-13525: --- Summary: camel - Only allow setting routeId once per route in Java DSL Key: CAMEL-13525 URL: https://issues.apache.org/jira/browse/CAMEL-13525 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 3.0.0 1 route = 1 route id, what you did in that unit test / JIRA ticket was wrong and not intended to be supported, eg .routeId will override each other, a route has 1 route id. So do only set .routeId once per route! >From gitter chat -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13524) RuntimeCamelCatalog#asEndpointUri strips dash from url with toD and netty4-http
[
https://issues.apache.org/jira/browse/CAMEL-13524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Bednar updated CAMEL-13524:
---
Description:
[https://stackoverflow.com/questions/56136857/how-to-use-camel-tod-and-netty4-http-component-problem-with-optimization-of-din]
This is very similar to CAMEL-12705, but in this case it affects url with
dashes. Tested with current master.
*{{url}}*
{code:java}
netty4-http:http://a-b-c.hostname.tld:8080/anything{code}
*results in*
{code:java}
netty4-http:http:a-b:8080/path{code}
Unit test in attachment.
-Maybe-
-_AbstractCamelCatalog#SYNTAX_PATTERN_ should be changed to-
{code:java}
([\w.-]+)
{code}
-Or is there reason, why is dash excluded from regexp?-
I have tried to edit regexp and it broke test too, it results in resolved =
"netty4-http:http:a-b-c.hostname.tld-8080"
was:
[https://stackoverflow.com/questions/56136857/how-to-use-camel-tod-and-netty4-http-component-problem-with-optimization-of-din]
This is very similar to CAMEL-12705, but in this case it affects url with
dashes. Tested with current master.
*{{url}}*
{code:java}
netty4-http:http://a-b-c.hostname.tld:8080/anything{code}
*results in*
{code:java}
netty4-http:http:a-b:8080/path{code}
Unit test in attachment.
Maybe
_AbstractCamelCatalog#SYNTAX_PATTERN_ should be changed to
{code:java}
([\w.-]+)
{code}
Or is there reason, why is dash excluded from regexp?
> RuntimeCamelCatalog#asEndpointUri strips dash from url with toD and
> netty4-http
> ---
>
> Key: CAMEL-13524
> URL: https://issues.apache.org/jira/browse/CAMEL-13524
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.23.0, 3.0.0-M2
>Reporter: Jan Bednar
>Priority: Major
> Attachments:
> RuntimeCamelCatalog#asEndpointUri_strips_dash_from_url_with_netty4-http.patch
>
>
> [https://stackoverflow.com/questions/56136857/how-to-use-camel-tod-and-netty4-http-component-problem-with-optimization-of-din]
> This is very similar to CAMEL-12705, but in this case it affects url with
> dashes. Tested with current master.
> *{{url}}*
> {code:java}
> netty4-http:http://a-b-c.hostname.tld:8080/anything{code}
> *results in*
> {code:java}
> netty4-http:http:a-b:8080/path{code}
> Unit test in attachment.
>
> -Maybe-
> -_AbstractCamelCatalog#SYNTAX_PATTERN_ should be changed to-
> {code:java}
> ([\w.-]+)
> {code}
> -Or is there reason, why is dash excluded from regexp?-
> I have tried to edit regexp and it broke test too, it results in resolved =
> "netty4-http:http:a-b-c.hostname.tld-8080"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13524) RuntimeCamelCatalog#asEndpointUri strips dash from url with toD and netty4-http
Jan Bednar created CAMEL-13524:
--
Summary: RuntimeCamelCatalog#asEndpointUri strips dash from url
with toD and netty4-http
Key: CAMEL-13524
URL: https://issues.apache.org/jira/browse/CAMEL-13524
Project: Camel
Issue Type: Bug
Components: came-core
Affects Versions: 3.0.0-M2, 2.23.0
Reporter: Jan Bednar
Attachments:
RuntimeCamelCatalog#asEndpointUri_strips_dash_from_url_with_netty4-http.patch
[https://stackoverflow.com/questions/56136857/how-to-use-camel-tod-and-netty4-http-component-problem-with-optimization-of-din]
This is very similar to CAMEL-12705, but in this case it affects url with
dashes. Tested with current master.
*{{url}}*
{code:java}
netty4-http:http://a-b-c.hostname.tld:8080/anything{code}
*results in*
{code:java}
netty4-http:http:a-b:8080/path{code}
Unit test in attachment.
Maybe
_AbstractCamelCatalog#SYNTAX_PATTERN_ should be changed to
{code:java}
([\w.-]+)
{code}
Or is there reason, why is dash excluded from regexp?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13390) Develop new jira component based on rest api
[ https://issues.apache.org/jira/browse/CAMEL-13390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839745#comment-16839745 ] Claudio Miranda commented on CAMEL-13390: - PR for master branch: https://github.com/apache/camel/pull/2915 > Develop new jira component based on rest api > > > Key: CAMEL-13390 > URL: https://issues.apache.org/jira/browse/CAMEL-13390 > Project: Camel > Issue Type: New Feature >Reporter: Claudio Miranda >Priority: Major > > For next syndesis version, we need a Jira component. This component should be > based on [Jira rest > api|https://developer.atlassian.com/server/jira/platform/rest-apis/] > The initial feature set is as follow: > create Jira issues including filed data such as > * type > * component > * assignee > * watchers > * issue type > * priority > * attachment > * labels > read Jira issues. > update Jira issues including filed data such as > * component > * status > * resolution > * type > * assignee > * watchers > * issue type > * labels > * priority > * attachment > delete Jira issues. > comment on an issue. > Search issues with a custom Jira query. > Documentation and unit tests are also included. > I want to prototype a first version and submit for review asap. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13234) Can we get rid of weld2
[ https://issues.apache.org/jira/browse/CAMEL-13234?focusedWorklogId=241984=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-241984 ] ASF GitHub Bot logged work on CAMEL-13234: -- Author: ASF GitHub Bot Created on: 14/May/19 19:36 Start Date: 14/May/19 19:36 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #2914: CAMEL-13234: Use weld3 instead of weld2 at CDI example projects URL: https://github.com/apache/camel/pull/2914 This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 Issue Time Tracking --- Worklog Id: (was: 241984) Time Spent: 20m (was: 10m) > Can we get rid of weld2 > --- > > Key: CAMEL-13234 > URL: https://issues.apache.org/jira/browse/CAMEL-13234 > Project: Camel > Issue Type: Task > Components: camel-cdi >Reporter: Claus Ibsen >Assignee: Denis Istomin >Priority: Major > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > camel-cdi is using weld3. And we may have some examples and other bits that > uses weld2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13234) Can we get rid of weld2
[ https://issues.apache.org/jira/browse/CAMEL-13234?focusedWorklogId=241953=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-241953 ] ASF GitHub Bot logged work on CAMEL-13234: -- Author: ASF GitHub Bot Created on: 14/May/19 18:49 Start Date: 14/May/19 18:49 Worklog Time Spent: 10m Work Description: DenisIstomin commented on pull request #2914: CAMEL-13234: Use weld3 instead of weld2 at CDI example projects URL: https://github.com/apache/camel/pull/2914 1. Double checked all modified examples to work with weld3. 1. There are more things that use weld2: camel-archetype-cdi, etc. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 Issue Time Tracking --- Worklog Id: (was: 241953) Time Spent: 10m Remaining Estimate: 0h > Can we get rid of weld2 > --- > > Key: CAMEL-13234 > URL: https://issues.apache.org/jira/browse/CAMEL-13234 > Project: Camel > Issue Type: Task > Components: camel-cdi >Reporter: Claus Ibsen >Assignee: Denis Istomin >Priority: Major > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > camel-cdi is using weld3. And we may have some examples and other bits that > uses weld2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13521) Add reverse proxy option in camel-netty4-http
[
https://issues.apache.org/jira/browse/CAMEL-13521?focusedWorklogId=241857=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-241857
]
ASF GitHub Bot logged work on CAMEL-13521:
--
Author: ASF GitHub Bot
Created on: 14/May/19 16:47
Start Date: 14/May/19 16:47
Worklog Time Spent: 10m
Work Description: zregvart commented on pull request #2911: CAMEL-13521:
Add reverse proxy option in camel-netty4-http
URL: https://github.com/apache/camel/pull/2911
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
Issue Time Tracking
---
Worklog Id: (was: 241857)
Time Spent: 20m (was: 10m)
> Add reverse proxy option in camel-netty4-http
> -
>
> Key: CAMEL-13521
> URL: https://issues.apache.org/jira/browse/CAMEL-13521
> Project: Camel
> Issue Type: New Feature
> Components: camel-netty4-http
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I think it would make sense to add support for reverse proxy operation in
> camel-netty4-http.
> With it one can have Camel act as a HTTP proxy perform some
> transformation/mediation/routing and make it easy to include in the
> architecture without much changing the client or the service.
> Perhaps adding a new protocol scheme {{proxy}} would be a good start, so the
> endpoint URI would look something like {{netty-http:proxy://0.0.0.0}}.
> I can work on a pull request to showcase this feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13520) camel-salesforce: setup-salesforce-instance issues error messages
[
https://issues.apache.org/jira/browse/CAMEL-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Dettinger resolved CAMEL-13520.
Resolution: Fixed
> camel-salesforce: setup-salesforce-instance issues error messages
> -
>
> Key: CAMEL-13520
> URL: https://issues.apache.org/jira/browse/CAMEL-13520
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.0.0-M2
>Reporter: Alex Dettinger
>Assignee: Alex Dettinger
>Priority: Minor
> Fix For: 3.0.0-M3
>
>
> {{Running *mvn -Pintegration antrun:run@setup-salesforce-instance* to first
> setup the connected app needed for integration tests reports issues:}}
> * {{The ModifyMetadata permission is needed}}
> * {{Some Apex classes contains invalid % characters}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13523) Support Java 12
John Poth created CAMEL-13523: - Summary: Support Java 12 Key: CAMEL-13523 URL: https://issues.apache.org/jira/browse/CAMEL-13523 Project: Camel Issue Type: Improvement Reporter: John Poth Fix For: 3.0.0 Builds fine but needs [https://github.com/mvel/mvel/issues/185/] to be merged and released. Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13513) CXFRS header "CamelDestinationOverrideUrl" ignored after changing it twice
[ https://issues.apache.org/jira/browse/CAMEL-13513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839524#comment-16839524 ] Antonio Gagliardi commented on CAMEL-13513: --- Hi Andrea, yes the issue exists also on master. I've made a PR on master with an integration test (disabled on master but works on 2.x) and the fix similar to the one made for CXFRS Spring Endpoint. [https://github.com/apache/camel/pull/2913] > CXFRS header "CamelDestinationOverrideUrl" ignored after changing it twice > -- > > Key: CAMEL-13513 > URL: https://issues.apache.org/jira/browse/CAMEL-13513 > Project: Camel > Issue Type: Bug > Components: camel-cxfrs >Affects Versions: 2.17.0 >Reporter: Antonio Gagliardi >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In a route that changes the destination of rsClient in CXFRS dynamically, > using the Header "CamelDestinationOverrideUrl", it stops working when set for > second time. > This issue has been partially fixed in the CAMEL-12541 but only for Spring > based endpoint, the issue still exists for the Blueprint based endpoint. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13513) CXFRS header "CamelDestinationOverrideUrl" ignored after changing it twice
[ https://issues.apache.org/jira/browse/CAMEL-13513?focusedWorklogId=241764=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-241764 ] ASF GitHub Bot logged work on CAMEL-13513: -- Author: ASF GitHub Bot Created on: 14/May/19 14:49 Start Date: 14/May/19 14:49 Worklog Time Spent: 10m Work Description: agagliardi commented on pull request #2913: CAMEL-13513 CXFRS header "CamelDestinationOverrideUrl" ignored after changing it twice URL: https://github.com/apache/camel/pull/2913 This issue has been fixed for the CXFRS Spring Endpoint with the CAMEL-12541 but not for the CXFRS Blueprint endpoint. Integration tests has been disabled on master but the test works on 2.x branches. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 Issue Time Tracking --- Worklog Id: (was: 241764) Time Spent: 10m Remaining Estimate: 0h > CXFRS header "CamelDestinationOverrideUrl" ignored after changing it twice > -- > > Key: CAMEL-13513 > URL: https://issues.apache.org/jira/browse/CAMEL-13513 > Project: Camel > Issue Type: Bug > Components: camel-cxfrs >Affects Versions: 2.17.0 >Reporter: Antonio Gagliardi >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In a route that changes the destination of rsClient in CXFRS dynamically, > using the Header "CamelDestinationOverrideUrl", it stops working when set for > second time. > This issue has been partially fixed in the CAMEL-12541 but only for Spring > based endpoint, the issue still exists for the Blueprint based endpoint. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13520) camel-salesforce: setup-salesforce-instance issues error messages
[
https://issues.apache.org/jira/browse/CAMEL-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Dettinger updated CAMEL-13520:
---
Description:
{{Running *mvn -Pintegration antrun:run@setup-salesforce-instance* to first
setup the connected app needed for integration tests reports issues:}}
* {{The ModifyMetadata permission is needed}}
* {{Some Apex classes contains invalid % characters}}
was:
{{Running *mvn -Pintegration antrun:run@setup-salesforce-instance* to first
setup the connected app needed for integration tests reports issues:}}
* {{The ModifyMetadata permission is needed}}
* {{Some Apex classes contains invalid % characters}}{{}}{{}}
> camel-salesforce: setup-salesforce-instance issues error messages
> -
>
> Key: CAMEL-13520
> URL: https://issues.apache.org/jira/browse/CAMEL-13520
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.0.0-M2
>Reporter: Alex Dettinger
>Assignee: Alex Dettinger
>Priority: Minor
> Fix For: 3.0.0-M3
>
>
> {{Running *mvn -Pintegration antrun:run@setup-salesforce-instance* to first
> setup the connected app needed for integration tests reports issues:}}
> * {{The ModifyMetadata permission is needed}}
> * {{Some Apex classes contains invalid % characters}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13521) Add reverse proxy option in camel-netty4-http
[
https://issues.apache.org/jira/browse/CAMEL-13521?focusedWorklogId=241698=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-241698
]
ASF GitHub Bot logged work on CAMEL-13521:
--
Author: ASF GitHub Bot
Created on: 14/May/19 13:04
Start Date: 14/May/19 13:04
Worklog Time Spent: 10m
Work Description: zregvart commented on pull request #2911: CAMEL-13521:
Add reverse proxy option in camel-netty4-http
URL: https://github.com/apache/camel/pull/2911
This adds support for reverse proxy functionality in `camel-netty4-http`
component.
While testing this I can see that the latency on the 99 percentile is
~50msec on my machine, would love to know if that can be optimized even
further. Transfer rate is definitely something that could be looked at.
In my tests I used a route like:
```java
from("netty-http:proxy://0.0.0.0:8080")
.toD("netty-http:"
+ "${headers." + Exchange.HTTP_SCHEME + "}://"
+ "${headers." + Exchange.HTTP_HOST + "}:"
+ "${headers." + Exchange.HTTP_PORT + "}")
```
I did notice some string/lambda allocations in the Pipeline that we might
want to take a look at also.
After some warmup here's a test I run with 1000 requests with concurrency of
100:
```shell
$ ab -c 100 -n 1000 -k -X localhost:8080 http://localhost:8000/hello
This is ApacheBench, Version 2.3 <$Revision: 1843412 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking localhost [through localhost:8080] (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Completed 600 requests
Completed 700 requests
Completed 800 requests
Completed 900 requests
Completed 1000 requests
Finished 1000 requests
Server Software:nginx/1.15.12
Server Hostname:localhost
Server Port:8000
Document Path: /hello
Document Length:13 bytes
Concurrency Level: 100
Time taken for tests: 0.534 seconds
Complete requests: 1000
Failed requests:0
Keep-Alive requests:995
Total transferred: 263975 bytes
HTML transferred: 13000 bytes
Requests per second:1872.85 [#/sec] (mean)
Time per request: 53.395 [ms] (mean)
Time per request: 0.534 [ms] (mean, across all concurrent requests)
Transfer rate: 482.80 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect:01 3.1 0 15
Processing: 1 50 26.0 46 145
Waiting:1 50 26.1 45 145
Total: 1 51 26.2 47 149
Percentage of the requests served within a certain time (ms)
50% 47
66% 59
75% 66
80% 71
90% 86
95%100
98%114
99%123
100%149 (longest request)
```
Versus going directly to the origin:
```shell
$ ab -c 100 -n 1000 -k http://localhost:8000/hello
This is ApacheBench, Version 2.3 <$Revision: 1843412 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking localhost (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Completed 600 requests
Completed 700 requests
Completed 800 requests
Completed 900 requests
Completed 1000 requests
Finished 1000 requests
Server Software:nginx/1.15.12
Server Hostname:localhost
Server Port:8000
Document Path: /hello
Document Length:13 bytes
Concurrency Level: 100
Time taken for tests: 0.082 seconds
Complete requests: 1000
Failed requests:0
Keep-Alive requests:1000
Total transferred: 264000 bytes
HTML transferred: 13000 bytes
Requests per second:12125.62 [#/sec] (mean)
Time per request: 8.247 [ms] (mean)
Time per request: 0.082 [ms] (mean, across all concurrent requests)
Transfer rate: 3126.14 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect:01 2.5 0 12
Processing: 16 14.3 2 67
Waiting:16 14.2 2 67
Total: 17 16.0 2 76
Percentage of the requests served within a certain time (ms)
50% 2
66% 2
75% 3
80% 3
90% 13
95% 64
98% 70
99% 71
100% 76
[jira] [Work logged] (CAMEL-13136) File consumer with charset doesn't parse XML
[ https://issues.apache.org/jira/browse/CAMEL-13136?focusedWorklogId=241682=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-241682 ] ASF GitHub Bot logged work on CAMEL-13136: -- Author: ASF GitHub Bot Created on: 14/May/19 11:46 Start Date: 14/May/19 11:46 Worklog Time Spent: 10m Work Description: tadayosi commented on pull request #2910: CAMEL-13136: File consumer with charset doesn't parse XML URL: https://github.com/apache/camel/pull/2910 https://issues.apache.org/jira/browse/CAMEL-13136 This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 Issue Time Tracking --- Worklog Id: (was: 241682) Time Spent: 10m Remaining Estimate: 0h > File consumer with charset doesn't parse XML > > > Key: CAMEL-13136 > URL: https://issues.apache.org/jira/browse/CAMEL-13136 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.0.0-M1 >Reporter: Thomas Diesler >Assignee: Tadayoshi Sato >Priority: Major > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > This now shows on camel-3.0 > https://issues.jboss.org/browse/ENTESB-10033 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13514) camel3 - Service start/stop should use unchecked exceptions
[ https://issues.apache.org/jira/browse/CAMEL-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839331#comment-16839331 ] Claus Ibsen commented on CAMEL-13514: - Also the start/stop of these services and camel context itself should avoid too many wrappings due checked vs unchecked exceptions are in play > camel3 - Service start/stop should use unchecked exceptions > --- > > Key: CAMEL-13514 > URL: https://issues.apache.org/jira/browse/CAMEL-13514 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > > The API for org.apache.camel.Service has throws Exception for its start/stop > methods. It would be great to remove those, as they throw runtime exceptions > when failing, and this makes using these APIs easier for end users, so they > dont have the burden of checked exceptions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13522) camel3 - The various Camel exceptions should favour extending runtime exception
Claus Ibsen created CAMEL-13522: --- Summary: camel3 - The various Camel exceptions should favour extending runtime exception Key: CAMEL-13522 URL: https://issues.apache.org/jira/browse/CAMEL-13522 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.0.0, 3.0.0-M3 This makes using the APIs in Camel easier, and most of them are runtime based anyway. So lets align to be more non checked exceptions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13521) Add reverse proxy option in camel-netty4-http
Zoran Regvart created CAMEL-13521:
-
Summary: Add reverse proxy option in camel-netty4-http
Key: CAMEL-13521
URL: https://issues.apache.org/jira/browse/CAMEL-13521
Project: Camel
Issue Type: New Feature
Components: camel-netty4-http
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Fix For: 3.0.0-M3
I think it would make sense to add support for reverse proxy operation in
camel-netty4-http.
With it one can have Camel act as a HTTP proxy perform some
transformation/mediation/routing and make it easy to include in the
architecture without much changing the client or the service.
Perhaps adding a new protocol scheme {{proxy}} would be a good start, so the
endpoint URI would look something like {{netty-http:proxy://0.0.0.0}}.
I can work on a pull request to showcase this feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Deleted] (CAMEL-13518) Camel-AWS SNS: Support filter policies during subscription
[ https://issues.apache.org/jira/browse/CAMEL-13518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino deleted CAMEL-13518: - > Camel-AWS SNS: Support filter policies during subscription > -- > > Key: CAMEL-13518 > URL: https://issues.apache.org/jira/browse/CAMEL-13518 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12966) camel-netty-http: use relative path by default
[
https://issues.apache.org/jira/browse/CAMEL-12966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-12966.
---
Resolution: Fixed
The default {{useRelativePath}} is now set to {{true}}. This makes it a good
default for the most common use case of issuing requests against a HTTP server
as opposed to against a proxy server.
See https://tools.ietf.org/html/rfc7230#section-5.3
> camel-netty-http: use relative path by default
> --
>
> Key: CAMEL-12966
> URL: https://issues.apache.org/jira/browse/CAMEL-12966
> Project: Camel
> Issue Type: Improvement
> Components: camel-netty4-http
>Reporter: Nicola Ferraro
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Netty-http 4 has a non-standard way of dealing with path, using the full url
> on the first line of the HTTP request. E.g.
>
> GET [http://thehost/thepath]
> instead of:
> GET /thepath
>
> This is controlled by the useRelativePath, that should be defaulted to "true"
> to be compatible with other components.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-13520) camel-salesforce: setup-salesforce-instance issues error messages
[
https://issues.apache.org/jira/browse/CAMEL-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Dettinger reassigned CAMEL-13520:
--
Assignee: Alex Dettinger
> camel-salesforce: setup-salesforce-instance issues error messages
> -
>
> Key: CAMEL-13520
> URL: https://issues.apache.org/jira/browse/CAMEL-13520
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.0.0-M2
>Reporter: Alex Dettinger
>Assignee: Alex Dettinger
>Priority: Minor
>
> {{Running *mvn -Pintegration antrun:run@setup-salesforce-instance* to first
> setup the connected app needed for integration tests reports issues:}}
> * {{The ModifyMetadata permission is needed}}
> * {{Some Apex classes contains invalid % characters}}{{}}{{}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13520) camel-salesforce: setup-salesforce-instance issues error messages
Alex Dettinger created CAMEL-13520:
--
Summary: camel-salesforce: setup-salesforce-instance issues error
messages
Key: CAMEL-13520
URL: https://issues.apache.org/jira/browse/CAMEL-13520
Project: Camel
Issue Type: Bug
Components: camel-salesforce
Affects Versions: 3.0.0-M2
Reporter: Alex Dettinger
{{Running *mvn -Pintegration antrun:run@setup-salesforce-instance* to first
setup the connected app needed for integration tests reports issues:}}
* {{The ModifyMetadata permission is needed}}
* {{Some Apex classes contains invalid % characters}}{{}}{{}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13520) camel-salesforce: setup-salesforce-instance issues error messages
[
https://issues.apache.org/jira/browse/CAMEL-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Dettinger updated CAMEL-13520:
---
Fix Version/s: 3.0.0-M3
> camel-salesforce: setup-salesforce-instance issues error messages
> -
>
> Key: CAMEL-13520
> URL: https://issues.apache.org/jira/browse/CAMEL-13520
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.0.0-M2
>Reporter: Alex Dettinger
>Assignee: Alex Dettinger
>Priority: Minor
> Fix For: 3.0.0-M3
>
>
> {{Running *mvn -Pintegration antrun:run@setup-salesforce-instance* to first
> setup the connected app needed for integration tests reports issues:}}
> * {{The ModifyMetadata permission is needed}}
> * {{Some Apex classes contains invalid % characters}}{{}}{{}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13517) Fix camel-netty4-http TLS tests
[ https://issues.apache.org/jira/browse/CAMEL-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-13517. --- Resolution: Fixed > Fix camel-netty4-http TLS tests > --- > > Key: CAMEL-13517 > URL: https://issues.apache.org/jira/browse/CAMEL-13517 > Project: Camel > Issue Type: Bug > Components: camel-netty4-http >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.0.0-M3 > > > The keystore used in TLS tests for contains a expired certificate for a DSA > key. This narrows down the cipher selection to disabled ciphers and the only > cipher available is the NULL with NULL cipher, making any TLS handshake > virtually impossible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13519) Camel-AWS SNS: Support encryption parameter when the creation of the topic is needed
Andrea Cosentino created CAMEL-13519: Summary: Camel-AWS SNS: Support encryption parameter when the creation of the topic is needed Key: CAMEL-13519 URL: https://issues.apache.org/jira/browse/CAMEL-13519 Project: Camel Issue Type: Task Components: camel-aws-msk Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.0.0, 3.0.0-M3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13518) Camel-AWS SNS: Support filter policies during subscription
Andrea Cosentino created CAMEL-13518: Summary: Camel-AWS SNS: Support filter policies during subscription Key: CAMEL-13518 URL: https://issues.apache.org/jira/browse/CAMEL-13518 Project: Camel Issue Type: Task Components: camel-aws-sns Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.0.0, 3.0.0-M3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13517) Fix camel-netty4-http TLS tests
Zoran Regvart created CAMEL-13517: - Summary: Fix camel-netty4-http TLS tests Key: CAMEL-13517 URL: https://issues.apache.org/jira/browse/CAMEL-13517 Project: Camel Issue Type: Bug Components: camel-netty4-http Reporter: Zoran Regvart Assignee: Zoran Regvart Fix For: 3.0.0-M3 The keystore used in TLS tests for contains a expired certificate for a DSA key. This narrows down the cipher selection to disabled ciphers and the only cipher available is the NULL with NULL cipher, making any TLS handshake virtually impossible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13516) camel-webhook - Consumer polish
Claus Ibsen created CAMEL-13516: --- Summary: camel-webhook - Consumer polish Key: CAMEL-13516 URL: https://issues.apache.org/jira/browse/CAMEL-13516 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Should extend ServiceSupport and do its startup stop in doStart/doStop etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13136) File consumer with charset doesn't parse XML
[
https://issues.apache.org/jira/browse/CAMEL-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839236#comment-16839236
]
Tadayoshi Sato commented on CAMEL-13136:
Thanks [~davsclaus]. Yes, you are right. We can directly refer to {{IOHelper}}
from {{GenericFileConverter}}. I'm making a pull req that applies the needed
changes.
> File consumer with charset doesn't parse XML
>
>
> Key: CAMEL-13136
> URL: https://issues.apache.org/jira/browse/CAMEL-13136
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 3.0.0-M1
>Reporter: Thomas Diesler
>Assignee: Tadayoshi Sato
>Priority: Major
> Fix For: 3.0.0
>
>
> This now shows on camel-3.0
> https://issues.jboss.org/browse/ENTESB-10033
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13514) camel3 - Service start/stop should use unchecked exceptions
[ https://issues.apache.org/jira/browse/CAMEL-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13514: Fix Version/s: 3.0.0-M3 > camel3 - Service start/stop should use unchecked exceptions > --- > > Key: CAMEL-13514 > URL: https://issues.apache.org/jira/browse/CAMEL-13514 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > > The API for org.apache.camel.Service has throws Exception for its start/stop > methods. It would be great to remove those, as they throw runtime exceptions > when failing, and this makes using these APIs easier for end users, so they > dont have the burden of checked exceptions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13514) camel3 - Service start/stop should use unchecked exceptions
[ https://issues.apache.org/jira/browse/CAMEL-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-13514: --- Assignee: Claus Ibsen > camel3 - Service start/stop should use unchecked exceptions > --- > > Key: CAMEL-13514 > URL: https://issues.apache.org/jira/browse/CAMEL-13514 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > The API for org.apache.camel.Service has throws Exception for its start/stop > methods. It would be great to remove those, as they throw runtime exceptions > when failing, and this makes using these APIs easier for end users, so they > dont have the burden of checked exceptions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-13136) File consumer with charset doesn't parse XML
[ https://issues.apache.org/jira/browse/CAMEL-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839190#comment-16839190 ] Claus Ibsen edited comment on CAMEL-13136 at 5/14/19 8:07 AM: -- camel-support uses camel-util, so it should be there? And you can try to use it from IOHelper instead was (Author: davsclaus): camel-support uses camel-util, so it should be there? > File consumer with charset doesn't parse XML > > > Key: CAMEL-13136 > URL: https://issues.apache.org/jira/browse/CAMEL-13136 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.0.0-M1 >Reporter: Thomas Diesler >Assignee: Tadayoshi Sato >Priority: Major > Fix For: 3.0.0 > > > This now shows on camel-3.0 > https://issues.jboss.org/browse/ENTESB-10033 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13136) File consumer with charset doesn't parse XML
[ https://issues.apache.org/jira/browse/CAMEL-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839190#comment-16839190 ] Claus Ibsen commented on CAMEL-13136: - camel-support uses camel-util, so it should be there? > File consumer with charset doesn't parse XML > > > Key: CAMEL-13136 > URL: https://issues.apache.org/jira/browse/CAMEL-13136 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.0.0-M1 >Reporter: Thomas Diesler >Assignee: Tadayoshi Sato >Priority: Major > Fix For: 3.0.0 > > > This now shows on camel-3.0 > https://issues.jboss.org/browse/ENTESB-10033 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13480) camel3 - docs - Cleanup reference to camel 2.x
[ https://issues.apache.org/jira/browse/CAMEL-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839174#comment-16839174 ] Claus Ibsen commented on CAMEL-13480: - Yeah sep-oct timeframe > camel3 - docs - Cleanup reference to camel 2.x > -- > > Key: CAMEL-13480 > URL: https://issues.apache.org/jira/browse/CAMEL-13480 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > For Camel 3 release we should cleanup all the docs with references for Camel > 2.x version stuff, so we can start from a "fresh". As all the docs going > forward will be versioned and part of the release. > So for example if you look at Camel 3.3.0 then the docs are for this release, > and if you use Camel 3.1.0, then you can find its docs and so on. > People are welcome to help, the current set of docs are the adoc files in the > source code, which you can help cleanup and submit PRs. We love contributions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13480) camel3 - docs - Cleanup reference to camel 2.x
[ https://issues.apache.org/jira/browse/CAMEL-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839162#comment-16839162 ] Alexandros Koufoudakis commented on CAMEL-13480: Thanks! Which is still "after summer 2019"? > camel3 - docs - Cleanup reference to camel 2.x > -- > > Key: CAMEL-13480 > URL: https://issues.apache.org/jira/browse/CAMEL-13480 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > For Camel 3 release we should cleanup all the docs with references for Camel > 2.x version stuff, so we can start from a "fresh". As all the docs going > forward will be versioned and part of the release. > So for example if you look at Camel 3.3.0 then the docs are for this release, > and if you use Camel 3.1.0, then you can find its docs and so on. > People are welcome to help, the current set of docs are the adoc files in the > source code, which you can help cleanup and submit PRs. We love contributions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13515) Allow producer to lazy start until first message
Claus Ibsen created CAMEL-13515: --- Summary: Allow producer to lazy start until first message Key: CAMEL-13515 URL: https://issues.apache.org/jira/browse/CAMEL-13515 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen We could add option to DefaultProducer so any producer allows to defer its startup (doStart) to when the first message is being processed. The danger is that the startup logic has to be thread-safe and if there are concurrent messages then they would need to hold back until the startup is done. This is a trade-off that the user would need to accept if enabled. But this can make it easier to let Camel startup routes even if some remote server is not available when a producer startup as part of route startup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13501) Component should move initialization logic to doInit instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-13501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839143#comment-16839143 ] Claus Ibsen commented on CAMEL-13501: - We could consider having when you set route auto startup = false, to let the consumer/producers of components etc only do init so they are only initialized, and then when you start the route, they are started. Then they are warmed up even more. Today the consumers are not warmedup. But on the other side the producers are started. What we want for producers is also to only initialize them, and start them when the route starts. But to make this easier, we could have when auto startup = false - routes and all its consumers, producers, eips are warmed up with only init - start is called on the route, then all its producers, eips are started, and the consumer started last. Then they have the same lifecycle. And allows safely to warmup and initalize resources. > Component should move initialization logic to doInit instead of doStart > --- > > Key: CAMEL-13501 > URL: https://issues.apache.org/jira/browse/CAMEL-13501 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > We should move logic that can be executed once during build/compile phase for > components to doInit, and then leave doStart to when components need to setup > live connections to remote systems etc. > In doInit we can do internal init such as setup a thread pool or other stuff > they need. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
