[jira] [Assigned] (CAMEL-18317) camel-salesforce - Endpoint syntax should have mandatory operationName
[
https://issues.apache.org/jira/browse/CAMEL-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Ross reassigned CAMEL-18317:
---
Assignee: Jeremy Ross
> camel-salesforce - Endpoint syntax should have mandatory operationName
> --
>
> Key: CAMEL-18317
> URL: https://issues.apache.org/jira/browse/CAMEL-18317
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
>Reporter: Claus Ibsen
>Assignee: Jeremy Ross
>Priority: Major
> Fix For: 3.19.0
>
>
> Today both the operationName and topicName are marked as optional - which
> makes the logic to parse the uri complex.
> A rule in Camel is that only one path parameter can be optional.
> It would be better to make operationName mandatory and add an operation for
> the consumer (what would be a good name, listen, consume, onMessage?), so you
> would do
> from("salesforce:listen:cheese")
> And in the uri for the producer uses the operationName already, where
> topicName is not in use.
> to("salesforce:updateSObject")
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18357) camel-core - Splitter issue with tokenizer with hashNext/next
Claus Ibsen created CAMEL-18357: --- Summary: camel-core - Splitter issue with tokenizer with hashNext/next Key: CAMEL-18357 URL: https://issues.apache.org/jira/browse/CAMEL-18357 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 3.18.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.18.2, 3.19.0 We suspect that splitter in streaming mode may call hasNext too frequently. Bruno M reported this to me, need to find time to investigate. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18353) camel-test - Upgrade to JUnit 5.9.x
[ https://issues.apache.org/jira/browse/CAMEL-18353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18353. - Resolution: Fixed > camel-test - Upgrade to JUnit 5.9.x > --- > > Key: CAMEL-18353 > URL: https://issues.apache.org/jira/browse/CAMEL-18353 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-test >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > There is a new 5.9.0 release and we use 5.8.x currently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18347) camel-test-infra: instances are not properly singleton
[ https://issues.apache.org/jira/browse/CAMEL-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-18347. -- Resolution: Fixed Fixed with the linked PRs. > camel-test-infra: instances are not properly singleton > -- > > Key: CAMEL-18347 > URL: https://issues.apache.org/jira/browse/CAMEL-18347 > Project: Camel > Issue Type: Bug > Components: camel-test-infra-arangodb, camel-test-infra-hbase, > camel-test-infra-kafka, camel-test-infra-mongodb >Affects Versions: 3.18.0, 3.19.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.18.2, 3.19.0 > > > Despite being advertised as singleton, the test infra still create multiple > instances of the services. This can slow down test execution and use more > resources than necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18347) camel-test-infra: instances are not properly singleton
[ https://issues.apache.org/jira/browse/CAMEL-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-18347: - Fix Version/s: 3.18.2 3.19.0 > camel-test-infra: instances are not properly singleton > -- > > Key: CAMEL-18347 > URL: https://issues.apache.org/jira/browse/CAMEL-18347 > Project: Camel > Issue Type: Bug > Components: camel-test-infra-arangodb, camel-test-infra-hbase, > camel-test-infra-kafka, camel-test-infra-mongodb >Affects Versions: 3.18.0, 3.19.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.18.2, 3.19.0 > > > Despite being advertised as singleton, the test infra still create multiple > instances of the services. This can slow down test execution and use more > resources than necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18347) camel-test-infra: instances are not properly singleton
[ https://issues.apache.org/jira/browse/CAMEL-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske reassigned CAMEL-18347: Assignee: Otavio Rodolfo Piske > camel-test-infra: instances are not properly singleton > -- > > Key: CAMEL-18347 > URL: https://issues.apache.org/jira/browse/CAMEL-18347 > Project: Camel > Issue Type: Bug > Components: camel-test-infra-arangodb, camel-test-infra-hbase, > camel-test-infra-kafka, camel-test-infra-mongodb >Affects Versions: 3.18.0, 3.19.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > > Despite being advertised as singleton, the test infra still create multiple > instances of the services. This can slow down test execution and use more > resources than necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18354) Camel AWS Cloudtrail: Create Karaf feature
[ https://issues.apache.org/jira/browse/CAMEL-18354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18354. -- Resolution: Fixed > Camel AWS Cloudtrail: Create Karaf feature > -- > > Key: CAMEL-18354 > URL: https://issues.apache.org/jira/browse/CAMEL-18354 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18351) ExchangePropertyKey.SPLIT_COMPLETE not set to true after zip splitting completed
[ https://issues.apache.org/jira/browse/CAMEL-18351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575708#comment-17575708 ] Alexander Lex commented on CAMEL-18351: --- Suggested fix: hasNext should look if there is a ZipInputStream::getNextEntry() and not if in the current ZipInputStream data is available > ExchangePropertyKey.SPLIT_COMPLETE not set to true after zip splitting > completed > > > Key: CAMEL-18351 > URL: https://issues.apache.org/jira/browse/CAMEL-18351 > Project: Camel > Issue Type: Bug > Components: camel-zipfile >Affects Versions: 3.18.0 >Reporter: Alexander Lex >Priority: Minor > > When running the zip splitter, it splits the zip file as expected. However, > looking at the property "ExchangePropertyKey.SPLIT_COMPLETE", it shows not > the expected "true". > > Expected behaviour is the property "ExchangePropertyKey.SPLIT_COMPLETE" to be > set to true after the splitting is completed. > > Code to reproduce can be found here: > https://github.com/lx183/camel-zip-issue/blob/master/src/test/java/ZipSplitterRouteTest.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18356) camel-resume-api: consolidade Kafka's single and multi strategies
Otavio Rodolfo Piske created CAMEL-18356: Summary: camel-resume-api: consolidade Kafka's single and multi strategies Key: CAMEL-18356 URL: https://issues.apache.org/jira/browse/CAMEL-18356 Project: Camel Issue Type: Improvement Components: camel-resume-api Reporter: Otavio Rodolfo Piske We should only have one resume strategy in the Kafka component. It makes everything simpler. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18351) ExchangePropertyKey.SPLIT_COMPLETE not set to true after zip splitting completed
[ https://issues.apache.org/jira/browse/CAMEL-18351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575679#comment-17575679 ] Alexander Lex commented on CAMEL-18351: --- The hasNext always returns true, even if it is the last element. From my understanding, this is why the SPLIT_COMPLETE will not be true. Sorry, I have only run debug until this point the code. > ExchangePropertyKey.SPLIT_COMPLETE not set to true after zip splitting > completed > > > Key: CAMEL-18351 > URL: https://issues.apache.org/jira/browse/CAMEL-18351 > Project: Camel > Issue Type: Bug > Components: camel-zipfile >Affects Versions: 3.18.0 >Reporter: Alexander Lex >Priority: Minor > > When running the zip splitter, it splits the zip file as expected. However, > looking at the property "ExchangePropertyKey.SPLIT_COMPLETE", it shows not > the expected "true". > > Expected behaviour is the property "ExchangePropertyKey.SPLIT_COMPLETE" to be > set to true after the splitting is completed. > > Code to reproduce can be found here: > https://github.com/lx183/camel-zip-issue/blob/master/src/test/java/ZipSplitterRouteTest.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18351) ExchangePropertyKey.SPLIT_COMPLETE not set to true after zip splitting completed
[ https://issues.apache.org/jira/browse/CAMEL-18351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575648#comment-17575648 ] Claus Ibsen commented on CAMEL-18351: - Can you point out exactly what you see as wrong in that hasNext method? And do you have a suggested fix? > ExchangePropertyKey.SPLIT_COMPLETE not set to true after zip splitting > completed > > > Key: CAMEL-18351 > URL: https://issues.apache.org/jira/browse/CAMEL-18351 > Project: Camel > Issue Type: Bug > Components: camel-zipfile >Affects Versions: 3.18.0 >Reporter: Alexander Lex >Priority: Minor > > When running the zip splitter, it splits the zip file as expected. However, > looking at the property "ExchangePropertyKey.SPLIT_COMPLETE", it shows not > the expected "true". > > Expected behaviour is the property "ExchangePropertyKey.SPLIT_COMPLETE" to be > set to true after the splitting is completed. > > Code to reproduce can be found here: > https://github.com/lx183/camel-zip-issue/blob/master/src/test/java/ZipSplitterRouteTest.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18351) ExchangePropertyKey.SPLIT_COMPLETE not set to true after zip splitting completed
[ https://issues.apache.org/jira/browse/CAMEL-18351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575643#comment-17575643 ] Alexander Lex commented on CAMEL-18351: --- Thank you for the quick response and the tip. However, as low prio issue, i still think the hasNext behaviour should be considered as bug. If I am also wrong here, you can close the issue. > ExchangePropertyKey.SPLIT_COMPLETE not set to true after zip splitting > completed > > > Key: CAMEL-18351 > URL: https://issues.apache.org/jira/browse/CAMEL-18351 > Project: Camel > Issue Type: Bug > Components: camel-zipfile >Affects Versions: 3.18.0 >Reporter: Alexander Lex >Priority: Minor > > When running the zip splitter, it splits the zip file as expected. However, > looking at the property "ExchangePropertyKey.SPLIT_COMPLETE", it shows not > the expected "true". > > Expected behaviour is the property "ExchangePropertyKey.SPLIT_COMPLETE" to be > set to true after the splitting is completed. > > Code to reproduce can be found here: > https://github.com/lx183/camel-zip-issue/blob/master/src/test/java/ZipSplitterRouteTest.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18355) HTTP component overwrites basic authentication credentials with proxy authentication
[
https://issues.apache.org/jira/browse/CAMEL-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575623#comment-17575623
]
Claus Ibsen commented on CAMEL-18355:
-
You are welcome to work on a PR as you can then also test the code changes in
your system
> HTTP component overwrites basic authentication credentials with proxy
> authentication
> -
>
> Key: CAMEL-18355
> URL: https://issues.apache.org/jira/browse/CAMEL-18355
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.18.0
>Reporter: Oliver Holzmann
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> We use HTTP endpoints with basic authentication (params {{authUsername}},
> {{authPassword}}) via a proxy that requires proxy authentication (params
> {{proxyAuthUsername}}, {{proxyAuthPassword}}).
> But basic authentication fails. In debug logs we see that basic
> authentication header is using proxy credentials.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18355) HTTP component overwrites basic authentication credentials with proxy authentication
[
https://issues.apache.org/jira/browse/CAMEL-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18355:
Fix Version/s: 3.18.2
> HTTP component overwrites basic authentication credentials with proxy
> authentication
> -
>
> Key: CAMEL-18355
> URL: https://issues.apache.org/jira/browse/CAMEL-18355
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.18.0
>Reporter: Oliver Holzmann
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> We use HTTP endpoints with basic authentication (params {{authUsername}},
> {{authPassword}}) via a proxy that requires proxy authentication (params
> {{proxyAuthUsername}}, {{proxyAuthPassword}}).
> But basic authentication fails. In debug logs we see that basic
> authentication header is using proxy credentials.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18355) HTTP component overwrites basic authentication credentials with proxy authentication
[
https://issues.apache.org/jira/browse/CAMEL-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18355:
Fix Version/s: 3.19.0
> HTTP component overwrites basic authentication credentials with proxy
> authentication
> -
>
> Key: CAMEL-18355
> URL: https://issues.apache.org/jira/browse/CAMEL-18355
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.18.0
>Reporter: Oliver Holzmann
>Priority: Major
> Fix For: 3.19.0
>
>
> We use HTTP endpoints with basic authentication (params {{authUsername}},
> {{authPassword}}) via a proxy that requires proxy authentication (params
> {{proxyAuthUsername}}, {{proxyAuthPassword}}).
> But basic authentication fails. In debug logs we see that basic
> authentication header is using proxy credentials.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18355) HTTP component overwrites basic authentication credentials with proxy authentication
[
https://issues.apache.org/jira/browse/CAMEL-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575612#comment-17575612
]
Oliver Holzmann commented on CAMEL-18355:
-
I think
* {{ProxyHttpClientConfigurer}} needs to set the proxy credentials for the auth
scope of the proxy {{HttpHost}} instead of {{AuthScope.ANY}}
* and it must add new credential to a potentially existing
{{credentialsProvider}} of {{clientBuilder}}; currently
{{ProxyHttpClientConfigurer}} overwrites the {{credentialsProvider}} of
{{clientBuilder}} provided by {{BasicAuthenticationHttpClientConfigurer}}
> HTTP component overwrites basic authentication credentials with proxy
> authentication
> -
>
> Key: CAMEL-18355
> URL: https://issues.apache.org/jira/browse/CAMEL-18355
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.18.0
>Reporter: Oliver Holzmann
>Priority: Major
>
> We use HTTP endpoints with basic authentication (params {{authUsername}},
> {{authPassword}}) via a proxy that requires proxy authentication (params
> {{proxyAuthUsername}}, {{proxyAuthPassword}}).
> But basic authentication fails. In debug logs we see that basic
> authentication header is using proxy credentials.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18349) Core - XPathRouteConcurrentBigTest - newly added limit of "operators an XPath expression can contain." fails the test
[
https://issues.apache.org/jira/browse/CAMEL-18349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18349.
-
Fix Version/s: 3.18.1
Resolution: Fixed
> Core - XPathRouteConcurrentBigTest - newly added limit of "operators an XPath
> expression can contain." fails the test
> -
>
> Key: CAMEL-18349
> URL: https://issues.apache.org/jira/browse/CAMEL-18349
> Project: Camel
> Issue Type: Test
> Components: tests
>Affects Versions: 3.19.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
> Fix For: 3.18.1, 3.19.0
>
>
> In java 11.0.15, there is a security limitation for "the number of operators
> an XPath expression can contain. (see [release
> notes|https://www.oracle.com/java/technologies/javase/11-0-15-relnotes.html])
> with default value 100.
> Unfortunately the test _XPathRouteConcurrentBigTest_ requires 101
> {code:java}
> Caused by: javax.xml.transform.TransformerException: JAXP0801002: the
> compiler encountered an XPath expression containing '101' operators that
> exceeds the '100' limit set by 'FEATURE_SECURE_PROCESSING'.
> {code}
> Solution would be to change a test little bit, to require <= 100 operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18355) HTTP component overwrites basic authentication credentials with proxy authentication
Oliver Holzmann created CAMEL-18355:
---
Summary: HTTP component overwrites basic authentication
credentials with proxy authentication
Key: CAMEL-18355
URL: https://issues.apache.org/jira/browse/CAMEL-18355
Project: Camel
Issue Type: Bug
Components: camel-http
Affects Versions: 3.18.0
Reporter: Oliver Holzmann
We use HTTP endpoints with basic authentication (params {{authUsername}},
{{authPassword}}) via a proxy that requires proxy authentication (params
{{proxyAuthUsername}}, {{proxyAuthPassword}}).
But basic authentication fails. In debug logs we see that basic authentication
header is using proxy credentials.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18354) Camel AWS Cloudtrail: Create Karaf feature
Andrea Cosentino created CAMEL-18354: Summary: Camel AWS Cloudtrail: Create Karaf feature Key: CAMEL-18354 URL: https://issues.apache.org/jira/browse/CAMEL-18354 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
