[jira] [Resolved] (CAMEL-18167) aws2-s3 get a download link does not work in browser when checksum enabled
[ https://issues.apache.org/jira/browse/CAMEL-18167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Feng resolved CAMEL-18167. Resolution: Fixed > aws2-s3 get a download link does not work in browser when checksum enabled > -- > > Key: CAMEL-18167 > URL: https://issues.apache.org/jira/browse/CAMEL-18167 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Affects Versions: 3.17.0 >Reporter: Zheng Feng >Assignee: Zheng Feng >Priority: Major > Fix For: 3.18.0 > > > This issue comes across [https://github.com/apache/camel-quarkus/issues/3829] > I think it could be better to check > [PresignedRequest.isBrowserExecutable()|https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/awscore/presigner/PresignedRequest.html#isBrowserExecutable--] > flag and show a message when it is false. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18176) Create a camel-hashicorp-vault test-infra module
Andrea Cosentino created CAMEL-18176: Summary: Create a camel-hashicorp-vault test-infra module Key: CAMEL-18176 URL: https://issues.apache.org/jira/browse/CAMEL-18176 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.18.0 To have a way to test the vault locally -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-17689) Create a Camel Hashicorp Vault Component
[ https://issues.apache.org/jira/browse/CAMEL-17689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17551607#comment-17551607 ] Andrea Cosentino commented on CAMEL-17689: -- TODO: - Support reading secrets as operation - Improving docs with examples - Create Spring Boot starter > Create a Camel Hashicorp Vault Component > > > Key: CAMEL-17689 > URL: https://issues.apache.org/jira/browse/CAMEL-17689 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.0 > > > https://github.com/spring-projects/spring-vault -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-17689) Create a Camel Hashicorp Vault Component
[ https://issues.apache.org/jira/browse/CAMEL-17689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17689: - Fix Version/s: 3.18.0 (was: 3.x) > Create a Camel Hashicorp Vault Component > > > Key: CAMEL-17689 > URL: https://issues.apache.org/jira/browse/CAMEL-17689 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.0 > > > https://github.com/spring-projects/spring-vault -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18175) camel-jbang - Download artifacts problem when they have custom classifier
Claus Ibsen created CAMEL-18175: --- Summary: camel-jbang - Download artifacts problem when they have custom classifier Key: CAMEL-18175 URL: https://issues.apache.org/jira/browse/CAMEL-18175 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.18.0 Such as camel-jira where atlassiant has a special jar that are built by some custom maven plugin and it sets atlassian-plugin then this confused apache ivy/groovy grape downloader. Similar for osgi with osgi -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-18151) camel-jbang - Export to Quarkus and Spring Boot maven projects
[ https://issues.apache.org/jira/browse/CAMEL-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17551587#comment-17551587 ] Claus Ibsen commented on CAMEL-18151: - TODO: Add option to log output of silent run that can be used for trouble shooting > camel-jbang - Export to Quarkus and Spring Boot maven projects > -- > > Key: CAMEL-18151 > URL: https://issues.apache.org/jira/browse/CAMEL-18151 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18172) camel-core - Eagerly resolve ref language when static to optimize
[
https://issues.apache.org/jira/browse/CAMEL-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18172.
-
Resolution: Fixed
> camel-core - Eagerly resolve ref language when static to optimize
> -
>
> Key: CAMEL-18172
> URL: https://issues.apache.org/jira/browse/CAMEL-18172
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.0
>
>
> The default RefLanguage component lazily resolve the ref expression hence it
> does not work with kamelets as the route template engine leverages a
> ThreadLocal bean repository to reify the route template, then such repo si
> cleared out and not more known by the routing engine.
> A way to workaround it is to create a custom ref language, as example:
> {code:java}
> import org.apache.camel.Expression;
> import org.apache.camel.Predicate;
> import org.apache.camel.language.ref.RefLanguage;
> import org.apache.camel.support.PredicateToExpressionAdapter;
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> public class EagerRefLanguage extends RefLanguage {
> private static final Logger LOGGER =
> LoggerFactory.getLogger(EagerRefLanguage.class);
> @Override
> public Expression createExpression(final String expression) {
> Expression exp =
> getCamelContext().getRegistry().lookupByNameAndType(expression,
> Expression.class);
> if (exp != null) {
> LOGGER.debug("Found and instance of {} expression in the registry
> {}", expression, exp);
> exp.init(getCamelContext());
> return exp;
> }
> Predicate pred =
> getCamelContext().getRegistry().lookupByNameAndType(expression,
> Predicate.class);
> if (pred != null) {
> LOGGER.debug("Found and instance of {} predicate in the registry
> {}", expression, pred);
> pred.init(getCamelContext());
> return PredicateToExpressionAdapter.toExpression(pred);
> }
> return super.createExpression(expression);
> }
> }
> {code}
> And bind it to the registry so camel will use as beans from the registry ahve
> priority over discovery form service loader.
> This is clearly an hack but we may want to bring such optimization to camel
> core, so i.e. if a ref expression is not dynamic, then we can load it when
> the ref is reified.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18172) camel-core - Eagerly resolve ref language when static to optimize
[
https://issues.apache.org/jira/browse/CAMEL-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18172:
Summary: camel-core - Eagerly resolve ref language when static to optimize
(was: camel-core - Eagerly resolve ref language)
> camel-core - Eagerly resolve ref language when static to optimize
> -
>
> Key: CAMEL-18172
> URL: https://issues.apache.org/jira/browse/CAMEL-18172
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.0
>
>
> The default RefLanguage component lazily resolve the ref expression hence it
> does not work with kamelets as the route template engine leverages a
> ThreadLocal bean repository to reify the route template, then such repo si
> cleared out and not more known by the routing engine.
> A way to workaround it is to create a custom ref language, as example:
> {code:java}
> import org.apache.camel.Expression;
> import org.apache.camel.Predicate;
> import org.apache.camel.language.ref.RefLanguage;
> import org.apache.camel.support.PredicateToExpressionAdapter;
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> public class EagerRefLanguage extends RefLanguage {
> private static final Logger LOGGER =
> LoggerFactory.getLogger(EagerRefLanguage.class);
> @Override
> public Expression createExpression(final String expression) {
> Expression exp =
> getCamelContext().getRegistry().lookupByNameAndType(expression,
> Expression.class);
> if (exp != null) {
> LOGGER.debug("Found and instance of {} expression in the registry
> {}", expression, exp);
> exp.init(getCamelContext());
> return exp;
> }
> Predicate pred =
> getCamelContext().getRegistry().lookupByNameAndType(expression,
> Predicate.class);
> if (pred != null) {
> LOGGER.debug("Found and instance of {} predicate in the registry
> {}", expression, pred);
> pred.init(getCamelContext());
> return PredicateToExpressionAdapter.toExpression(pred);
> }
> return super.createExpression(expression);
> }
> }
> {code}
> And bind it to the registry so camel will use as beans from the registry ahve
> priority over discovery form service loader.
> This is clearly an hack but we may want to bring such optimization to camel
> core, so i.e. if a ref expression is not dynamic, then we can load it when
> the ref is reified.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18172) camel-core - Eagerly resolve ref language
[
https://issues.apache.org/jira/browse/CAMEL-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18172:
Summary: camel-core - Eagerly resolve ref language (was: Eagerly resolve
ref language)
> camel-core - Eagerly resolve ref language
> -
>
> Key: CAMEL-18172
> URL: https://issues.apache.org/jira/browse/CAMEL-18172
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.0
>
>
> The default RefLanguage component lazily resolve the ref expression hence it
> does not work with kamelets as the route template engine leverages a
> ThreadLocal bean repository to reify the route template, then such repo si
> cleared out and not more known by the routing engine.
> A way to workaround it is to create a custom ref language, as example:
> {code:java}
> import org.apache.camel.Expression;
> import org.apache.camel.Predicate;
> import org.apache.camel.language.ref.RefLanguage;
> import org.apache.camel.support.PredicateToExpressionAdapter;
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> public class EagerRefLanguage extends RefLanguage {
> private static final Logger LOGGER =
> LoggerFactory.getLogger(EagerRefLanguage.class);
> @Override
> public Expression createExpression(final String expression) {
> Expression exp =
> getCamelContext().getRegistry().lookupByNameAndType(expression,
> Expression.class);
> if (exp != null) {
> LOGGER.debug("Found and instance of {} expression in the registry
> {}", expression, exp);
> exp.init(getCamelContext());
> return exp;
> }
> Predicate pred =
> getCamelContext().getRegistry().lookupByNameAndType(expression,
> Predicate.class);
> if (pred != null) {
> LOGGER.debug("Found and instance of {} predicate in the registry
> {}", expression, pred);
> pred.init(getCamelContext());
> return PredicateToExpressionAdapter.toExpression(pred);
> }
> return super.createExpression(expression);
> }
> }
> {code}
> And bind it to the registry so camel will use as beans from the registry ahve
> priority over discovery form service loader.
> This is clearly an hack but we may want to bring such optimization to camel
> core, so i.e. if a ref expression is not dynamic, then we can load it when
> the ref is reified.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (CAMEL-18172) Eagerly resolve ref language
[
https://issues.apache.org/jira/browse/CAMEL-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-18172:
---
Assignee: Claus Ibsen
> Eagerly resolve ref language
>
>
> Key: CAMEL-18172
> URL: https://issues.apache.org/jira/browse/CAMEL-18172
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.0
>
>
> The default RefLanguage component lazily resolve the ref expression hence it
> does not work with kamelets as the route template engine leverages a
> ThreadLocal bean repository to reify the route template, then such repo si
> cleared out and not more known by the routing engine.
> A way to workaround it is to create a custom ref language, as example:
> {code:java}
> import org.apache.camel.Expression;
> import org.apache.camel.Predicate;
> import org.apache.camel.language.ref.RefLanguage;
> import org.apache.camel.support.PredicateToExpressionAdapter;
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> public class EagerRefLanguage extends RefLanguage {
> private static final Logger LOGGER =
> LoggerFactory.getLogger(EagerRefLanguage.class);
> @Override
> public Expression createExpression(final String expression) {
> Expression exp =
> getCamelContext().getRegistry().lookupByNameAndType(expression,
> Expression.class);
> if (exp != null) {
> LOGGER.debug("Found and instance of {} expression in the registry
> {}", expression, exp);
> exp.init(getCamelContext());
> return exp;
> }
> Predicate pred =
> getCamelContext().getRegistry().lookupByNameAndType(expression,
> Predicate.class);
> if (pred != null) {
> LOGGER.debug("Found and instance of {} predicate in the registry
> {}", expression, pred);
> pred.init(getCamelContext());
> return PredicateToExpressionAdapter.toExpression(pred);
> }
> return super.createExpression(expression);
> }
> }
> {code}
> And bind it to the registry so camel will use as beans from the registry ahve
> priority over discovery form service loader.
> This is clearly an hack but we may want to bring such optimization to camel
> core, so i.e. if a ref expression is not dynamic, then we can load it when
> the ref is reified.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (CAMEL-18174) camel-resume-api: allow intermittent offsets
Otavio Rodolfo Piske created CAMEL-18174: Summary: camel-resume-api: allow intermittent offsets Key: CAMEL-18174 URL: https://issues.apache.org/jira/browse/CAMEL-18174 Project: Camel Issue Type: Task Components: camel-resume-api Affects Versions: 3.17.0 Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Fix For: 3.18.0 In some circumstances the offset may not be present in all the exchanges. Currently the resume API throws an error if this happen. It should be modified to allow users to set intermittent mode. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18173) camel-jbang - Add option to turn off download over the internet
[ https://issues.apache.org/jira/browse/CAMEL-18173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18173. - Resolution: Fixed > camel-jbang - Add option to turn off download over the internet > --- > > Key: CAMEL-18173 > URL: https://issues.apache.org/jira/browse/CAMEL-18173 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18173) camel-jbang - Add option to turn off download over the internet
Claus Ibsen created CAMEL-18173: --- Summary: camel-jbang - Add option to turn off download over the internet Key: CAMEL-18173 URL: https://issues.apache.org/jira/browse/CAMEL-18173 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.18.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18172) Eagerly resolve ref language
Luca Burgazzoli created CAMEL-18172:
---
Summary: Eagerly resolve ref language
Key: CAMEL-18172
URL: https://issues.apache.org/jira/browse/CAMEL-18172
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Luca Burgazzoli
Fix For: 3.18.0
The default RefLanguage component lazily resolve the ref expression hence it
does not work with kamelets as the route template engine leverages a
ThreadLocal bean repository to reify the route template, then such repo si
cleared out and not more known by the routing engine.
A way to workaround it is to create a custom ref language, as example:
{code:java}
import org.apache.camel.Expression;
import org.apache.camel.Predicate;
import org.apache.camel.language.ref.RefLanguage;
import org.apache.camel.support.PredicateToExpressionAdapter;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
public class EagerRefLanguage extends RefLanguage {
private static final Logger LOGGER =
LoggerFactory.getLogger(EagerRefLanguage.class);
@Override
public Expression createExpression(final String expression) {
Expression exp =
getCamelContext().getRegistry().lookupByNameAndType(expression,
Expression.class);
if (exp != null) {
LOGGER.debug("Found and instance of {} expression in the registry
{}", expression, exp);
exp.init(getCamelContext());
return exp;
}
Predicate pred =
getCamelContext().getRegistry().lookupByNameAndType(expression,
Predicate.class);
if (pred != null) {
LOGGER.debug("Found and instance of {} predicate in the registry
{}", expression, pred);
pred.init(getCamelContext());
return PredicateToExpressionAdapter.toExpression(pred);
}
return super.createExpression(expression);
}
}
{code}
And bind it to the registry so camel will use as beans from the registry ahve
priority over discovery form service loader.
This is clearly an hack but we may want to bring such optimization to camel
core, so i.e. if a ref expression is not dynamic, then we can load it when the
ref is reified.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (CAMEL-18044) camel-infinispan: Avoid usage of JBossUserMarshaller in InfinispanRemoteAggregationRepository
[ https://issues.apache.org/jira/browse/CAMEL-18044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton reassigned CAMEL-18044: --- Assignee: James Netherton > camel-infinispan: Avoid usage of JBossUserMarshaller in > InfinispanRemoteAggregationRepository > - > > Key: CAMEL-18044 > URL: https://issues.apache.org/jira/browse/CAMEL-18044 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan >Reporter: James Netherton >Assignee: James Netherton >Priority: Major > Fix For: 3.18.0 > > > Dependency infinispan-jboss-marshalling and therefore usage of > JBossUserMarshaller is deprecated for removal in Infinispan 14, so we should > look to see if there are better alternatives. > Probably the simplest replacement would be to use > JavaSerializationMarshaller. But as per the comment linked to below, it > should perhaps be considered whether Java serialization is the correct > approach. > https://github.com/apache/camel/blob/main/components/camel-infinispan/camel-infinispan/src/main/java/org/apache/camel/component/infinispan/remote/InfinispanRemoteAggregationRepository.java#L57-L77 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (CAMEL-18045) camel-infinispan: Avoid usage of Protostuff marshaller
[ https://issues.apache.org/jira/browse/CAMEL-18045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton reassigned CAMEL-18045: --- Assignee: James Netherton > camel-infinispan: Avoid usage of Protostuff marshaller > -- > > Key: CAMEL-18045 > URL: https://issues.apache.org/jira/browse/CAMEL-18045 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan >Reporter: James Netherton >Assignee: James Netherton >Priority: Major > Fix For: 3.18.0 > > > Dependency infinispan-marshaller-protostuff is deprecated for removal in > Infinispan 15.x so it'd be good to start thinking of a replacement sooner > than later. E.g by using the more modern protostream marshaller. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-18170) Add serviceAccountKey parameter to google components
[
https://issues.apache.org/jira/browse/CAMEL-18170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17551404#comment-17551404
]
Otavio Rodolfo Piske commented on CAMEL-18170:
--
[~rhuanrcoha] thanks for looking at this one. I assigned it to myself as
requested.
> Add serviceAccountKey parameter to google components
>
>
> Key: CAMEL-18170
> URL: https://issues.apache.org/jira/browse/CAMEL-18170
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-calendar, camel-google-drive,
> camel-google-mail, camel-google-sheets
>Reporter: Claudio Miranda
>Assignee: Otavio Rodolfo Piske
>Priority: Minor
>
> Add support to use {{service account key}} parameter to google components:
> sheets, calendar, mail, drive.
> Similar to google bigquery component.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (CAMEL-18170) Add serviceAccountKey parameter to google components
[
https://issues.apache.org/jira/browse/CAMEL-18170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske reassigned CAMEL-18170:
Assignee: Otavio Rodolfo Piske
> Add serviceAccountKey parameter to google components
>
>
> Key: CAMEL-18170
> URL: https://issues.apache.org/jira/browse/CAMEL-18170
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-calendar, camel-google-drive,
> camel-google-mail, camel-google-sheets
>Reporter: Claudio Miranda
>Assignee: Otavio Rodolfo Piske
>Priority: Minor
>
> Add support to use {{service account key}} parameter to google components:
> sheets, calendar, mail, drive.
> Similar to google bigquery component.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (CAMEL-18170) Add serviceAccountKey parameter to google components
[
https://issues.apache.org/jira/browse/CAMEL-18170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske reassigned CAMEL-18170:
Assignee: (was: Otavio Rodolfo Piske)
> Add serviceAccountKey parameter to google components
>
>
> Key: CAMEL-18170
> URL: https://issues.apache.org/jira/browse/CAMEL-18170
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-calendar, camel-google-drive,
> camel-google-mail, camel-google-sheets
>Reporter: Claudio Miranda
>Priority: Minor
>
> Add support to use {{service account key}} parameter to google components:
> sheets, calendar, mail, drive.
> Similar to google bigquery component.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (CAMEL-18170) Add serviceAccountKey parameter to google components
[
https://issues.apache.org/jira/browse/CAMEL-18170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske reassigned CAMEL-18170:
Assignee: Otavio Rodolfo Piske
> Add serviceAccountKey parameter to google components
>
>
> Key: CAMEL-18170
> URL: https://issues.apache.org/jira/browse/CAMEL-18170
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-calendar, camel-google-drive,
> camel-google-mail, camel-google-sheets
>Reporter: Claudio Miranda
>Assignee: Otavio Rodolfo Piske
>Priority: Minor
>
> Add support to use {{service account key}} parameter to google components:
> sheets, calendar, mail, drive.
> Similar to google bigquery component.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
