[jira] [Updated] (CAMEL-13864) JMS Component does not support non-durable shared subscription
[ https://issues.apache.org/jira/browse/CAMEL-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13864: Fix Version/s: 3.0.0.RC1 3.0.0 > JMS Component does not support non-durable shared subscription > -- > > Key: CAMEL-13864 > URL: https://issues.apache.org/jira/browse/CAMEL-13864 > Project: Camel > Issue Type: Improvement > Components: camel-jms >Affects Versions: 2.24.1, 3.0.0.M4 >Reporter: Benjamin Graf >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > Time Spent: 10m > Remaining Estimate: 0h > > Issue described under > https://lists.apache.org/thread.html/888044ae9bb3bbad529beb1a1715c65187c7b3c47bc0434642bb0011@%3Cusers.camel.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13864) JMS Component does not support non-durable shared subscription
[ https://issues.apache.org/jira/browse/CAMEL-13864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13864: Issue Type: Improvement (was: Bug) > JMS Component does not support non-durable shared subscription > -- > > Key: CAMEL-13864 > URL: https://issues.apache.org/jira/browse/CAMEL-13864 > Project: Camel > Issue Type: Improvement > Components: camel-jms >Affects Versions: 2.24.1, 3.0.0.M4 >Reporter: Benjamin Graf >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Issue described under > https://lists.apache.org/thread.html/888044ae9bb3bbad529beb1a1715c65187c7b3c47bc0434642bb0011@%3Cusers.camel.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Work logged] (CAMEL-13864) JMS Component does not support non-durable shared subscription
[ https://issues.apache.org/jira/browse/CAMEL-13864?focusedWorklogId=294115=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-294115 ] ASF GitHub Bot logged work on CAMEL-13864: -- Author: ASF GitHub Bot Created on: 13/Aug/19 19:25 Start Date: 13/Aug/19 19:25 Worklog Time Spent: 10m Work Description: graben commented on pull request #3103: CAMEL-13864: Allow subscriptionName to be set for non-durable shared subscription URL: https://github.com/apache/camel/pull/3103 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: 294115) Time Spent: 10m Remaining Estimate: 0h > JMS Component does not support non-durable shared subscription > -- > > Key: CAMEL-13864 > URL: https://issues.apache.org/jira/browse/CAMEL-13864 > Project: Camel > Issue Type: Bug > Components: camel-jms >Affects Versions: 2.24.1, 3.0.0.M4 >Reporter: Benjamin Graf >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Issue described under > https://lists.apache.org/thread.html/888044ae9bb3bbad529beb1a1715c65187c7b3c47bc0434642bb0011@%3Cusers.camel.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (CAMEL-13864) JMS Component does not support non-durable shared subscription
Benjamin Graf created CAMEL-13864: - Summary: JMS Component does not support non-durable shared subscription Key: CAMEL-13864 URL: https://issues.apache.org/jira/browse/CAMEL-13864 Project: Camel Issue Type: Bug Components: camel-jms Affects Versions: 3.0.0.M4, 2.24.1 Reporter: Benjamin Graf Issue described under https://lists.apache.org/thread.html/888044ae9bb3bbad529beb1a1715c65187c7b3c47bc0434642bb0011@%3Cusers.camel.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-13850) camel3 - Property placeholders on EIP models can be optimized
[ https://issues.apache.org/jira/browse/CAMEL-13850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906369#comment-16906369 ] Claus Ibsen commented on CAMEL-13850: - Okay I have now the prototype to not use reflection at all for the EIP model, components, and the fields on Exchange. Now we generate java source code for fast property placeholders and field lookup on exchange. > camel3 - Property placeholders on EIP models can be optimized > - > > Key: CAMEL-13850 > URL: https://issues.apache.org/jira/browse/CAMEL-13850 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > > We do a bit of introspection on each model class to fin its getter/setter > properties, which we can then use for property placeholders. > org.apache.camel.model.ProcessorDefinitionHelper#resolvePropertyPlaceholders > We should look at optimising this -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-12957) camel-cxf - Swagger/OpenAPI feature should not involve the Camel route
[ https://issues.apache.org/jira/browse/CAMEL-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-12957. -- Resolution: Fixed Fix Version/s: 2.25.0 > camel-cxf - Swagger/OpenAPI feature should not involve the Camel route > -- > > Key: CAMEL-12957 > URL: https://issues.apache.org/jira/browse/CAMEL-12957 > Project: Camel > Issue Type: Improvement > Components: camel-cxfrs >Affects Versions: 2.22.2 >Reporter: Jens Kleine-Herzbruch >Assignee: Freeman Fang >Priority: Minor > Fix For: 3.0.0, 2.25.0 > > Attachments: camel-openapi-test-swagger2feature.tar, > camel-openapi-test.zip > > > Currently, when adding Swagger2Feature or OpenApiFeature to a CXFRS endpoint, > the calls to the API descriptions go through the Camel route, ie. one has to > implement an additional Camel route in order to make those features work. > Using runAsFilter=false a call to > http://localhost:8080/services/myCamelService/openapi.json > results in a call of the Camel route with an operation "getOpenApi" > http://localhost:8080/services/myCamelServive/api-docs?url=openapi.json > results in call of the Camel route with an operation "getResource" > Using runAsFilter=true the situation improves marginally: > http://localhost:8080/services/myCamelService/openapi.json > still results in a call of the Camel route with an operation "getOpenApi" > http://localhost:8080/services/myCamelServive/api-docs?url=openapi.json > at least now shows the Swagger UI page frame but still fails to load the > actual service description since it again calls the Camel route with the > "getOpenApi" operation. > Supposedly that means the filter correctly intercepts the getResource call > but not the getOpenApi call. It would be great if this worked out of the box. > A custom implementation would still be possible by not running as a filter. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-12957) camel-cxf - Swagger/OpenAPI feature should not involve the Camel route
[ https://issues.apache.org/jira/browse/CAMEL-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906274#comment-16906274 ] Freeman Fang commented on CAMEL-12957: -- CXF 3.3.3 is out, I will update to use it and close this issue > camel-cxf - Swagger/OpenAPI feature should not involve the Camel route > -- > > Key: CAMEL-12957 > URL: https://issues.apache.org/jira/browse/CAMEL-12957 > Project: Camel > Issue Type: Improvement > Components: camel-cxfrs >Affects Versions: 2.22.2 >Reporter: Jens Kleine-Herzbruch >Assignee: Freeman Fang >Priority: Minor > Fix For: 3.0.0 > > Attachments: camel-openapi-test-swagger2feature.tar, > camel-openapi-test.zip > > > Currently, when adding Swagger2Feature or OpenApiFeature to a CXFRS endpoint, > the calls to the API descriptions go through the Camel route, ie. one has to > implement an additional Camel route in order to make those features work. > Using runAsFilter=false a call to > http://localhost:8080/services/myCamelService/openapi.json > results in a call of the Camel route with an operation "getOpenApi" > http://localhost:8080/services/myCamelServive/api-docs?url=openapi.json > results in call of the Camel route with an operation "getResource" > Using runAsFilter=true the situation improves marginally: > http://localhost:8080/services/myCamelService/openapi.json > still results in a call of the Camel route with an operation "getOpenApi" > http://localhost:8080/services/myCamelServive/api-docs?url=openapi.json > at least now shows the Swagger UI page frame but still fails to load the > actual service description since it again calls the Camel route with the > "getOpenApi" operation. > Supposedly that means the filter correctly intercepts the getResource call > but not the getOpenApi call. It would be great if this worked out of the box. > A custom implementation would still be possible by not running as a filter. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (CAMEL-13863) camel3 - Optimize XmlConverterLoader
Claus Ibsen created CAMEL-13863: --- Summary: camel3 - Optimize XmlConverterLoader Key: CAMEL-13863 URL: https://issues.apache.org/jira/browse/CAMEL-13863 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Fix For: 3.0.0.RC2 I wonder if we can optimize XmlConverterLoader this to init the getXmlConverter once only and avoid synchronized. It does take a bit time to load according to the yourkit profiler -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-13862) Camel-Kafka-Starter module for springboot properties usage is not described anywhere
[ https://issues.apache.org/jira/browse/CAMEL-13862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906067#comment-16906067 ] ArunTaneja commented on CAMEL-13862: Can you please provide example for the usage of properties defined in camel-kafka-starter? > Camel-Kafka-Starter module for springboot properties usage is not described > anywhere > > > Key: CAMEL-13862 > URL: https://issues.apache.org/jira/browse/CAMEL-13862 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 2.23.1 >Reporter: ArunTaneja >Priority: Major > > As per the document > [https://github.com/apache/camel/blob/master/components/camel-kafka/src/main/docs/kafka-component.adoc] > > We can include this camel-kafka-starter for springboot project > h2. Spring Boot Auto-Configuration > When using Spring Boot make sure to use the following Maven dependency to > have support for auto configuration: > org.apache.camel > camel-kafka-starter x.x.x > > > But there is no example or way to use these auto configutation properties in > our code.We still need to use from(kafka:topicNAme?broker=&) and add further > properties with query parameters in from method. > > We though auto configuration should eliminate this URI building in "from" > method while creating route. > > Please provide example to describe the usage of this library > > Thanks, > Arun -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-13850) camel3 - Property placeholders on EIP models can be optimized
[ https://issues.apache.org/jira/browse/CAMEL-13850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906065#comment-16906065 ] Claus Ibsen commented on CAMEL-13850: - Okay so the component placeholder can likely be removed as configuring this is already supported via camel main / camel spring boot etc, and in xml you would spring or blueprint style. Otherwise we would need to also do some apt compiler magic and generate source code for this, and it seems a bit overkill. > camel3 - Property placeholders on EIP models can be optimized > - > > Key: CAMEL-13850 > URL: https://issues.apache.org/jira/browse/CAMEL-13850 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > > We do a bit of introspection on each model class to fin its getter/setter > properties, which we can then use for property placeholders. > org.apache.camel.model.ProcessorDefinitionHelper#resolvePropertyPlaceholders > We should look at optimising this -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-11494) Incorporate search engine microdata
[ https://issues.apache.org/jira/browse/CAMEL-11494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-11494. --- Resolution: Fixed We now have logo, Twitter and breadcrumbs thanks to [~nayanagamuhandiram] > Incorporate search engine microdata > --- > > Key: CAMEL-11494 > URL: https://issues.apache.org/jira/browse/CAMEL-11494 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > We should incorporate microdata into pages to make them surface better in the > search engines: > - https://developers.google.com/gmail/markup/reference/formats/microdata > - https://search.google.com/structured-data/testing-tool/u/0/ -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-13814) Inline EIP images
[ https://issues.apache.org/jira/browse/CAMEL-13814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-13814. --- Resolution: Done > Inline EIP images > - > > Key: CAMEL-13814 > URL: https://issues.apache.org/jira/browse/CAMEL-13814 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > > We're sourcing images from http://www.eaipatterns.com/ that is brittle and > I'm not sure if we have the rights to those images, I think there was a > contribution of new EIP images that we can use to replace those and serve > them locally. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-13862) Camel-Kafka-Starter module for springboot properties usage is not described anywhere
[ https://issues.apache.org/jira/browse/CAMEL-13862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906025#comment-16906025 ] Claus Ibsen commented on CAMEL-13862: - Also mind about the version of Camel you use. Camel Kafka was recently updated to allow to configure brokers on component level, so the uri only has the topic name etc. > Camel-Kafka-Starter module for springboot properties usage is not described > anywhere > > > Key: CAMEL-13862 > URL: https://issues.apache.org/jira/browse/CAMEL-13862 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 2.23.1 >Reporter: ArunTaneja >Priority: Major > > As per the document > [https://github.com/apache/camel/blob/master/components/camel-kafka/src/main/docs/kafka-component.adoc] > > We can include this camel-kafka-starter for springboot project > h2. Spring Boot Auto-Configuration > When using Spring Boot make sure to use the following Maven dependency to > have support for auto configuration: > org.apache.camel > camel-kafka-starter x.x.x > > > But there is no example or way to use these auto configutation properties in > our code.We still need to use from(kafka:topicNAme?broker=&) and add further > properties with query parameters in from method. > > We though auto configuration should eliminate this URI building in "from" > method while creating route. > > Please provide example to describe the usage of this library > > Thanks, > Arun -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-13862) Camel-Kafka-Starter module for springboot properties usage is not described anywhere
[ https://issues.apache.org/jira/browse/CAMEL-13862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13862. - Resolution: Invalid Spring Boot auto configuration is only for global options on the kafka component level. You cannot configure everything there, some options are endpoint only etc. > Camel-Kafka-Starter module for springboot properties usage is not described > anywhere > > > Key: CAMEL-13862 > URL: https://issues.apache.org/jira/browse/CAMEL-13862 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 2.23.1 >Reporter: ArunTaneja >Priority: Major > > As per the document > [https://github.com/apache/camel/blob/master/components/camel-kafka/src/main/docs/kafka-component.adoc] > > We can include this camel-kafka-starter for springboot project > h2. Spring Boot Auto-Configuration > When using Spring Boot make sure to use the following Maven dependency to > have support for auto configuration: > org.apache.camel > camel-kafka-starter x.x.x > > > But there is no example or way to use these auto configutation properties in > our code.We still need to use from(kafka:topicNAme?broker=&) and add further > properties with query parameters in from method. > > We though auto configuration should eliminate this URI building in "from" > method while creating route. > > Please provide example to describe the usage of this library > > Thanks, > Arun -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (CAMEL-13862) Camel-Kafka-Starter module for springboot properties usage is not described anywhere
ArunTaneja created CAMEL-13862: -- Summary: Camel-Kafka-Starter module for springboot properties usage is not described anywhere Key: CAMEL-13862 URL: https://issues.apache.org/jira/browse/CAMEL-13862 Project: Camel Issue Type: Task Components: camel-kafka Affects Versions: 2.23.1 Reporter: ArunTaneja As per the document [https://github.com/apache/camel/blob/master/components/camel-kafka/src/main/docs/kafka-component.adoc] We can include this camel-kafka-starter for springboot project h2. Spring Boot Auto-Configuration When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration: org.apache.camel camel-kafka-starter x.x.x But there is no example or way to use these auto configutation properties in our code.We still need to use from(kafka:topicNAme?broker=&) and add further properties with query parameters in from method. We though auto configuration should eliminate this URI building in "from" method while creating route. Please provide example to describe the usage of this library Thanks, Arun -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-13850) camel3 - Property placeholders on EIP models can be optimized
[ https://issues.apache.org/jira/browse/CAMEL-13850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905896#comment-16905896 ] Claus Ibsen commented on CAMEL-13850: - You can see before vs after reduction of reflection class caches in this tweet https://twitter.com/davsclaus/status/1161176136338018304?s=20 The remainder is not the model classes, but Camel components. > camel3 - Property placeholders on EIP models can be optimized > - > > Key: CAMEL-13850 > URL: https://issues.apache.org/jira/browse/CAMEL-13850 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > > We do a bit of introspection on each model class to fin its getter/setter > properties, which we can then use for property placeholders. > org.apache.camel.model.ProcessorDefinitionHelper#resolvePropertyPlaceholders > We should look at optimising this -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CAMEL-13580) camel-zookeeper - Deprecate route master/slave policy
[ https://issues.apache.org/jira/browse/CAMEL-13580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905883#comment-16905883 ] Saravanan Tirugnanum commented on CAMEL-13580: -- If camel-zookeeper is deprecated in 3.0.0-M4, is there a way we can achieve multi master ( multiple active nodes) scenarios ( like we had CuratorMultiMasterLeaderRoutePolicy ) in the new version. Any thoughts? > camel-zookeeper - Deprecate route master/slave policy > - > > Key: CAMEL-13580 > URL: https://issues.apache.org/jira/browse/CAMEL-13580 > Project: Camel > Issue Type: Improvement > Components: camel-zookeeper >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > As the camel-zookeeper-master component is better at handling this. So lets > deprecate this in Camel 2.x, and remove in 3.0 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
