[jira] [Commented] (CAMEL-14466) camel-core - Optimize reduce error handler memory usage
[ https://issues.apache.org/jira/browse/CAMEL-14466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027864#comment-17027864 ] Claus Ibsen commented on CAMEL-14466: - Also look at initializing exchange properties map with smaller default capacity as 16 may be too much on regular use. > camel-core - Optimize reduce error handler memory usage > --- > > Key: CAMEL-14466 > URL: https://issues.apache.org/jira/browse/CAMEL-14466 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > Just experimenting if we can reduce the RedeliveryTask object size, for > example to have a simple task for non redeliverable processing, and then the > current when you need advanced error handling. This may reduce the object > sizes in memory during routing for some use-cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14466) camel-core - Optimize reduce error handler memory usage
[ https://issues.apache.org/jira/browse/CAMEL-14466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027862#comment-17027862 ] Claus Ibsen commented on CAMEL-14466: - 2nd optimasation reduces object allocations by 10% in the sample app. But that would vary how many steps there are in routes. But it helps nevertheless. > camel-core - Optimize reduce error handler memory usage > --- > > Key: CAMEL-14466 > URL: https://issues.apache.org/jira/browse/CAMEL-14466 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > Just experimenting if we can reduce the RedeliveryTask object size, for > example to have a simple task for non redeliverable processing, and then the > current when you need advanced error handling. This may reduce the object > sizes in memory during routing for some use-cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14447) OpenApi V3: ensure all variables are parsed for Server Url
[ https://issues.apache.org/jira/browse/CAMEL-14447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang resolved CAMEL-14447. -- Resolution: Fixed > OpenApi V3: ensure all variables are parsed for Server Url > -- > > Key: CAMEL-14447 > URL: https://issues.apache.org/jira/browse/CAMEL-14447 > Project: Camel > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-12619) camel-swagger-java - Add support for 3.0 spec
[ https://issues.apache.org/jira/browse/CAMEL-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang resolved CAMEL-12619. -- Resolution: Fixed > camel-swagger-java - Add support for 3.0 spec > - > > Key: CAMEL-12619 > URL: https://issues.apache.org/jira/browse/CAMEL-12619 > Project: Camel > Issue Type: New Feature > Components: camel-swagger >Reporter: Claus Ibsen >Assignee: Freeman Yue Fang >Priority: Major > Labels: gsoc2019 > Fix For: 3.1.0 > > > Not sure if we can make swagger v3 generate v2 spec files, so we can be 100% > backwards compatible. But v3 openapi 3.0 spec is a different maven GAV so its > maybe not an easy upgrade. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14453) ensure Camel Rest Swagger example work again
[ https://issues.apache.org/jira/browse/CAMEL-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang resolved CAMEL-14453. -- Fix Version/s: 2.25.1 3.1.0 Resolution: Fixed > ensure Camel Rest Swagger example work again > > > Key: CAMEL-14453 > URL: https://issues.apache.org/jira/browse/CAMEL-14453 > Project: Camel > Issue Type: Bug > Components: examples >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.1.0, 2.25.1 > > > example > camel-example-spring-boot-rest-swagger-simple on Camel 3.x > camel-example-rest-swagger on Camel 2.x > broken due to the changes on petstore.swagger.io server. Like change from > http to https, and available Pet ID changed on the server -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14454) add openapi examples
[ https://issues.apache.org/jira/browse/CAMEL-14454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang resolved CAMEL-14454. -- Resolution: Fixed > add openapi examples > > > Key: CAMEL-14454 > URL: https://issues.apache.org/jira/browse/CAMEL-14454 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > > like the swagger examples counterparts -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14466) camel-core - Optimize reduce error handler memory usage
[ https://issues.apache.org/jira/browse/CAMEL-14466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027703#comment-17027703 ] Claus Ibsen commented on CAMEL-14466: - First optimisation done, look next week on that 2nd idea > camel-core - Optimize reduce error handler memory usage > --- > > Key: CAMEL-14466 > URL: https://issues.apache.org/jira/browse/CAMEL-14466 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > Just experimenting if we can reduce the RedeliveryTask object size, for > example to have a simple task for non redeliverable processing, and then the > current when you need advanced error handling. This may reduce the object > sizes in memory during routing for some use-cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14440) Add Workday report as a service component.
[ https://issues.apache.org/jira/browse/CAMEL-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-14440. -- Resolution: Fixed > Add Workday report as a service component. > -- > > Key: CAMEL-14440 > URL: https://issues.apache.org/jira/browse/CAMEL-14440 > Project: Camel > Issue Type: New Feature >Reporter: Fernando Avalos >Priority: Minor > Fix For: 3.1.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Create a Workday component to consume Workday report as a service in Camel. > The component must be ready to work with a Workday Client API for > Integrations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14440) Add Workday report as a service component.
[ https://issues.apache.org/jira/browse/CAMEL-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-14440: - Fix Version/s: 3.1.0 > Add Workday report as a service component. > -- > > Key: CAMEL-14440 > URL: https://issues.apache.org/jira/browse/CAMEL-14440 > Project: Camel > Issue Type: New Feature >Reporter: Fernando Avalos >Priority: Minor > Fix For: 3.1.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Create a Workday component to consume Workday report as a service in Camel. > The component must be ready to work with a Workday Client API for > Integrations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14440) Add Workday report as a service component.
[ https://issues.apache.org/jira/browse/CAMEL-14440?focusedWorklogId=380026&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-380026 ] ASF GitHub Bot logged work on CAMEL-14440: -- Author: ASF GitHub Bot Created on: 31/Jan/20 14:28 Start Date: 31/Jan/20 14:28 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #3512: CAMEL-14440: Add Workday report as service support URL: https://github.com/apache/camel/pull/3512 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: 380026) Remaining Estimate: 0h Time Spent: 10m > Add Workday report as a service component. > -- > > Key: CAMEL-14440 > URL: https://issues.apache.org/jira/browse/CAMEL-14440 > Project: Camel > Issue Type: New Feature >Reporter: Fernando Avalos >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Create a Workday component to consume Workday report as a service in Camel. > The component must be ready to work with a Workday Client API for > Integrations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14469) Switch to maven plugins and remove apt processors
[ https://issues.apache.org/jira/browse/CAMEL-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned CAMEL-14469: --- Assignee: Guillaume Nodet > Switch to maven plugins and remove apt processors > - > > Key: CAMEL-14469 > URL: https://issues.apache.org/jira/browse/CAMEL-14469 > Project: Camel > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14411) Avoid using reflection when configuring DataFormats
[
https://issues.apache.org/jira/browse/CAMEL-14411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved CAMEL-14411.
-
Resolution: Fixed
> Avoid using reflection when configuring DataFormats
> ---
>
> Key: CAMEL-14411
> URL: https://issues.apache.org/jira/browse/CAMEL-14411
> Project: Camel
> Issue Type: Improvement
>Reporter: Peter Palaga
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.1.0
>
>
> See the following call path when a new DataFormat is configured in Camel
> Quarkus (against Camel 3.0.0). Note that the setLineSeparator() method is
> accessed using reflection there.
> Should this be fixed in Camel or should perhaps Camel Quarkus be adapted to
> use some generated configurer?
> {code}
> at
> org.apache.camel.dataformat.base64.Base64DataFormat.setLineSeparator(Base64DataFormat.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.camel.support.IntrospectionSupport.setProperty(IntrospectionSupport.java:715)
> at
> org.apache.camel.support.IntrospectionSupport.setProperty(IntrospectionSupport.java:795)
> at
> org.apache.camel.impl.engine.DefaultBeanIntrospection.setProperty(DefaultBeanIntrospection.java:170)
> at
> org.apache.camel.reifier.dataformat.DataFormatReifier.setProperty(DataFormatReifier.java:243)
> at
> org.apache.camel.reifier.dataformat.Base64DataFormatReifier.configureDataFormat(Base64DataFormatReifier.java:41)
> at
> org.apache.camel.reifier.dataformat.DataFormatReifier.createDataFormat(DataFormatReifier.java:203)
> at
> org.apache.camel.reifier.dataformat.DataFormatReifier.getDataFormat(DataFormatReifier.java:169)
> at
> org.apache.camel.reifier.MarshalReifier.createProcessor(MarshalReifier.java:35)
> at
> org.apache.camel.reifier.ProcessorReifier.makeProcessorImpl(ProcessorReifier.java:571)
> at
> org.apache.camel.reifier.ProcessorReifier.makeProcessor(ProcessorReifier.java:537)
> at
> org.apache.camel.reifier.ProcessorReifier.addRoutes(ProcessorReifier.java:250)
> at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:384)
> at
> org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:108)
> at org.apache.camel.quarkus.core.FastModel.start(FastModel.java:61)
> at
> org.apache.camel.quarkus.core.BaseModel.startRoute(BaseModel.java:327)
> at
> org.apache.camel.quarkus.core.BaseModel.startRouteDefinitions(BaseModel.java:320)
> at
> org.apache.camel.quarkus.core.BaseModel.startRouteDefinitions(BaseModel.java:299)
> at
> org.apache.camel.quarkus.core.FastCamelContext.startRouteDefinitions(FastCamelContext.java:135)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doStartCamel(AbstractCamelContext.java:2597)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.lambda$doStart$2(AbstractCamelContext.java:2445)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doWithDefinedClassLoader(AbstractCamelContext.java:2462)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doStart(AbstractCamelContext.java:2443)
> at
> org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:117)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2352)
> at org.apache.camel.quarkus.core.CamelMain.doStart(CamelMain.java:50)
> at
> org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:117)
> at
> org.apache.camel.quarkus.core.CamelMainRecorder.start(CamelMainRecorder.java:92)
> at
> io.quarkus.deployment.steps.Main$start38.deploy_0(Main$start38.zig:97)
> at
> io.quarkus.deployment.steps.Main$start38.deploy(Main$start38.zig:36)
> at io.quarkus.runner.ApplicationImpl.doStart(ApplicationImpl.zig:180)
> at io.quarkus.runtime.Application.start(Application.java:87)
> at io.quarkus.runner.RuntimeRunner.run(RuntimeRunner.java:167)
> at
> io.quarkus.test.junit.QuarkusTestExtension.doJavaStart(QuarkusTestExtension.java:249)
> at
> io.quarkus.test.junit.QuarkusTestExtension.createTestInstance(QuarkusTestExtension.java:394)
> at
> org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.invokeTestInstanceFactory(ClassBasedTestDescriptor.java:285)
> at
> org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.instantiateTestClass
[jira] [Created] (CAMEL-14469) Switch to maven plugins and remove apt processors
Guillaume Nodet created CAMEL-14469: --- Summary: Switch to maven plugins and remove apt processors Key: CAMEL-14469 URL: https://issues.apache.org/jira/browse/CAMEL-14469 Project: Camel Issue Type: Task Reporter: Guillaume Nodet Fix For: 3.1.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14468) Add support for classification in camel-weka
[ https://issues.apache.org/jira/browse/CAMEL-14468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027500#comment-17027500 ] Thomas Diesler commented on CAMEL-14468: PR: https://github.com/apache/camel/pull/3536 > Add support for classification in camel-weka > > > Key: CAMEL-14468 > URL: https://issues.apache.org/jira/browse/CAMEL-14468 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 3.x > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14468) Add support for classification in camel-weka
[ https://issues.apache.org/jira/browse/CAMEL-14468?focusedWorklogId=379992&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-379992 ] ASF GitHub Bot logged work on CAMEL-14468: -- Author: ASF GitHub Bot Created on: 31/Jan/20 13:39 Start Date: 31/Jan/20 13:39 Worklog Time Spent: 10m Work Description: tdiesler commented on pull request #3536: [CAMEL-14468] Add support for classification in camel-weka URL: https://github.com/apache/camel/pull/3536 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: 379992) Time Spent: 0.5h (was: 20m) > Add support for classification in camel-weka > > > Key: CAMEL-14468 > URL: https://issues.apache.org/jira/browse/CAMEL-14468 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 3.x > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14466) camel-core - Optimize reduce error handler memory usage
[ https://issues.apache.org/jira/browse/CAMEL-14466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027475#comment-17027475 ] Claus Ibsen commented on CAMEL-14466: - Another idea is to store the redelivery state on the exchange once on uow-start and then reset the state before each redelivery error handler. Then its one object created per uow/exchange instead of per step in the routing > camel-core - Optimize reduce error handler memory usage > --- > > Key: CAMEL-14466 > URL: https://issues.apache.org/jira/browse/CAMEL-14466 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > Just experimenting if we can reduce the RedeliveryTask object size, for > example to have a simple task for non redeliverable processing, and then the > current when you need advanced error handling. This may reduce the object > sizes in memory during routing for some use-cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14468) Add support for classification in camel-weka
[ https://issues.apache.org/jira/browse/CAMEL-14468?focusedWorklogId=379984&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-379984 ] ASF GitHub Bot logged work on CAMEL-14468: -- Author: ASF GitHub Bot Created on: 31/Jan/20 13:15 Start Date: 31/Jan/20 13:15 Worklog Time Spent: 10m Work Description: tdiesler commented on pull request #3536: [CAMEL-14468] Add support for classification in camel-weka URL: https://github.com/apache/camel/pull/3536 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: 379984) Time Spent: 20m (was: 10m) > Add support for classification in camel-weka > > > Key: CAMEL-14468 > URL: https://issues.apache.org/jira/browse/CAMEL-14468 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 3.x > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14468) Add support for classification in camel-weka
[ https://issues.apache.org/jira/browse/CAMEL-14468?focusedWorklogId=379982&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-379982 ] ASF GitHub Bot logged work on CAMEL-14468: -- Author: ASF GitHub Bot Created on: 31/Jan/20 13:12 Start Date: 31/Jan/20 13:12 Worklog Time Spent: 10m Work Description: tdiesler commented on pull request #3536: [CAMEL-14468] Add support for classification in camel-weka URL: https://github.com/apache/camel/pull/3536 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: 379982) Remaining Estimate: 0h Time Spent: 10m > Add support for classification in camel-weka > > > Key: CAMEL-14468 > URL: https://issues.apache.org/jira/browse/CAMEL-14468 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 3.x > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14468) Add support for classification in camel-weka
[ https://issues.apache.org/jira/browse/CAMEL-14468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated CAMEL-14468: --- Summary: Add support for classification in camel-weka (was: Add support for working with Weka models) > Add support for classification in camel-weka > > > Key: CAMEL-14468 > URL: https://issues.apache.org/jira/browse/CAMEL-14468 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14468) Add support for working with Weka models
Thomas Diesler created CAMEL-14468: -- Summary: Add support for working with Weka models Key: CAMEL-14468 URL: https://issues.apache.org/jira/browse/CAMEL-14468 Project: Camel Issue Type: New Feature Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 3.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14466) camel-core - Optimize reduce error handler memory usage
[ https://issues.apache.org/jira/browse/CAMEL-14466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027372#comment-17027372 ] Claus Ibsen commented on CAMEL-14466: - Its a big state object so it takes up in a basic Camel example 76% of the memory and I can get that reduced to 59% of the memory usage. 5 min sampling takes 98 MB (76% space by this) reduced to 55 MB (59% space by this) > camel-core - Optimize reduce error handler memory usage > --- > > Key: CAMEL-14466 > URL: https://issues.apache.org/jira/browse/CAMEL-14466 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > Just experimenting if we can reduce the RedeliveryTask object size, for > example to have a simple task for non redeliverable processing, and then the > current when you need advanced error handling. This may reduce the object > sizes in memory during routing for some use-cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14467) Dynamically bypass the cache for lookups
Jens Kleine-Herzbruch created CAMEL-14467: - Summary: Dynamically bypass the cache for lookups Key: CAMEL-14467 URL: https://issues.apache.org/jira/browse/CAMEL-14467 Project: Camel Issue Type: New Feature Components: camel-jcache Affects Versions: 3.0.1 Reporter: Jens Kleine-Herzbruch Attachments: bypass.diff Currently, the JCachePolicy can only enabled or disable the cache completely at startup. It would be useful to be able to enable or disable caching per request, though. This change adds a new property "bypassExpression". If this expression is set and returns true, the cache is ignored for lookup, the underlying route is executed as normal, and the returned value is inserted in the cache for future lookups. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14466) camel-core - Optimize reduce error handler memory usage
Claus Ibsen created CAMEL-14466: --- Summary: camel-core - Optimize reduce error handler memory usage Key: CAMEL-14466 URL: https://issues.apache.org/jira/browse/CAMEL-14466 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.1.0 Just experimenting if we can reduce the RedeliveryTask object size, for example to have a simple task for non redeliverable processing, and then the current when you need advanced error handling. This may reduce the object sizes in memory during routing for some use-cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-12191) Camel-Kafka: create an example on Kubernetes/Openshift by using Strimzi
[ https://issues.apache.org/jira/browse/CAMEL-12191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027294#comment-17027294 ] Aykut Bulgu commented on CAMEL-12191: - Hi [~acosentino]. Already created the example, but having a very busy end of FY. I will complete the explanation part of it in a week and let you know. > Camel-Kafka: create an example on Kubernetes/Openshift by using Strimzi > --- > > Key: CAMEL-12191 > URL: https://issues.apache.org/jira/browse/CAMEL-12191 > Project: Camel > Issue Type: Task > Components: camel-kafka, examples >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.x > > > https://github.com/strimzi/strimzi -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14452) Unable to configure font or page size on PDF endpoints
[ https://issues.apache.org/jira/browse/CAMEL-14452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton resolved CAMEL-14452. - Assignee: James Netherton Resolution: Fixed > Unable to configure font or page size on PDF endpoints > -- > > Key: CAMEL-14452 > URL: https://issues.apache.org/jira/browse/CAMEL-14452 > Project: Camel > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: James Netherton >Assignee: James Netherton >Priority: Minor > Fix For: 3.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This could be related to CAMEL-14284. > If you try to set the font or pageSize options on a PDF endpoint then you get > an NPE. E.g > pdf:create?fontSize=6&pageSize=PAGE_SIZE_A5&font=courier > Probably due to PdfEndpointConfigurer expecting the type to be either PDFont > or PDRectangle when its actually trying to deal with a String. -- This message was sent by Atlassian Jira (v8.3.4#803005)
