[jira] [Updated] (CAMEL-13663) camel-main-maven-plugin - Generate tooling metadata
[ https://issues.apache.org/jira/browse/CAMEL-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13663: Attachment: Screenshot 2019-06-19 at 07.51.45.png > camel-main-maven-plugin - Generate tooling metadata > --- > > Key: CAMEL-13663 > URL: https://issues.apache.org/jira/browse/CAMEL-13663 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > Attachments: Screenshot 2019-06-19 at 07.51.45.png > > > To assist editing Camel Main and eg application.properties then we could > "fool" tooling by generating Spring Boot metadata json files, so tools see > these files and offer their code completions. > Then you can use ctrl + space for type completions when typing > camel.component.jms -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13663) camel-main-maven-plugin - Generate tooling metadata
[ https://issues.apache.org/jira/browse/CAMEL-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867212#comment-16867212 ] Claus Ibsen commented on CAMEL-13663: - Ah yeah got it to work with IDEA too if you [x] in spring boot settings: Allow to auto-configure application contexts > camel-main-maven-plugin - Generate tooling metadata > --- > > Key: CAMEL-13663 > URL: https://issues.apache.org/jira/browse/CAMEL-13663 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > To assist editing Camel Main and eg application.properties then we could > "fool" tooling by generating Spring Boot metadata json files, so tools see > these files and offer their code completions. > Then you can use ctrl + space for type completions when typing > camel.component.jms -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13663) camel-main-maven-plugin - Generate tooling metadata
[ https://issues.apache.org/jira/browse/CAMEL-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867208#comment-16867208 ] Claus Ibsen commented on CAMEL-13663: - Okay Visual Source Code seems to support this without having spring boot on the classpath / pom.xml > camel-main-maven-plugin - Generate tooling metadata > --- > > Key: CAMEL-13663 > URL: https://issues.apache.org/jira/browse/CAMEL-13663 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > To assist editing Camel Main and eg application.properties then we could > "fool" tooling by generating Spring Boot metadata json files, so tools see > these files and offer their code completions. > Then you can use ctrl + space for type completions when typing > camel.component.jms -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13663) camel-main-maven-plugin - Generate tooling metadata
[ https://issues.apache.org/jira/browse/CAMEL-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867200#comment-16867200 ] Claus Ibsen commented on CAMEL-13663: - Okay sadly this requires having spring-boot JARs on the classpath before the tooling in IDEA enables auto completion for properties files. > camel-main-maven-plugin - Generate tooling metadata > --- > > Key: CAMEL-13663 > URL: https://issues.apache.org/jira/browse/CAMEL-13663 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > To assist editing Camel Main and eg application.properties then we could > "fool" tooling by generating Spring Boot metadata json files, so tools see > these files and offer their code completions. > Then you can use ctrl + space for type completions when typing > camel.component.jms -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13658) Refine ProcessorDefinition output handling
[
https://issues.apache.org/jira/browse/CAMEL-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13658.
-
Resolution: Fixed
> 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
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 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] [Commented] (CAMEL-13658) Refine ProcessorDefinition output handling
[
https://issues.apache.org/jira/browse/CAMEL-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867007#comment-16867007
]
Claus Ibsen commented on CAMEL-13658:
-
Okay got a working prototype doing a bit more testing before merging. Now you
can check via instanceof OutputNode to know if it supports output or not - we
also use this in the apt compiler plugin when generating model json schema
files.
> 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
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 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] [Updated] (CAMEL-13658) Refine ProcessorDefinition output handling
[
https://issues.apache.org/jira/browse/CAMEL-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13658:
Fix Version/s: 3.0.0
> 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
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 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] [Moved] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11
[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang moved CXF-8058 to CAMEL-13664: --- Workflow: classic default workflow (was: Default workflow, editable Closed status) Key: CAMEL-13664 (was: CXF-8058) Project: Camel (was: CXF) > OSGi tests broken for both JDK8 and JDK11 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test >Reporter: Freeman Fang >Priority: Major > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11
[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13664: Assignee: Freeman Fang > OSGi tests broken for both JDK8 and JDK11 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0 > > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11
[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-13664: - Fix Version/s: 3.0.0 Component/s: osgi > OSGi tests broken for both JDK8 and JDK11 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Priority: Major > Fix For: 3.0.0 > > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13658) Refine ProcessorDefinition output handling
[
https://issues.apache.org/jira/browse/CAMEL-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866931#comment-16866931
]
Claus Ibsen commented on CAMEL-13658:
-
Okay working on adding OutputNode to mark which model classes has output or not
> 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
>Assignee: Claus Ibsen
>Priority: Minor
> 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] [Assigned] (CAMEL-13658) Refine ProcessorDefinition output handling
[
https://issues.apache.org/jira/browse/CAMEL-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-13658:
---
Assignee: Claus Ibsen
> 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
>Assignee: Claus Ibsen
>Priority: Minor
> 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] [Created] (CAMEL-13663) camel-main-maven-plugin - Generate tooling metadata
Claus Ibsen created CAMEL-13663: --- Summary: camel-main-maven-plugin - Generate tooling metadata Key: CAMEL-13663 URL: https://issues.apache.org/jira/browse/CAMEL-13663 Project: Camel Issue Type: New Feature Components: tooling Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.0.0, 3.0.0.M4 To assist editing Camel Main and eg application.properties then we could "fool" tooling by generating Spring Boot metadata json files, so tools see these files and offer their code completions. Then you can use ctrl + space for type completions when typing camel.component.jms -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13660) xml-specs - Can we upgrade stax2-api from 3.x to 4.x
[ https://issues.apache.org/jira/browse/CAMEL-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866809#comment-16866809 ] Freeman Fang commented on CAMEL-13660: -- In OSGi if we upgrade to stax2 4.x, we also should upgrade to woodstox-core 5.x > xml-specs - Can we upgrade stax2-api from 3.x to 4.x > > > Key: CAMEL-13660 > URL: https://issues.apache.org/jira/browse/CAMEL-13660 > Project: Camel > Issue Type: Task > Components: karaf, osgi >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.0.0 > > > I wonder if we can upgrade to use the v4 of stax2-api's? The camel-stax > component now uses that, but the xml-specs feature is using the old v3 from > 2014 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13662) [MongoDB] Allow component to get connectionBean from properties
[ https://issues.apache.org/jira/browse/CAMEL-13662?focusedWorklogId=262356=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-262356 ] ASF GitHub Bot logged work on CAMEL-13662: -- Author: ASF GitHub Bot Created on: 18/Jun/19 14:55 Start Date: 18/Jun/19 14:55 Worklog Time Spent: 10m Work Description: squakez commented on pull request #2984: CAMEL-13662 connectionBean fallback to properties URL: https://github.com/apache/camel/pull/2984 * Adding the possibility to get connection from properties * Extend a basic unit test in order to use the new feature * Add a timeout as the test was hanging up indefinitely 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: 262356) Time Spent: 10m Remaining Estimate: 0h > [MongoDB] Allow component to get connectionBean from properties > --- > > Key: CAMEL-13662 > URL: https://issues.apache.org/jira/browse/CAMEL-13662 > Project: Camel > Issue Type: Improvement > Components: camel-mongodb3 >Affects Versions: 3.0.0 >Reporter: Pasquale Congiusti >Priority: Major > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The component allow to get a connectionBean client only from context, making > difficult to inject it at runtime. I'd like to make some change that would > allow to retrieve the connectionBean from properties if it is not found in > the context. > I'd keep therefore retrocompatibility and ensure through proper unit testing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (CAMEL-13660) xml-specs - Can we upgrade stax2-api from 3.x to 4.x
[ https://issues.apache.org/jira/browse/CAMEL-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-13660 started by Ramu. > xml-specs - Can we upgrade stax2-api from 3.x to 4.x > > > Key: CAMEL-13660 > URL: https://issues.apache.org/jira/browse/CAMEL-13660 > Project: Camel > Issue Type: Task > Components: karaf, osgi >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.0.0 > > > I wonder if we can upgrade to use the v4 of stax2-api's? The camel-stax > component now uses that, but the xml-specs feature is using the old v3 from > 2014 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13660) xml-specs - Can we upgrade stax2-api from 3.x to 4.x
[ https://issues.apache.org/jira/browse/CAMEL-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866654#comment-16866654 ] Ramu commented on CAMEL-13660: -- looking into it > xml-specs - Can we upgrade stax2-api from 3.x to 4.x > > > Key: CAMEL-13660 > URL: https://issues.apache.org/jira/browse/CAMEL-13660 > Project: Camel > Issue Type: Task > Components: karaf, osgi >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.0.0 > > > I wonder if we can upgrade to use the v4 of stax2-api's? The camel-stax > component now uses that, but the xml-specs feature is using the old v3 from > 2014 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13660) xml-specs - Can we upgrade stax2-api from 3.x to 4.x
[ https://issues.apache.org/jira/browse/CAMEL-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-13660: Assignee: Ramu > xml-specs - Can we upgrade stax2-api from 3.x to 4.x > > > Key: CAMEL-13660 > URL: https://issues.apache.org/jira/browse/CAMEL-13660 > Project: Camel > Issue Type: Task > Components: karaf, osgi >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.0.0 > > > I wonder if we can upgrade to use the v4 of stax2-api's? The camel-stax > component now uses that, but the xml-specs feature is using the old v3 from > 2014 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13662) [MongoDB] Allow component to get connectionBean from properties
[ https://issues.apache.org/jira/browse/CAMEL-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866652#comment-16866652 ] Pasquale Congiusti commented on CAMEL-13662: I've already worked on it, just proceeding to PR... > [MongoDB] Allow component to get connectionBean from properties > --- > > Key: CAMEL-13662 > URL: https://issues.apache.org/jira/browse/CAMEL-13662 > Project: Camel > Issue Type: Improvement > Components: camel-mongodb3 >Affects Versions: 3.0.0 >Reporter: Pasquale Congiusti >Priority: Major > Fix For: 3.0.0 > > > The component allow to get a connectionBean client only from context, making > difficult to inject it at runtime. I'd like to make some change that would > allow to retrieve the connectionBean from properties if it is not found in > the context. > I'd keep therefore retrocompatibility and ensure through proper unit testing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13662) [MongoDB] Allow component to get connectionBean from properties
Pasquale Congiusti created CAMEL-13662: -- Summary: [MongoDB] Allow component to get connectionBean from properties Key: CAMEL-13662 URL: https://issues.apache.org/jira/browse/CAMEL-13662 Project: Camel Issue Type: Improvement Components: camel-mongodb3 Affects Versions: 3.0.0 Reporter: Pasquale Congiusti Fix For: 3.0.0 The component allow to get a connectionBean client only from context, making difficult to inject it at runtime. I'd like to make some change that would allow to retrieve the connectionBean from properties if it is not found in the context. I'd keep therefore retrocompatibility and ensure through proper unit testing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13658) Refine ProcessorDefinition output handling
[
https://issues.apache.org/jira/browse/CAMEL-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866590#comment-16866590
]
Luca Burgazzoli commented on CAMEL-13658:
-
I saw it but it is not possible to detect if a definition support outputs at
compile time, i.e. with an instanceOf (well, theoretically you can check for
NoOutputDefinition but there's no guarantees).
> 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
>Priority: Minor
> 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] [Commented] (CAMEL-13638) camel-salesforce - Lookups to polymorphic relationship fields must include an attributes object with a type property
[
https://issues.apache.org/jira/browse/CAMEL-13638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866451#comment-16866451
]
Colm O hEigeartaigh commented on CAMEL-13638:
-
[~aldettinger] - I backported the fix to camel-2.x, as it was causing a test
failure there as well.
> camel-salesforce - Lookups to polymorphic relationship fields must include an
> attributes object with a type property
>
>
> Key: CAMEL-13638
> URL: https://issues.apache.org/jira/browse/CAMEL-13638
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
>Affects Versions: 2.24.0, 3.0.0-M2
>Reporter: Jeremy Ross
>Priority: Major
> Fix For: 2.24.1, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When referencing a related record that is a polymorphic lookup, the JSON must
> include an {{attributes}} object with a {{type}} property indicating which
> type of Object is being referenced.
> E.g.:
> {code:json}
> {
> "Description": "Contact HR for further information",
> "Status": "Completed",
> "Who": {
> "attributes": {
> "type": "Contact"
> },
> "External_Id_Field__c": "cfcec54d-5d77-4ffa-a2ec-7fa2ce0e9616"
> },
> "Subject": "Comment"
> }
> {code}
> This {{attributes}} object is optional for non-polymorphic lookups, so no
> harm in including it in all lookups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-13661) camel-example-spring-cloud-serviceregistry is failing
[ https://issues.apache.org/jira/browse/CAMEL-13661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-13661: -- Assignee: Alex Dettinger > camel-example-spring-cloud-serviceregistry is failing > - > > Key: CAMEL-13661 > URL: https://issues.apache.org/jira/browse/CAMEL-13661 > Project: Camel > Issue Type: Bug > Components: examples >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > > There is a version misalignment as spring boot and spring cloud release train > are bound together. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13661) camel-example-spring-cloud-serviceregistry is failing
Alex Dettinger created CAMEL-13661: -- Summary: camel-example-spring-cloud-serviceregistry is failing Key: CAMEL-13661 URL: https://issues.apache.org/jira/browse/CAMEL-13661 Project: Camel Issue Type: Bug Components: examples Reporter: Alex Dettinger There is a version misalignment as spring boot and spring cloud release train are bound together. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13661) camel-example-spring-cloud-serviceregistry is failing
[ https://issues.apache.org/jira/browse/CAMEL-13661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13661: --- Affects Version/s: 3.0.0-M3 > camel-example-spring-cloud-serviceregistry is failing > - > > Key: CAMEL-13661 > URL: https://issues.apache.org/jira/browse/CAMEL-13661 > Project: Camel > Issue Type: Bug > Components: examples >Affects Versions: 3.0.0-M3 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > > There is a version misalignment as spring boot and spring cloud release train > are bound together. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13651) Rest DSL seems to duplicate the routes, therefore we can experience on having duplicated ids issues
[
https://issues.apache.org/jira/browse/CAMEL-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866427#comment-16866427
]
Jonathan Vila commented on CAMEL-13651:
---
[~davsclaus] I will search for the issue and try to backport for 2.23.x
> Rest DSL seems to duplicate the routes, therefore we can experience on having
> duplicated ids issues
> ---
>
> Key: CAMEL-13651
> URL: https://issues.apache.org/jira/browse/CAMEL-13651
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Jonathan Vila
>Priority: Major
>
> Having this route :
> {code:java}
> rest()
> .post("/upload/{customerID}")
> .to("direct:upload")
> .get("/health")
> .to("log:health")
> .get("/info")
> .to("log:info");
> {code}
> When I inspect *camelContext.getRoutes()* I see route1, route2, route3,
> post1, get1, get2 and route1 is identical to post1, and so on.
> So , if I try to assign an id to a route :
> {code:java}
> rest()
> .id("rest-route")
> .get("/health")
> .id("get-health")
> .to("log:health")
> .post("/uploadXX/{customerID}")
> .id("post-upload")
> .to("direct:upload")
> .get("/info")
> .id("get-info")
> .to("log:info");
> {code}
> Then I get an error : Failed to start route get-health because of duplicate
> id detected: get-health
> The motivation to give ids to rest routes is to test only one at a time. I do
> that using *@AdviceWith* and then *camelContext.startRoute("post1")*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (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 resolved CAMEL-13653. Resolution: Cannot Reproduce Fix Version/s: 3.0.0.M4 > 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 > Fix For: 3.0.0.M4 > > -- 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=16866342#comment-16866342 ] Alex Dettinger commented on CAMEL-13653: Those 3 CI tests sticky failed during 5 builds and now passes. The upgrade to the consul:1.5.1 image seems unrelated. Closing for now, let's track any new occurrences if any. > 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] [Created] (CAMEL-13660) xml-specs - Can we upgrade stax2-api from 3.x to 4.x
Claus Ibsen created CAMEL-13660: --- Summary: xml-specs - Can we upgrade stax2-api from 3.x to 4.x Key: CAMEL-13660 URL: https://issues.apache.org/jira/browse/CAMEL-13660 Project: Camel Issue Type: Task Components: karaf, osgi Reporter: Claus Ibsen Fix For: 3.0.0 I wonder if we can upgrade to use the v4 of stax2-api's? The camel-stax component now uses that, but the xml-specs feature is using the old v3 from 2014 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13373) camel-stax - FileInputStream not closed
[
https://issues.apache.org/jira/browse/CAMEL-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13373.
-
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: 3.0.0.M4
3.0.0
Thanks for reporting and the PR.
Mind that this happens on windows only
> camel-stax - FileInputStream not closed
> ---
>
> Key: CAMEL-13373
> URL: https://issues.apache.org/jira/browse/CAMEL-13373
> Project: Camel
> Issue Type: Bug
> Components: camel-stax
>Affects Versions: 2.23.1
>Reporter: Alexandru
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> The StAXProcessor.java class does not close the stream it opens.
> I had to modify it like this:
> public void process(Exchange exchange) throws Exception {
> InputSource is = exchange.getIn().getMandatoryBody(InputSource.class);
> XMLStreamReader stream =
> exchange.getIn().getMandatoryBody(XMLStreamReader.class);
> // Fermeture de la inputstream ici, car dans la version originale de la
> classe la stream reste ouverte.
> *try(InputStream inputStreamToClose = is.getByteStream()) {*
> XMLReader reader = new StaxStreamXMLReader(stream);
> ContentHandler handler;
> if (this.contentHandlerClass != null)
> { handler = (ContentHandler) this.contentHandlerClass.newInstance(); }
> else
> { handler = this.contentHandler; }
> reader.setContentHandler(handler);
> reader.parse(is);
> if (ExchangeHelper.isOutCapable(exchange))
> { exchange.getOut().setHeaders(exchange.getIn().getHeaders());
> exchange.getOut().setBody(handler); }
> else
> { exchange.getIn().setBody(handler); }
> } *finally*
> *{ // Fermeture de la strem ValidatingStreamReader validatingStreamReader =
> (ValidatingStreamReader)stream; validatingStreamReader.closeCompletely(); }*
> *}*
--
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
]
Andrea Cosentino updated CAMEL-13654:
-
Fix Version/s: 3.0.0.M4
> 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, 3.0.0.M4
>
> Time Spent: 20m
> 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] [Resolved] (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
]
Andrea Cosentino resolved CAMEL-13654.
--
Resolution: Fixed
> 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: 20m
> 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] [Work logged] (CAMEL-13654) optaplanner-7.23 not usable in WildFly
[
https://issues.apache.org/jira/browse/CAMEL-13654?focusedWorklogId=262120=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-262120
]
ASF GitHub Bot logged work on CAMEL-13654:
--
Author: ASF GitHub Bot
Created on: 18/Jun/19 07:56
Start Date: 18/Jun/19 07:56
Worklog Time Spent: 10m
Work Description: oscerd 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: 262120)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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] [Commented] (CAMEL-13658) Refine ProcessorDefinition output handling
[
https://issues.apache.org/jira/browse/CAMEL-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866314#comment-16866314
]
Claus Ibsen commented on CAMEL-13658:
-
There is a method on the processor definiton
public abstract boolean isOutputSupported();
Maybe that is sufficient?
> 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
>Priority: Minor
> 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] [Updated] (CAMEL-13657) Simpler attribute names in the XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13657:
Priority: Major (was: Minor)
> Simpler attribute names in the XML 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: Major
> Fix For: 3.0.0, 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-13657) Simpler attribute names in the XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13657:
Fix Version/s: 3.0.0
> Simpler attribute names in the XML 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, 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] [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=16866313#comment-16866313 ] Claus Ibsen commented on CAMEL-13650: - Thanks [~jpoth] for fixing this > 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] [Updated] (CAMEL-13657) Simpler attribute names in the XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13657:
Summary: Simpler attribute names in the XML DSL (was: Simpler names in the
DSL)
> Simpler attribute names in the XML 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)
