[jira] [Commented] (CAMEL-13180) camel-salesforce - Apex calls could support more flexible response parsing
[ https://issues.apache.org/jira/browse/CAMEL-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488495#comment-17488495 ] Jesse Sightler commented on CAMEL-13180: I have tried it out and it looks like this will work fine for us. Thank you for the new feature! > camel-salesforce - Apex calls could support more flexible response parsing > -- > > Key: CAMEL-13180 > URL: https://issues.apache.org/jira/browse/CAMEL-13180 > Project: Camel > Issue Type: New Feature > Components: camel-salesforce >Reporter: Jesse Sightler >Assignee: Jeremy Ross >Priority: Major > Fix For: 3.15.0 > > > The current approach requires following a very strict format for error codes > other than 2xx. This isn't necessarily the case, though, for custom apex > classes. > Ideally, it would be possible to (optionally) handle the parsing in the camel > route itself. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17614) Be able to run infinispan spring-boot example out of the box
[ https://issues.apache.org/jira/browse/CAMEL-17614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang reassigned CAMEL-17614: Assignee: Freeman Yue Fang > Be able to run infinispan spring-boot example out of the box > > > Key: CAMEL-17614 > URL: https://issues.apache.org/jira/browse/CAMEL-17614 > Project: Camel > Issue Type: Task > Components: camel-spring-boot, examples >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > > currently the camel-spring-boot infinispan exmaple requires a separate > running Infinispan server. > I think it's better to be able to run this example OOTB, like start a docker > Infinispan server image and create the "default" cacheName if required(since > the default cache doesn't exist in latest Infinispan server ) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17614) Be able to run infinispan spring-boot example out of the box
Freeman Yue Fang created CAMEL-17614: Summary: Be able to run infinispan spring-boot example out of the box Key: CAMEL-17614 URL: https://issues.apache.org/jira/browse/CAMEL-17614 Project: Camel Issue Type: Task Components: camel-spring-boot, examples Reporter: Freeman Yue Fang currently the camel-spring-boot infinispan exmaple requires a separate running Infinispan server. I think it's better to be able to run this example OOTB, like start a docker Infinispan server image and create the "default" cacheName if required(since the default cache doesn't exist in latest Infinispan server ) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17613) Race condition in AggregateProcessor with Jdbc Repository
[ https://issues.apache.org/jira/browse/CAMEL-17613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin BONNET updated CAMEL-17613: Affects Version/s: 3.11.2 (was: 3.11.4) > Race condition in AggregateProcessor with Jdbc Repository > - > > Key: CAMEL-17613 > URL: https://issues.apache.org/jira/browse/CAMEL-17613 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-sql >Affects Versions: 3.11.2 >Reporter: Benjamin BONNET >Priority: Major > > Hi, > using aggregate with a JdbcAggregationRepository, we are encountering a race > condition that may leave a completed exchange in completed table even after > that completed exchange has been sent. Unfortunately, that leads to > duplicates since recovery task will eventually try and recover it. > Normally, when the exchange completes, it is deleted from repo exchange table > and inserted into repo completed exchange table. Then exchange is sent and > deleted from repo completed exchange table. > But, due to the fact those two actions are run by different threads (and in > different transactions) that order may vary. > > Here is a normal sequence : > AggregateProcessor.doProcess > doAggregation > doAggregationComplete > onCompletion > JdbcAggregationRepository.remove : => INSERT ... INTO _completed > onSubmitCompletion > AggregateOnCompletion.onComplete (via executorService) > JdbcAggregationRepository.confirm : => DELETE FROM _completed > With the use of executorService, confirm is run by another thread and may > commit before remove commits. Eventually, when that occurs, one can check > that DELETE statement returns 0 (number of deleted rows) instead of 1. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17589) Enable ITests of camel-infinispan on MacOSX
[ https://issues.apache.org/jira/browse/CAMEL-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488352#comment-17488352 ] Freeman Yue Fang commented on CAMEL-17589: -- camel-spring-boot has the same issue, apply the same fix there https://github.com/apache/camel-spring-boot/commit/d081b6ed001a0fa3a97f3eec8e39d5fdea8fe378 > Enable ITests of camel-infinispan on MacOSX > --- > > Key: CAMEL-17589 > URL: https://issues.apache.org/jira/browse/CAMEL-17589 > Project: Camel > Issue Type: Test > Components: camel-infinispan, tests > Environment: [link title|http://example.com] >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Minor > Fix For: 3.16.0 > > > Currently all Integration Tests of camel-infinispan are disabled for MAC, > because docker image is used and Docker Desktop on Mac has different network > configuration as Docker on Linux, this can cause issue when infinispan hotrod > client is trying to access an internal node/IP from the host(mac), more > details described > [here|https://infinispan.org/blog/2018/03/06/accessing-infinispan-inside-docker-for] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17610) camel-aws2-ses: Support CC and BCC as endpoint parameters
[ https://issues.apache.org/jira/browse/CAMEL-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17610. -- Resolution: Fixed > camel-aws2-ses: Support CC and BCC as endpoint parameters > - > > Key: CAMEL-17610 > URL: https://issues.apache.org/jira/browse/CAMEL-17610 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Billy Jaime Beltran >Priority: Minor > Labels: pull-request-available > Fix For: 3.16.0 > > > Currently CC and BCC are missing from the uri params but are supported by the > Amazon SDK. Patch so we can send cc and bcc just like we do with To without > having to manually create a javax mail instance. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17613) Race condition in AggregateProcessor with Jdbc Repository
Benjamin BONNET created CAMEL-17613: --- Summary: Race condition in AggregateProcessor with Jdbc Repository Key: CAMEL-17613 URL: https://issues.apache.org/jira/browse/CAMEL-17613 Project: Camel Issue Type: Bug Components: camel-core, camel-sql Affects Versions: 3.11.4 Reporter: Benjamin BONNET Hi, using aggregate with a JdbcAggregationRepository, we are encountering a race condition that may leave a completed exchange in completed table even after that completed exchange has been sent. Unfortunately, that leads to duplicates since recovery task will eventually try and recover it. Normally, when the exchange completes, it is deleted from repo exchange table and inserted into repo completed exchange table. Then exchange is sent and deleted from repo completed exchange table. But, due to the fact those two actions are run by different threads (and in different transactions) that order may vary. Here is a normal sequence : AggregateProcessor.doProcess doAggregation doAggregationComplete onCompletion JdbcAggregationRepository.remove : => INSERT ... INTO _completed onSubmitCompletion AggregateOnCompletion.onComplete (via executorService) JdbcAggregationRepository.confirm : => DELETE FROM _completed With the use of executorService, confirm is run by another thread and may commit before remove commits. Eventually, when that occurs, one can check that DELETE statement returns 0 (number of deleted rows) instead of 1. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17612) camel google functions documentation shows consumer example instead of producer
Zineb Bendhiba created CAMEL-17612:
--
Summary: camel google functions documentation shows consumer
example instead of producer
Key: CAMEL-17612
URL: https://issues.apache.org/jira/browse/CAMEL-17612
Project: Camel
Issue Type: Bug
Reporter: Zineb Bendhiba
The official documentation of Camel Google Cloud Functions component says that
the component is supported for Producer only.
However, this is a consumer example shown in the documentation
{code:java}
from("google-functions://myCamelFunction?project=myProject&location=us-central1&operation=callFunction&serviceAccountKey=/home/user/Downloads/my-key.json")
.to("direct:test");{code}
There's something wrong with the doc.
[https://camel.apache.org/components/3.14.x/google-functions-component.html]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17612) camel google functions documentation shows consumer example instead of producer
[
https://issues.apache.org/jira/browse/CAMEL-17612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zineb Bendhiba updated CAMEL-17612:
---
Affects Version/s: 3.14.1
> camel google functions documentation shows consumer example instead of
> producer
>
>
> Key: CAMEL-17612
> URL: https://issues.apache.org/jira/browse/CAMEL-17612
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.14.1
>Reporter: Zineb Bendhiba
>Priority: Major
>
> The official documentation of Camel Google Cloud Functions component says
> that the component is supported for Producer only.
> However, this is a consumer example shown in the documentation
> {code:java}
> from("google-functions://myCamelFunction?project=myProject&location=us-central1&operation=callFunction&serviceAccountKey=/home/user/Downloads/my-key.json")
>
> .to("direct:test");{code}
> There's something wrong with the doc.
> [https://camel.apache.org/components/3.14.x/google-functions-component.html]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17611) Allow to create a Route from a route template in XML and YAML
[
https://issues.apache.org/jira/browse/CAMEL-17611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17611:
Fix Version/s: 3.16.0
> Allow to create a Route from a route template in XML and YAML
> -
>
> Key: CAMEL-17611
> URL: https://issues.apache.org/jira/browse/CAMEL-17611
> Project: Camel
> Issue Type: Improvement
> Components: came-core
>Reporter: Nicolas Filotto
>Assignee: Nicolas Filotto
>Priority: Major
> Fix For: 3.16.0
>
>
> With the existing code it is possible to create a route from a route template
> thanks to TemplatedRouteBuilder with a pure Java code or simply with a
> Kamelet. However in some particular cases it could be interesting to be able
> to create routes from a route template from a pure XML or YAML file
> especially for camel users that don't want to use Kamelets and write Java
> code.
>
> So for example, following XML snippet would allow to instantiate a route
> whose id is "my-route" from the route template "myTemplate" with the 2
> parameters "for" and "bar" and the bean "myBean".
> {code:java}
>
>
>
> type="#class:org.apache.camel.spring.routebuilder.MySpecialBean">
>
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17611) Allow to create a Route from a route template in XML and YAML
[
https://issues.apache.org/jira/browse/CAMEL-17611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488137#comment-17488137
]
Claus Ibsen commented on CAMEL-17611:
-
Yeah sure
> Allow to create a Route from a route template in XML and YAML
> -
>
> Key: CAMEL-17611
> URL: https://issues.apache.org/jira/browse/CAMEL-17611
> Project: Camel
> Issue Type: Improvement
> Components: came-core
>Reporter: Nicolas Filotto
>Assignee: Nicolas Filotto
>Priority: Major
>
> With the existing code it is possible to create a route from a route template
> thanks to TemplatedRouteBuilder with a pure Java code or simply with a
> Kamelet. However in some particular cases it could be interesting to be able
> to create routes from a route template from a pure XML or YAML file
> especially for camel users that don't want to use Kamelets and write Java
> code.
>
> So for example, following XML snippet would allow to instantiate a route
> whose id is "my-route" from the route template "myTemplate" with the 2
> parameters "for" and "bar" and the bean "myBean".
> {code:java}
>
>
>
> type="#class:org.apache.camel.spring.routebuilder.MySpecialBean">
>
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17611) Allow to create a Route from a route template in XML and YAML
[
https://issues.apache.org/jira/browse/CAMEL-17611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488136#comment-17488136
]
Nicolas Filotto commented on CAMEL-17611:
-
[~davsclaus] If you don't mind I would like to work on this ticket
> Allow to create a Route from a route template in XML and YAML
> -
>
> Key: CAMEL-17611
> URL: https://issues.apache.org/jira/browse/CAMEL-17611
> Project: Camel
> Issue Type: Improvement
> Components: came-core
>Reporter: Nicolas Filotto
>Assignee: Nicolas Filotto
>Priority: Major
>
> With the existing code it is possible to create a route from a route template
> thanks to TemplatedRouteBuilder with a pure Java code or simply with a
> Kamelet. However in some particular cases it could be interesting to be able
> to create routes from a route template from a pure XML or YAML file
> especially for camel users that don't want to use Kamelets and write Java
> code.
>
> So for example, following XML snippet would allow to instantiate a route
> whose id is "my-route" from the route template "myTemplate" with the 2
> parameters "for" and "bar" and the bean "myBean".
> {code:java}
>
>
>
> type="#class:org.apache.camel.spring.routebuilder.MySpecialBean">
>
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17611) Allow to create a Route from a route template in XML and YAML
Nicolas Filotto created CAMEL-17611:
---
Summary: Allow to create a Route from a route template in XML and
YAML
Key: CAMEL-17611
URL: https://issues.apache.org/jira/browse/CAMEL-17611
Project: Camel
Issue Type: Improvement
Components: came-core
Reporter: Nicolas Filotto
Assignee: Nicolas Filotto
With the existing code it is possible to create a route from a route template
thanks to TemplatedRouteBuilder with a pure Java code or simply with a Kamelet.
However in some particular cases it could be interesting to be able to create
routes from a route template from a pure XML or YAML file especially for camel
users that don't want to use Kamelets and write Java code.
So for example, following XML snippet would allow to instantiate a route whose
id is "my-route" from the route template "myTemplate" with the 2 parameters
"for" and "bar" and the bean "myBean".
{code:java}
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17514) BreadcrumbId MDC Value not set even MDCLogging is true during ErrorHandling Processor
[
https://issues.apache.org/jira/browse/CAMEL-17514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488131#comment-17488131
]
Gijsbert van den Brink commented on CAMEL-17514:
Hello [~davsclaus], I'm running into this issue as well, but the fix applied to
3.14.1 and 3.15.0 doesn't work for me. All MDC values are missing in the actual
log output, the camel values (like breadcrumbId and routeId), but also values I
add from my own code. I had to revert back to 3.11.5 to get it working again.
> BreadcrumbId MDC Value not set even MDCLogging is true during ErrorHandling
> Processor
> -
>
> Key: CAMEL-17514
> URL: https://issues.apache.org/jira/browse/CAMEL-17514
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 3.13.0, 3.14.0
>Reporter: Michael Rambichler
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.14.1, 3.15.0
>
>
> *Expected Behaviour:*
> If UseMDCLogging=true and UseBreadcrumb=true is set then i expect then
> everywhere the MDC Value camel.breadcrumbId is set.
> like it works in Camel Version < 3.12
> *Reproducable*
> *Camel Version > 3.11*
>
> Hint: If I use a custom UnitOfWorkFactory it works as expected. But I would
> assume that If MDCLogging is enabled then the DefaultUnitOfWork would handle
> this.
>
> *Log without MDC camel.Breadcrumb:*
> 2022-01-19 12:01:00,335 INFO [1 - timer://foo] route1
> [route1 0141fbc5-bb47-4458-a982-1e6585109b8a] - Received exchange
> with breadcrumbID: 0141fbc5-bb47-4458-a982-1e6585109b8a
> 2022-01-19 12:01:00,337 INFO [1 - timer://foo]
> c.t.a.r.h.HelloBreadcrumbRoute [route1
> 0141fbc5-bb47-4458-a982-1e6585109b8a] - Process with bug
> 2022-01-19 12:01:00,338 INFO [1 - timer://foo]
> c.t.a.r.h.OnExceptionProcessor
> [{color:#FF}breadcrumbMissing{color}] - Some OnException process
> 2022-01-19 12:01:00,344 INFO [1 - timer://foo] route2
> [route2 {color:#FF}breadcrumbMissing{color}] -
> Deadletter receive
>
> *Example:*
> @Override
> public void configure() throws Exception {
> getContext().setUseMDCLogging(true);
> getContext().setUseBreadcrumb(true);
> DeadLetterChannelBuilder errorHandlerBuilder = new
> DeadLetterChannelBuilder();
> errorHandlerBuilder.setDeadLetterUri("direct:deadletterTest");
> errorHandlerBuilder.setOnExceptionOccurred(onExceptionProcessor);
> errorHandler(errorHandlerBuilder);
> from("timer://foo?fixedRate=true&period=1")
> .log("Received exchange with breadcrumbID: ${in.headers.breadcrumbId}")
> .process(exchange -> {
> throw new Exception("Some Bug");
> });
> from("direct:deadletterTest")
> .log("Deadletter received ${body}");
> }
>
> *OnExceptionProcessor:*
> @Component
> public class OnExceptionProcessor implements Processor {
> private static final Logger LOG =
> LoggerFactory.getLogger(OnExceptionProcessor.class);
> @Override
> public void process(Exchange exchange) throws Exception {
> LOG.info("Some OnException process");
> }
> }
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17610) camel-aws2-ses: Support CC and BCC as endpoint parameters
[ https://issues.apache.org/jira/browse/CAMEL-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488110#comment-17488110 ] Andrea Cosentino commented on CAMEL-17610: -- https://github.com/apache/camel/pull/6897 > camel-aws2-ses: Support CC and BCC as endpoint parameters > - > > Key: CAMEL-17610 > URL: https://issues.apache.org/jira/browse/CAMEL-17610 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Billy Jaime Beltran >Priority: Minor > Labels: pull-request-available > Fix For: 3.16.0 > > > Currently CC and BCC are missing from the uri params but are supported by the > Amazon SDK. Patch so we can send cc and bcc just like we do with To without > having to manually create a javax mail instance. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17610) camel-aws2-ses
[ https://issues.apache.org/jira/browse/CAMEL-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17610: - Fix Version/s: 3.16.0 (was: Future) > camel-aws2-ses > -- > > Key: CAMEL-17610 > URL: https://issues.apache.org/jira/browse/CAMEL-17610 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Billy Jaime Beltran >Priority: Minor > Labels: pull-request-available > Fix For: 3.16.0 > > > Currently CC and BCC are missing from the uri params but are supported by the > Amazon SDK. Patch so we can send cc and bcc just like we do with To without > having to manually create a javax mail instance. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17610) camel-aws2-ses: Support CC and BCC as endpoint parameters
[ https://issues.apache.org/jira/browse/CAMEL-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17610: - External issue URL: (was: https://github.com/apache/camel/pull/6897) > camel-aws2-ses: Support CC and BCC as endpoint parameters > - > > Key: CAMEL-17610 > URL: https://issues.apache.org/jira/browse/CAMEL-17610 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Billy Jaime Beltran >Priority: Minor > Labels: pull-request-available > Fix For: 3.16.0 > > > Currently CC and BCC are missing from the uri params but are supported by the > Amazon SDK. Patch so we can send cc and bcc just like we do with To without > having to manually create a javax mail instance. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17610) camel-aws2-ses: Support CC and BCC as endpoint parameters
[ https://issues.apache.org/jira/browse/CAMEL-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17610: - External issue ID: (was: 6987) > camel-aws2-ses: Support CC and BCC as endpoint parameters > - > > Key: CAMEL-17610 > URL: https://issues.apache.org/jira/browse/CAMEL-17610 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Billy Jaime Beltran >Priority: Minor > Labels: pull-request-available > Fix For: 3.16.0 > > > Currently CC and BCC are missing from the uri params but are supported by the > Amazon SDK. Patch so we can send cc and bcc just like we do with To without > having to manually create a javax mail instance. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17610) camel-aws2-ses: Support CC and BCC as endpoint parameters
[ https://issues.apache.org/jira/browse/CAMEL-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17610: - Summary: camel-aws2-ses: Support CC and BCC as endpoint parameters (was: camel-aws2-ses) > camel-aws2-ses: Support CC and BCC as endpoint parameters > - > > Key: CAMEL-17610 > URL: https://issues.apache.org/jira/browse/CAMEL-17610 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Billy Jaime Beltran >Priority: Minor > Labels: pull-request-available > Fix For: 3.16.0 > > > Currently CC and BCC are missing from the uri params but are supported by the > Amazon SDK. Patch so we can send cc and bcc just like we do with To without > having to manually create a javax mail instance. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17610) camel-aws2-ses
[ https://issues.apache.org/jira/browse/CAMEL-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Jaime Beltran updated CAMEL-17610: Description: Currently CC and BCC are missing from the uri params but are supported by the Amazon SDK. Patch so we can send cc and bcc just like we do with To without having to manually create a javax mail instance. (was: Currently CC and BCC are missing. Patch so we can send cc and bcc just like we do with To without having to manually create a javax mail instance.) > camel-aws2-ses > -- > > Key: CAMEL-17610 > URL: https://issues.apache.org/jira/browse/CAMEL-17610 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Billy Jaime Beltran >Priority: Minor > Labels: pull-request-available > Fix For: Future > > > Currently CC and BCC are missing from the uri params but are supported by the > Amazon SDK. Patch so we can send cc and bcc just like we do with To without > having to manually create a javax mail instance. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17610) camel-aws2-ses
[ https://issues.apache.org/jira/browse/CAMEL-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Jaime Beltran updated CAMEL-17610: External issue ID: 6987 External issue URL: https://github.com/apache/camel/pull/6897 > camel-aws2-ses > -- > > Key: CAMEL-17610 > URL: https://issues.apache.org/jira/browse/CAMEL-17610 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Billy Jaime Beltran >Priority: Minor > Labels: pull-request-available > Fix For: Future > > > Currently CC and BCC are missing. Patch so we can send cc and bcc just like > we do with To without having to manually create a javax mail instance. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17610) camel-aws2-ses
Billy Jaime Beltran created CAMEL-17610: --- Summary: camel-aws2-ses Key: CAMEL-17610 URL: https://issues.apache.org/jira/browse/CAMEL-17610 Project: Camel Issue Type: Improvement Components: camel-aws2 Reporter: Billy Jaime Beltran Fix For: Future Currently CC and BCC are missing. Patch so we can send cc and bcc just like we do with To without having to manually create a javax mail instance. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17608) camel-salesforce: allow overriding sobject name when using DTOs
[
https://issues.apache.org/jira/browse/CAMEL-17608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488078#comment-17488078
]
Zoran Regvart commented on CAMEL-17608:
---
Yeah, if folk provide the {{sObjectName}} that should be taken as is and
override the name derived from the body. It does change the behavior from what
we do for a long time, but I don't think it breaks the backward compatibility
for most folks as they would either use {{sObjectName}} or they would rely on
the class name; if both are specified and they differ this will, most likely,
break for folk, so it might be a good idea to either throw an exception or log
a warning. I suspect the logic as it stands today is in a number places so
changing this we'd need to be a bit careful to stay consistent.
> camel-salesforce: allow overriding sobject name when using DTOs
> ---
>
> Key: CAMEL-17608
> URL: https://issues.apache.org/jira/browse/CAMEL-17608
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
>Affects Versions: 3.15.0
>Reporter: Jeremy Ross
>Priority: Major
>
> When subclasses of the generated DTOs are used, Camel uses the name of the
> subclass as the sobject name, which won't work. Also, because instanceof
> check passes, camel ignores the sObjectName option. The solution would be for
> Camel to always honor the sObjectName option.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17587) camel-core - Make Health Check API simpler
[ https://issues.apache.org/jira/browse/CAMEL-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488013#comment-17488013 ] Claus Ibsen commented on CAMEL-17587: - Or instead of configuration then we can just have a single option where you can disable by pattern (multi separated by comma) camel.health.check.disabled-pattern = netty > camel-core - Make Health Check API simpler > -- > > Key: CAMEL-17587 > URL: https://issues.apache.org/jira/browse/CAMEL-17587 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > > The thresholds for failure / success / interval etc should be removed, to > make invoking health checks in camel always executing. > Such thresholds does not belong inside camel but the monitoring systems where > they can setup such rules. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17587) camel-core - Make Health Check API simpler
[ https://issues.apache.org/jira/browse/CAMEL-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488010#comment-17488010 ] Claus Ibsen commented on CAMEL-17587: - We can make configuration simpler to avoid the parent and just have a way to enable/disable individual checks camel.health.config[timer].parent = routes camel.health.config[timer].enabled = true Can be camel.health.routes[timer].enabled = true > camel-core - Make Health Check API simpler > -- > > Key: CAMEL-17587 > URL: https://issues.apache.org/jira/browse/CAMEL-17587 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > > The thresholds for failure / success / interval etc should be removed, to > make invoking health checks in camel always executing. > Such thresholds does not belong inside camel but the monitoring systems where > they can setup such rules. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17587) camel-core - Make Health Check API simpler
[ https://issues.apache.org/jira/browse/CAMEL-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487998#comment-17487998 ] Claus Ibsen edited comment on CAMEL-17587 at 2/7/22, 10:21 AM: --- TODO: camel-core *DONE* TODO: camel-spring-boot *DONE* TODO: camel-examples *DONE* TODO: camel-spring-boot-examples *DONE* TODO: Deprecate in camel 3.14.x *DONE* was (Author: davsclaus): TODO: camel-spring-boot *DONE* TODO: camel-examples *DONE* TODO: camel-spring-boot-examples *DONE* > camel-core - Make Health Check API simpler > -- > > Key: CAMEL-17587 > URL: https://issues.apache.org/jira/browse/CAMEL-17587 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > > The thresholds for failure / success / interval etc should be removed, to > make invoking health checks in camel always executing. > Such thresholds does not belong inside camel but the monitoring systems where > they can setup such rules. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17587) camel-core - Make Health Check API simpler
[ https://issues.apache.org/jira/browse/CAMEL-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487998#comment-17487998 ] Claus Ibsen edited comment on CAMEL-17587 at 2/7/22, 10:12 AM: --- TODO: camel-spring-boot *DONE* TODO: camel-examples *DONE* TODO: camel-spring-boot-examples *DONE* was (Author: davsclaus): TODO: camel-spring-boot TODO: camel-examples TODO: camel-spring-boot-examples > camel-core - Make Health Check API simpler > -- > > Key: CAMEL-17587 > URL: https://issues.apache.org/jira/browse/CAMEL-17587 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > > The thresholds for failure / success / interval etc should be removed, to > make invoking health checks in camel always executing. > Such thresholds does not belong inside camel but the monitoring systems where > they can setup such rules. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17587) camel-core - Make Health Check API simpler
[ https://issues.apache.org/jira/browse/CAMEL-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487998#comment-17487998 ] Claus Ibsen commented on CAMEL-17587: - TODO: camel-spring-boot TODO: camel-examples TODO: camel-spring-boot-examples > camel-core - Make Health Check API simpler > -- > > Key: CAMEL-17587 > URL: https://issues.apache.org/jira/browse/CAMEL-17587 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > > The thresholds for failure / success / interval etc should be removed, to > make invoking health checks in camel always executing. > Such thresholds does not belong inside camel but the monitoring systems where > they can setup such rules. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17587) camel-core - Make Health Check API simpler
[ https://issues.apache.org/jira/browse/CAMEL-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-17587: --- Assignee: Claus Ibsen > camel-core - Make Health Check API simpler > -- > > Key: CAMEL-17587 > URL: https://issues.apache.org/jira/browse/CAMEL-17587 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > > The thresholds for failure / success / interval etc should be removed, to > make invoking health checks in camel always executing. > Such thresholds does not belong inside camel but the monitoring systems where > they can setup such rules. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-11834) provide automated tests for Camel examples
[ https://issues.apache.org/jira/browse/CAMEL-11834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487973#comment-17487973 ] Nicolas Filotto edited comment on CAMEL-11834 at 2/7/22, 9:07 AM: -- I definitively agree with you. I'm wondering if the real purpose of the examples has already been defined? If so what is it exactly? Showing in practice: # only the main features of Camel # the main features of Camel but also the most important/used components and if so how to clearly know which ones should have an example and which ones should not was (Author: essobedo): I definitively agree with you. I'm wondering if the real purpose of the examples has already been defined? If so what is it exactly? Showing in practice: # only the main features of Camel # the main features of Camel but also the most important/used components and if so how to clearly know which ones should have an example and which should not > provide automated tests for Camel examples > -- > > Key: CAMEL-11834 > URL: https://issues.apache.org/jira/browse/CAMEL-11834 > Project: Camel > Issue Type: Task > Components: examples >Affects Versions: 2.19.3 >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 3.x > > Time Spent: 20m > Remaining Estimate: 0h > > currently someone need to check manually that everything is fine. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-11834) provide automated tests for Camel examples
[ https://issues.apache.org/jira/browse/CAMEL-11834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487973#comment-17487973 ] Nicolas Filotto commented on CAMEL-11834: - I definitively agree with you. I'm wondering if the real purpose of the examples has already been defined? If so what is it exactly? Showing in practice: # only the main features of Camel # the main features of Camel but also the most important/used components and if so how to clearly know which ones should have an example and which should not > provide automated tests for Camel examples > -- > > Key: CAMEL-11834 > URL: https://issues.apache.org/jira/browse/CAMEL-11834 > Project: Camel > Issue Type: Task > Components: examples >Affects Versions: 2.19.3 >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 3.x > > Time Spent: 20m > Remaining Estimate: 0h > > currently someone need to check manually that everything is fine. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17606) camel-core - Endpoint DSL - fluent builder to refer to property placeholder
[
https://issues.apache.org/jira/browse/CAMEL-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-17606.
-
Resolution: Fixed
> camel-core - Endpoint DSL - fluent builder to refer to property placeholder
> ---
>
> Key: CAMEL-17606
> URL: https://issues.apache.org/jira/browse/CAMEL-17606
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.16.0
>
>
> I wonder if we need a builder method to refer to property placeholder?
> .username("{{mail.sender}}")
> vs
> .username(property("mail.sender"))
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17606) camel-core - Endpoint DSL - fluent builder to refer to property placeholder
[
https://issues.apache.org/jira/browse/CAMEL-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17606:
Priority: Minor (was: Major)
> camel-core - Endpoint DSL - fluent builder to refer to property placeholder
> ---
>
> Key: CAMEL-17606
> URL: https://issues.apache.org/jira/browse/CAMEL-17606
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.16.0
>
>
> I wonder if we need a builder method to refer to property placeholder?
> .username("{{mail.sender}}")
> vs
> .username(property("mail.sender"))
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17606) camel-core - Endpoint DSL - fluent builder to refer to property placeholder
[
https://issues.apache.org/jira/browse/CAMEL-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17606:
Fix Version/s: 3.16.0
(was: 3.x)
> camel-core - Endpoint DSL - fluent builder to refer to property placeholder
> ---
>
> Key: CAMEL-17606
> URL: https://issues.apache.org/jira/browse/CAMEL-17606
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> I wonder if we need a builder method to refer to property placeholder?
> .username("{{mail.sender}}")
> vs
> .username(property("mail.sender"))
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (CAMEL-17606) camel-core - Endpoint DSL - fluent builder to refer to property placeholder
[
https://issues.apache.org/jira/browse/CAMEL-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-17606:
---
Assignee: Claus Ibsen
> camel-core - Endpoint DSL - fluent builder to refer to property placeholder
> ---
>
> Key: CAMEL-17606
> URL: https://issues.apache.org/jira/browse/CAMEL-17606
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.x
>
>
> I wonder if we need a builder method to refer to property placeholder?
> .username("{{mail.sender}}")
> vs
> .username(property("mail.sender"))
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
