[jira] [Resolved] (CAMEL-13655) Allow to plug a custom ProcessorReifier
[ https://issues.apache.org/jira/browse/CAMEL-13655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli resolved CAMEL-13655. - Resolution: Fixed > Allow to plug a custom ProcessorReifier > --- > > Key: CAMEL-13655 > URL: https://issues.apache.org/jira/browse/CAMEL-13655 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 3.0.0.M4 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13659) TokenizerDefinition to support string based contructor
[ https://issues.apache.org/jira/browse/CAMEL-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli resolved CAMEL-13659. - Resolution: Fixed > TokenizerDefinition to support string based contructor > -- > > Key: CAMEL-13659 > URL: https://issues.apache.org/jira/browse/CAMEL-13659 > Project: Camel > Issue Type: Improvement >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 3.0.0.M4 > > Time Spent: 10m > Remaining Estimate: 0h > > Most of the various language Expression have a constructor with a string > where basically one can set the expression to use but the tokenizer does not > have a similar constructor. > We can provide one that by default sets the token field. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13655) Allow to plug a custom ProcessorReifier
[ https://issues.apache.org/jira/browse/CAMEL-13655?focusedWorklogId=262054=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-262054 ] ASF GitHub Bot logged work on CAMEL-13655: -- Author: ASF GitHub Bot Created on: 18/Jun/19 05:50 Start Date: 18/Jun/19 05:50 Worklog Time Spent: 10m Work Description: lburgazzoli commented on pull request #2982: CAMEL-13655: Allow to plug a custom ProcessorReifier URL: https://github.com/apache/camel/pull/2982 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: 262054) Time Spent: 10m Remaining Estimate: 0h > Allow to plug a custom ProcessorReifier > --- > > Key: CAMEL-13655 > URL: https://issues.apache.org/jira/browse/CAMEL-13655 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 3.0.0.M4 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13659) TokenizerDefinition to support string based contructor
[ https://issues.apache.org/jira/browse/CAMEL-13659?focusedWorklogId=262055=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-262055 ] ASF GitHub Bot logged work on CAMEL-13659: -- Author: ASF GitHub Bot Created on: 18/Jun/19 05:50 Start Date: 18/Jun/19 05:50 Worklog Time Spent: 10m Work Description: lburgazzoli commented on pull request #2983: CAMEL-13659: TokenizerDefinition to support string based contructor URL: https://github.com/apache/camel/pull/2983 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: 262055) Time Spent: 10m Remaining Estimate: 0h > TokenizerDefinition to support string based contructor > -- > > Key: CAMEL-13659 > URL: https://issues.apache.org/jira/browse/CAMEL-13659 > Project: Camel > Issue Type: Improvement >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 3.0.0.M4 > > Time Spent: 10m > Remaining Estimate: 0h > > Most of the various language Expression have a constructor with a string > where basically one can set the expression to use but the tokenizer does not > have a similar constructor. > We can provide one that by default sets the token field. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (CAMEL-13659) TokenizerDefinition to support string based contructor
[ https://issues.apache.org/jira/browse/CAMEL-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-13659 started by Luca Burgazzoli. --- > TokenizerDefinition to support string based contructor > -- > > Key: CAMEL-13659 > URL: https://issues.apache.org/jira/browse/CAMEL-13659 > Project: Camel > Issue Type: Improvement >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 3.0.0.M4 > > > Most of the various language Expression have a constructor with a string > where basically one can set the expression to use but the tokenizer does not > have a similar constructor. > We can provide one that by default sets the token field. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13659) TokenizerDefinition to support string based contructor
Luca Burgazzoli created CAMEL-13659: --- Summary: TokenizerDefinition to support string based contructor Key: CAMEL-13659 URL: https://issues.apache.org/jira/browse/CAMEL-13659 Project: Camel Issue Type: Improvement Reporter: Luca Burgazzoli Assignee: Luca Burgazzoli Fix For: 3.0.0.M4 Most of the various language Expression have a constructor with a string where basically one can set the expression to use but the tokenizer does not have a similar constructor. We can provide one that by default sets the token field. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13658) Refine ProcessorDefinition output handling
Luca Burgazzoli created CAMEL-13658:
---
Summary: Refine ProcessorDefinition output handling
Key: CAMEL-13658
URL: https://issues.apache.org/jira/browse/CAMEL-13658
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Luca Burgazzoli
Fix For: 3.0.0.M4
The ProcessDefinition class is the base class for most of the DSL / Definitions
and defines a number of methods related to outputs such as:
{code:java}
public abstract List> getOutputs();
public abstract boolean isOutputSupported();
{code}
The information about the ability to handle outputs is thus available at
runtime only which complicates the creation of alternative DSLs (i.e
https://github.com/apache/camel-k-runtime/issues/80)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12975) WARN: No CamelContext defined yet so cannot inject into bean: org.apache.camel.converter.jaxb.FallbackTypeConverter
[
https://issues.apache.org/jira/browse/CAMEL-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CAMEL-12975.
--
Resolution: Fixed
Fix Version/s: 2.25.0
2.24.1
2.23.3
> WARN: No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter
> ---
>
> Key: CAMEL-12975
> URL: https://issues.apache.org/jira/browse/CAMEL-12975
> Project: Camel
> Issue Type: Bug
> Components: camel-jaxb, camel-spring-boot-starters
>Affects Versions: 2.23.0, 2.24.0
>Reporter: Pascal Schumacher
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 2.23.3, 2.24.1, 2.25.0
>
>
> I'm using camel-jaxb-starter 2.23.0 in combination with Spring Boot 2.1.1.
> During start-up this warning is displayed:
> {{WARN 15204 --- [ main] o.a.c.i.DefaultCamelBeanPostProcessor:
> No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter}}
> Otherwise everything is working fine (as far as I can tell).
> I created a minimal project that allows reproducing this warning:
> https://github.com/PascalSchumacher/CamelJaxbStartupWarning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13657) Simpler names in the DSL
[
https://issues.apache.org/jira/browse/CAMEL-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated CAMEL-13657:
Summary: Simpler names in the DSL (was: Sipler names in in DSL)
> Simpler names in the DSL
>
>
> Key: CAMEL-13657
> URL: https://issues.apache.org/jira/browse/CAMEL-13657
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0.M4
>
>
> Some part of the DSL expose verbose properties as example, the set header
> definition, has ha setHeaderName property which leads to an XML like:
> {code:xml}
>
> {code}
> This is not wrong but the context gives enough information so it can be
> rewritten as:
> {code:xml}
>
> {code}
> Which makes it shorter and does not impact comprehension.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13657) Sipler names in in DSL
Luca Burgazzoli created CAMEL-13657:
---
Summary: Sipler names in in DSL
Key: CAMEL-13657
URL: https://issues.apache.org/jira/browse/CAMEL-13657
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Luca Burgazzoli
Fix For: 3.0.0.M4
Some part of the DSL expose verbose properties as example, the set header
definition, has ha setHeaderName property which leads to an XML like:
{code:xml}
{code}
This is not wrong but the context gives enough information so it can be
rewritten as:
{code:xml}
{code}
Which makes it shorter and does not impact comprehension.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12975) WARN: No CamelContext defined yet so cannot inject into bean: org.apache.camel.converter.jaxb.FallbackTypeConverter
[
https://issues.apache.org/jira/browse/CAMEL-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated CAMEL-12975:
-
Fix Version/s: (was: 3.0.0)
> WARN: No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter
> ---
>
> Key: CAMEL-12975
> URL: https://issues.apache.org/jira/browse/CAMEL-12975
> Project: Camel
> Issue Type: Bug
> Components: camel-jaxb, camel-spring-boot-starters
>Affects Versions: 2.23.0, 2.24.0
>Reporter: Pascal Schumacher
>Priority: Minor
>
> I'm using camel-jaxb-starter 2.23.0 in combination with Spring Boot 2.1.1.
> During start-up this warning is displayed:
> {{WARN 15204 --- [ main] o.a.c.i.DefaultCamelBeanPostProcessor:
> No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter}}
> Otherwise everything is working fine (as far as I can tell).
> I created a minimal project that allows reproducing this warning:
> https://github.com/PascalSchumacher/CamelJaxbStartupWarning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-12975) WARN: No CamelContext defined yet so cannot inject into bean: org.apache.camel.converter.jaxb.FallbackTypeConverter
[
https://issues.apache.org/jira/browse/CAMEL-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CAMEL-12975:
Assignee: Freeman Fang
> WARN: No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter
> ---
>
> Key: CAMEL-12975
> URL: https://issues.apache.org/jira/browse/CAMEL-12975
> Project: Camel
> Issue Type: Bug
> Components: camel-jaxb, camel-spring-boot-starters
>Affects Versions: 2.23.0, 2.24.0
>Reporter: Pascal Schumacher
>Assignee: Freeman Fang
>Priority: Minor
>
> I'm using camel-jaxb-starter 2.23.0 in combination with Spring Boot 2.1.1.
> During start-up this warning is displayed:
> {{WARN 15204 --- [ main] o.a.c.i.DefaultCamelBeanPostProcessor:
> No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter}}
> Otherwise everything is working fine (as far as I can tell).
> I created a minimal project that allows reproducing this warning:
> https://github.com/PascalSchumacher/CamelJaxbStartupWarning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12975) WARN: No CamelContext defined yet so cannot inject into bean: org.apache.camel.converter.jaxb.FallbackTypeConverter
[
https://issues.apache.org/jira/browse/CAMEL-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865807#comment-16865807
]
Freeman Fang edited comment on CAMEL-12975 at 6/17/19 5:33 PM:
---
I think we also need to add org.apache.camel.DeferredContextBinding annotation
to org.apache.camel.converter.jaxb.FallbackTypeConverter(for camel 2.x) to get
rid of the WARN message.
Btw, it's not a problem anymore for Camel 3.x since FallbackTypeConverter isn't
CamelContextAware anymore.
was (Author: ffang):
I think we also need to add org.apache.camel.DeferredContextBinding annotation
to org.apache.camel.converter.jaxb.FallbackTypeConverter to get rid of the WARN
message
> WARN: No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter
> ---
>
> Key: CAMEL-12975
> URL: https://issues.apache.org/jira/browse/CAMEL-12975
> Project: Camel
> Issue Type: Bug
> Components: camel-jaxb, camel-spring-boot-starters
>Affects Versions: 2.23.0, 2.24.0
>Reporter: Pascal Schumacher
>Priority: Minor
> Fix For: 3.0.0
>
>
> I'm using camel-jaxb-starter 2.23.0 in combination with Spring Boot 2.1.1.
> During start-up this warning is displayed:
> {{WARN 15204 --- [ main] o.a.c.i.DefaultCamelBeanPostProcessor:
> No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter}}
> Otherwise everything is working fine (as far as I can tell).
> I created a minimal project that allows reproducing this warning:
> https://github.com/PascalSchumacher/CamelJaxbStartupWarning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12975) WARN: No CamelContext defined yet so cannot inject into bean: org.apache.camel.converter.jaxb.FallbackTypeConverter
[
https://issues.apache.org/jira/browse/CAMEL-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865807#comment-16865807
]
Freeman Fang commented on CAMEL-12975:
--
I think we also need to add org.apache.camel.DeferredContextBinding annotation
to org.apache.camel.converter.jaxb.FallbackTypeConverter to get rid of the WARN
message
> WARN: No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter
> ---
>
> Key: CAMEL-12975
> URL: https://issues.apache.org/jira/browse/CAMEL-12975
> Project: Camel
> Issue Type: Bug
> Components: camel-jaxb, camel-spring-boot-starters
>Affects Versions: 2.23.0, 2.24.0
>Reporter: Pascal Schumacher
>Priority: Minor
> Fix For: 3.0.0
>
>
> I'm using camel-jaxb-starter 2.23.0 in combination with Spring Boot 2.1.1.
> During start-up this warning is displayed:
> {{WARN 15204 --- [ main] o.a.c.i.DefaultCamelBeanPostProcessor:
> No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter}}
> Otherwise everything is working fine (as far as I can tell).
> I created a minimal project that allows reproducing this warning:
> https://github.com/PascalSchumacher/CamelJaxbStartupWarning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-13650) Properties component - loadProperties to return properties in order
[ https://issues.apache.org/jira/browse/CAMEL-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865797#comment-16865797 ] John Poth edited comment on CAMEL-13650 at 6/17/19 5:17 PM: Should be fixed with [https://github.com/apache/camel/commit/684378fcfd5a4e57a6290761bc7a5faaf43c9805] was (Author: jpoth): Should have been fixed with https://github.com/apache/camel/commit/684378fcfd5a4e57a6290761bc7a5faaf43c9805 > Properties component - loadProperties to return properties in order > --- > > Key: CAMEL-13650 > URL: https://issues.apache.org/jira/browse/CAMEL-13650 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > The API > Properties loadProperties(); > Properties loadProperties(String... locations); > But the Properties is a Hashtable that is unordered, but it would be better > if we could get this as Map so we can use LinkedHashMap so they are in order. > This would work better with the order the end users may define in their > application.properties files etc > camel.component.jms.configuration.connectionFactory=#class:org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory > camel.component.jms.configuration.connectionFactory.brokerUrl=localhost:61616 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13650) Properties component - loadProperties to return properties in order
[ https://issues.apache.org/jira/browse/CAMEL-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865797#comment-16865797 ] John Poth commented on CAMEL-13650: --- Should have been fixed with https://github.com/apache/camel/commit/684378fcfd5a4e57a6290761bc7a5faaf43c9805 > Properties component - loadProperties to return properties in order > --- > > Key: CAMEL-13650 > URL: https://issues.apache.org/jira/browse/CAMEL-13650 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > The API > Properties loadProperties(); > Properties loadProperties(String... locations); > But the Properties is a Hashtable that is unordered, but it would be better > if we could get this as Map so we can use LinkedHashMap so they are in order. > This would work better with the order the end users may define in their > application.properties files etc > camel.component.jms.configuration.connectionFactory=#class:org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory > camel.component.jms.configuration.connectionFactory.brokerUrl=localhost:61616 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13650) Properties component - loadProperties to return properties in order
[ https://issues.apache.org/jira/browse/CAMEL-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865760#comment-16865760 ] Colm O hEigeartaigh commented on CAMEL-13650: - [~davsclaus] - looks like this could have caused the failing tests on master with JDK 11? https://builds.apache.org/job/Camel%20JDK11/job/master/187/ > Properties component - loadProperties to return properties in order > --- > > Key: CAMEL-13650 > URL: https://issues.apache.org/jira/browse/CAMEL-13650 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > The API > Properties loadProperties(); > Properties loadProperties(String... locations); > But the Properties is a Hashtable that is unordered, but it would be better > if we could get this as Map so we can use LinkedHashMap so they are in order. > This would work better with the order the end users may define in their > application.properties files etc > camel.component.jms.configuration.connectionFactory=#class:org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory > camel.component.jms.configuration.connectionFactory.brokerUrl=localhost:61616 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13656) reifiers classes should be public
Luca Burgazzoli created CAMEL-13656: --- Summary: reifiers classes should be public Key: CAMEL-13656 URL: https://issues.apache.org/jira/browse/CAMEL-13656 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Luca Burgazzoli Assignee: Luca Burgazzoli Fix For: 3.0.0.M4 Refiers classes are now package private that make it impossible to reuse them for example in a custom processor factory like what it is done by Hystrix: https://github.com/apache/camel/blob/master/components/camel-hystrix/src/main/java/org/apache/camel/component/hystrix/processor/HystrixProcessorFactory.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13655) Allow to plug a custom ProcessorReifier
Luca Burgazzoli created CAMEL-13655: --- Summary: Allow to plug a custom ProcessorReifier Key: CAMEL-13655 URL: https://issues.apache.org/jira/browse/CAMEL-13655 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Luca Burgazzoli Assignee: Luca Burgazzoli Fix For: 3.0.0.M4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13652) Allow to plug a custom DataFormatReifier
[ https://issues.apache.org/jira/browse/CAMEL-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli resolved CAMEL-13652. - Resolution: Fixed > Allow to plug a custom DataFormatReifier > > > Key: CAMEL-13652 > URL: https://issues.apache.org/jira/browse/CAMEL-13652 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 3.0.0.M4 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13652) Allow to plug a custom DataFormatReifier
[ https://issues.apache.org/jira/browse/CAMEL-13652?focusedWorklogId=261309=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-261309 ] ASF GitHub Bot logged work on CAMEL-13652: -- Author: ASF GitHub Bot Created on: 17/Jun/19 12:26 Start Date: 17/Jun/19 12:26 Worklog Time Spent: 10m Work Description: lburgazzoli commented on pull request #2981: CAMEL-13652: Allow to plug a custom DataFormatReifier URL: https://github.com/apache/camel/pull/2981 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: 261309) Time Spent: 10m Remaining Estimate: 0h > Allow to plug a custom DataFormatReifier > > > Key: CAMEL-13652 > URL: https://issues.apache.org/jira/browse/CAMEL-13652 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 3.0.0.M4 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13647) camel-main - Add support for auto binding to components by interface type and discover impl class on classpath
[ https://issues.apache.org/jira/browse/CAMEL-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13647. - Resolution: Fixed > camel-main - Add support for auto binding to components by interface type and > discover impl class on classpath > -- > > Key: CAMEL-13647 > URL: https://issues.apache.org/jira/browse/CAMEL-13647 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > This can make convention over configuration nicer. For example some > components requires a ConnectionFactory etc and if we can auto-discover that > on the classpath there is only 1 implementation of such interface, we can try > to auto create the instance and configure it on the component. > This should be an option you can turn on|off. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13654) optaplanner-7.23 not usable in WildFly
[
https://issues.apache.org/jira/browse/CAMEL-13654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-13654:
---
Description:
drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader &&
isOsgiClassLoader(droolsClassLoader)) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
drools-7.14 uses
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
In a non flat classpath environment, the later version of drools does not allow
the CL to get set to anything that is not an OSGi CL.
CrossRefs: https://github.com/wildfly-extras/wildfly-camel/issues/2831,
https://github.com/kiegroup/drools/commit/85c5308031a84a0ac4086c1df363bb1b4b3c6af9
was:
drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader &&
isOsgiClassLoader(droolsClassLoader)) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
drools-7.14 uses
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
In a non flat classpath environment, the later version of drools does not allow
the CL to get set to anything that is not an OSGi CL.
CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2831
> optaplanner-7.23 not usable in WildFly
> --
>
> Key: CAMEL-13654
> URL: https://issues.apache.org/jira/browse/CAMEL-13654
> Project: Camel
> Issue Type: Bug
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader &&
> isOsgiClassLoader(droolsClassLoader)) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> drools-7.14 uses
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> In a non flat classpath environment, the later version of drools does not
> allow the CL to get set to anything that is not an OSGi CL.
> CrossRefs: https://github.com/wildfly-extras/wildfly-camel/issues/2831,
> https://github.com/kiegroup/drools/commit/85c5308031a84a0ac4086c1df363bb1b4b3c6af9
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13654) optaplanner-7.23 not usable in WildFly
[
https://issues.apache.org/jira/browse/CAMEL-13654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-13654:
---
Description:
drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader &&
isOsgiClassLoader(droolsClassLoader)) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
drools-7.14 uses
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
In a non flat classpath environment, the later version of drools does not allow
the CL to get set to anything that is not an OSGi CL.
CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2831
was:
drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader &&
isOsgiClassLoader(droolsClassLoader)) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
drools-7.14 uses
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
In a non flat classpath environment, the later version of drools does not allow
the CL to get set to anything that is not an OSGi CL.
> optaplanner-7.23 not usable in WildFly
> --
>
> Key: CAMEL-13654
> URL: https://issues.apache.org/jira/browse/CAMEL-13654
> Project: Camel
> Issue Type: Bug
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader &&
> isOsgiClassLoader(droolsClassLoader)) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> drools-7.14 uses
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> In a non flat classpath environment, the later version of drools does not
> allow the CL to get set to anything that is not an OSGi CL.
> CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2831
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13654) optaplanner-7.23 not usable in WildFly
[
https://issues.apache.org/jira/browse/CAMEL-13654?focusedWorklogId=261281=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-261281
]
ASF GitHub Bot logged work on CAMEL-13654:
--
Author: ASF GitHub Bot
Created on: 17/Jun/19 11:12
Start Date: 17/Jun/19 11:12
Worklog Time Spent: 10m
Work Description: tdiesler commented on pull request #2980: [CAMEL-13654]
optaplanner-7.23 not usable in WildFly
URL: https://github.com/apache/camel/pull/2980
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: 261281)
Time Spent: 10m
Remaining Estimate: 0h
> optaplanner-7.23 not usable in WildFly
> --
>
> Key: CAMEL-13654
> URL: https://issues.apache.org/jira/browse/CAMEL-13654
> Project: Camel
> Issue Type: Bug
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader &&
> isOsgiClassLoader(droolsClassLoader)) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> drools-7.14 uses
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> In a non flat classpath environment, the later version of drools does not
> allow the CL to get set to anything that is not an OSGi CL.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13654) optaplanner-7.23 not usable in WildFly
[
https://issues.apache.org/jira/browse/CAMEL-13654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-13654:
---
Description:
drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader &&
isOsgiClassLoader(droolsClassLoader)) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
drools-7.14 uses
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
In a non flat classpath environment, the later version of drools does not allow
the CL to get set to anything that is not an OSGi CL.
was:
drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader &&
isOsgiClassLoader(droolsClassLoader)) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
drools-7.14 uses
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
In a non flat classpath environment, the later version of drools does not allow
the CL to get set to anything that is not an OSGi CL. Hence, it will fail in
any other modular environment, except OSGi.
> optaplanner-7.23 not usable in WildFly
> --
>
> Key: CAMEL-13654
> URL: https://issues.apache.org/jira/browse/CAMEL-13654
> Project: Camel
> Issue Type: Bug
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0
>
>
> drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader &&
> isOsgiClassLoader(droolsClassLoader)) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> drools-7.14 uses
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> In a non flat classpath environment, the later version of drools does not
> allow the CL to get set to anything that is not an OSGi CL.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13654) optaplanner-7.23 not usable in WildFly
[
https://issues.apache.org/jira/browse/CAMEL-13654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-13654:
---
Description:
drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader &&
isOsgiClassLoader(droolsClassLoader)) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
drools-7.14 uses
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
In a non flat classpath environment, the later version of drools does not allow
the CL to get set to anything that is not an OSGi CL. Hence, it will fail in
any other modular environment, except OSGi.
was:
drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader &&
isOsgiClassLoader(droolsClassLoader)) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
drools-7.14 uses
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
The later version of drools does not allow the CL to get set to anything that
is not an OSGi CL. Hence, it will fail in any other modular environment, except
OSGi.
> optaplanner-7.23 not usable in WildFly
> --
>
> Key: CAMEL-13654
> URL: https://issues.apache.org/jira/browse/CAMEL-13654
> Project: Camel
> Issue Type: Bug
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0
>
>
> drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader &&
> isOsgiClassLoader(droolsClassLoader)) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> drools-7.14 uses
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> In a non flat classpath environment, the later version of drools does not
> allow the CL to get set to anything that is not an OSGi CL. Hence, it will
> fail in any other modular environment, except OSGi.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13654) optaplanner-7.23 not usable in WildFly
[
https://issues.apache.org/jira/browse/CAMEL-13654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-13654:
---
Summary: optaplanner-7.23 not usable in WildFly (was: optaplanner-7.23 not
usable in wildfly)
> optaplanner-7.23 not usable in WildFly
> --
>
> Key: CAMEL-13654
> URL: https://issues.apache.org/jira/browse/CAMEL-13654
> Project: Camel
> Issue Type: Bug
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0
>
>
> drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader &&
> isOsgiClassLoader(droolsClassLoader)) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> drools-7.14 uses
> {code}
> public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
> if (getParent() != droolsClassLoader) {
> this.droolsClassLoader = droolsClassLoader;
> if (CACHE_NON_EXISTING_CLASSES) {
> nonExistingClasses.clear();
> }
> }
> }
> {code}
> The later version of drools does not allow the CL to get set to anything that
> is not an OSGi CL. Hence, it will fail in any other modular environment,
> except OSGi.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13654) optaplanner-7.23 not usable in wildfly
Thomas Diesler created CAMEL-13654:
--
Summary: optaplanner-7.23 not usable in wildfly
Key: CAMEL-13654
URL: https://issues.apache.org/jira/browse/CAMEL-13654
Project: Camel
Issue Type: Bug
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 3.0.0
drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader &&
isOsgiClassLoader(droolsClassLoader)) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
drools-7.14 uses
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
The later version of drools does not allow the CL to get set to anything that
is not an OSGi CL. Hence, it will fail in any other modular environment, except
OSGi.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13653) Repair some failed CI tests (aufs layer ... no such file or directory)
[ https://issues.apache.org/jira/browse/CAMEL-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865473#comment-16865473 ] Alex Dettinger commented on CAMEL-13653: 3 tests involving the docker image consul:1.0.7 are failing in CI: * ContainerAwareSpringTestSupportIT * ContainerAwareTestSupportIT * ConsulServiceRegistryIT For those 3 tests, the error message below is issued: open /var/lib/docker/aufs/layers/d85e709cc8231015022bfd721c48294479f5f117dbd2da8412cae2aa0ec06648: no such file or directory The issue can't be reproduced locally for any of those 3 tests. Reference to similar issues suggest that possible solutions could involve, not using cache, upgrading docker version, re-pulling the image or cleaning up all docker data and restarting the daemon. As a first step, let's upgrade the ConsulServiceRegistryIT image to consul:1.5.1. This way, a new fresh image will be pulled, and we gain information around a possible corruption. If successful, we should consider upgrading all tests and base test class involving consul 1.0.7. > Repair some failed CI tests (aufs layer ... no such file or directory) > -- > > Key: CAMEL-13653 > URL: https://issues.apache.org/jira/browse/CAMEL-13653 > Project: Camel > Issue Type: Task >Affects Versions: 3.0.0-M3 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13653) Repair some failed CI tests (aufs layer ... no such file or directory)
[ https://issues.apache.org/jira/browse/CAMEL-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13653: --- Affects Version/s: 3.0.0-M3 > Repair some failed CI tests (aufs layer ... no such file or directory) > -- > > Key: CAMEL-13653 > URL: https://issues.apache.org/jira/browse/CAMEL-13653 > Project: Camel > Issue Type: Task >Affects Versions: 3.0.0-M3 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13653) Repair some failed CI tests (aufs layer ... no such file or directory)
[ https://issues.apache.org/jira/browse/CAMEL-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-13653: -- Assignee: Alex Dettinger > Repair some failed CI tests (aufs layer ... no such file or directory) > -- > > Key: CAMEL-13653 > URL: https://issues.apache.org/jira/browse/CAMEL-13653 > Project: Camel > Issue Type: Task >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13653) Repair some failed CI tests (aufs layer ... no such file or directory)
Alex Dettinger created CAMEL-13653: -- Summary: Repair some failed CI tests (aufs layer ... no such file or directory) Key: CAMEL-13653 URL: https://issues.apache.org/jira/browse/CAMEL-13653 Project: Camel Issue Type: Task Reporter: Alex Dettinger -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-13563. - Resolution: Fixed > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.25.0, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13652) Allow to plug a custom DataFormatReifier
Luca Burgazzoli created CAMEL-13652: --- Summary: Allow to plug a custom DataFormatReifier Key: CAMEL-13652 URL: https://issues.apache.org/jira/browse/CAMEL-13652 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Luca Burgazzoli Assignee: Luca Burgazzoli Fix For: 3.0.0.M4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-13647) camel-main - Add support for auto binding to components by interface type and discover impl class on classpath
[ https://issues.apache.org/jira/browse/CAMEL-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865129#comment-16865129 ] Claus Ibsen edited comment on CAMEL-13647 at 6/17/19 7:39 AM: -- So we can add support for - constructor parameters *LATER* - private setters *DONE* So you can say that the method is private via #private# or something like that ...connectionFactory.#private#brokerUrl=localhost:61616 Okay we now support private methods by default (but you can turn it off) ...connectionFactory.brokerUrl=localhost:61616 was (Author: davsclaus): So we can add support for - constructor parameters - private setters *DONE* So you can say that the method is private via #private# or something like that ...connectionFactory.#private#brokerUrl=localhost:61616 Okay we now support private methods by default (but you can turn it off) ...connectionFactory.brokerUrl=localhost:61616 > camel-main - Add support for auto binding to components by interface type and > discover impl class on classpath > -- > > Key: CAMEL-13647 > URL: https://issues.apache.org/jira/browse/CAMEL-13647 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > This can make convention over configuration nicer. For example some > components requires a ConnectionFactory etc and if we can auto-discover that > on the classpath there is only 1 implementation of such interface, we can try > to auto create the instance and configure it on the component. > This should be an option you can turn on|off. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-13647) camel-main - Add support for auto binding to components by interface type and discover impl class on classpath
[ https://issues.apache.org/jira/browse/CAMEL-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865129#comment-16865129 ] Claus Ibsen edited comment on CAMEL-13647 at 6/17/19 7:34 AM: -- So we can add support for - constructor parameters - private setters *DONE* So you can say that the method is private via #private# or something like that ...connectionFactory.#private#brokerUrl=localhost:61616 Okay we now support private methods by default (but you can turn it off) ...connectionFactory.brokerUrl=localhost:61616 was (Author: davsclaus): So we can add support for - constructor parameters - private setters *DONE* So you can say that the method is private via #private# or something like that ...connectionFactory.#private#brokerUrl=localhost:61616 > camel-main - Add support for auto binding to components by interface type and > discover impl class on classpath > -- > > Key: CAMEL-13647 > URL: https://issues.apache.org/jira/browse/CAMEL-13647 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > This can make convention over configuration nicer. For example some > components requires a ConnectionFactory etc and if we can auto-discover that > on the classpath there is only 1 implementation of such interface, we can try > to auto create the instance and configure it on the component. > This should be an option you can turn on|off. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13466) DefaultCamelContext not stopping all routes on doStop()
[
https://issues.apache.org/jira/browse/CAMEL-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13466:
Fix Version/s: (was: 2.24.1)
(was: 2.23.3)
2.23.4
2.24.2
> DefaultCamelContext not stopping all routes on doStop()
> ---
>
> Key: CAMEL-13466
> URL: https://issues.apache.org/jira/browse/CAMEL-13466
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.20.1
>Reporter: Julien Greffe
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.25.0, 2.24.2
>
> Attachments: sample-dozer-route-2.0.0-SNAPSHOT.jar
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hello,
> after applying CAMEL-12980,
> we're still facing an issue with a failing starting feature and the
> CXFServlet {{/services}} URL.
>
> To reproduce :
> * drop the attached JAR in deploy
> * wait for bundle start and failure
> * access {{/services}} URL : endpoint + WSDL are listed > is this an
> expected behaviour?
>
> For further analysis, it seems to be something missing in camel-core :
> When blueprint fails, the {{doStop()}} method is called :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
> At that line, it tries to stop only the routes already started, but not the
> ones failing *before* filling {{routeStartupOrder}} List.
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L4041]
> One of this routes is a CxfConsumer which has already been instanciated, with
> a server creation :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java#L69]
> Even with {{DefaultCamelContext.doStop()}}, the server is still started and
> available in {{/services}}.
> Tried a fix by adding this line in DefaultCamelContext:3502 :
> {code:java}
> // fill all the routes to be stopped
> getRouteStartupOrder().addAll(routeServices.values().stream().map(this::doPrepareRouteToBeStarted).collect(Collectors.toList()));
> // stop route inputs in the same order as they was started so we stop the
> very first inputs first
> try {
> // force shutting down routes as they may otherwise cause shutdown to hang
> ...
> {code}
> And now the endpoint isn't available anymore.
> But this fix isn't effective enough as {{getRouteStartupOrder()}} may have
> duplicates?
> Thanks,
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
