[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=16865142#comment-16865142 ] Claus Ibsen edited comment on CAMEL-13647 at 6/17/19 4:35 AM: -- Also we should add option to main to be case insensitive when setting these names, so you can say brokerUrl, brokerURL brokerurl etc and they would all work *WONT FIX* instead we report more detailed if there was no setter/getter with that exact name, so the user can fix it was (Author: davsclaus): Also we should add option to main to be case insensitive when setting these names, so you can say brokerUrl, brokerURL brokerurl etc and they would all work > 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 4:06 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 was (Author: davsclaus): So we can add support for - constructor parameters - private setters 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-13069) Display proper FTP reply message in case of transfer error
[
https://issues.apache.org/jira/browse/CAMEL-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13069:
Fix Version/s: (was: 2.23.3)
(was: 2.24.0)
2.25.0
> Display proper FTP reply message in case of transfer error
> --
>
> Key: CAMEL-13069
> URL: https://issues.apache.org/jira/browse/CAMEL-13069
> Project: Camel
> Issue Type: Improvement
> Components: camel-ftp
>Affects Versions: 2.23.0
> Environment: Any
>Reporter: Gerold Broser
>Priority: Major
> Labels: FTP, FTP-Reply
> Fix For: 3.0.0, 2.25.0
>
>
> When trying to transfer a file to an FTP server on an IBM mainframe that's
> too large for the allocated data set there I get the following log message:
> {code:java}
> ...
> 2019-01-16 10:10:22,368 WARN file.remote.RemoteFileProducer – Writing file
> failed with: File operation failed: 125 Storing data set
> TEST.TRANSFER.FB80.TXT
> IOException caught while copying.. Code: 125
> ...{code}
> This is confusing since according to RFC 959 [reply codes {{1yz}} are
> {{Positive Preliminary}} replies|https://tools.ietf.org/html/rfc959#page-37]
> with:
> {quote}[{{125 Data connection already open; transfer
> starting.}}|https://tools.ietf.org/html/rfc959#page-41]
> {quote}
> being more informational than exceptional.
> Performing the same transfer manually with FileZilla and Windows 7's command
> line ftp client results in:
> FileZilla:
> {code:java}
> ...
> Command: STOR TRANSFER.FB80.TXT
> Response: 125 Storing data set TEST.TRANSFER.FB80.TXT
> Response: 451-Error: Name=CkResults (Write) RC=-13
> Response: 451-System completion code and reason: B37-04
> Response: 451-Data set is out of space.
> Response: 451-Error (1013) closing the data set.
> Response: 451 Transfer aborted due to file error.
> ...{code}
> ftp:
> {code:java}
> ftp> send TRANSFER.FB80.TXT
> ---> PORT 10,100,113,251,254,235
> 200 Port request OK.
> ---> STOR TRANSFER.FB80.TXT
> 125 Storing data set TEST.TRANSFER.FB80.TXT
> 451-Error: Name=CkResults (Write) RC=-13
> 451-System completion code and reason: B37-04
> 451-Data set is out of space.
> 451-Error (1013) closing the data set.
> 451 Transfer aborted due to file error.
> ...{code}
> To get the real cause we can use Apache Commons Net's
> [{{FTP.getReply()}}|https://commons.apache.org/proper/commons-net/javadocs/api-3.6/org/apache/commons/net/ftp/FTP.html#getReply()]:
> {quote}Fetches a reply from the FTP server and returns the integer reply
> code. After calling this method, the actual reply text can be accessed from
> either calling getReplyString or getReplyStrings . Only use this method if
> you are implementing your own FTP client *or if you need to fetch a secondary
> response from the FTP server*.
> {quote}
> in the {{catch (IOException e)}} block in
> [{{FtpOperations.doStoreFile()}}|https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpOperations.java#L717]
> like:
> {code:java}
> ...
> catch (IOException e) {
> final IOException primary = new IOException(client.getReplyString());
> e = new IOException(e.getMessage(), primary);
> client.getReply(); // get secondary reply
> throw new GenericFileOperationFailedException(client.getReplyString(), e);
> }
> ...
> {code}
> which results in the following comprehensible stack trace in my test code:
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException:
> 451-Error: Name=CkResults (Write) RC=-13
> 451-System completion code and reason: B37-04
> 451-Data set is out of space.
> 451-Error (1013) closing the data set.
> 451 Transfer aborted due to file error.
> at my.FTPTransferTest.testMF_FTP((FTPTransferTest.java:74))
> ...
> Caused by: java.io.IOException: IOException caught while copying.
> at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:70)
> ... 24 more
> Caused by: java.io.IOException: 125 Storing data set TEST.TRANSFER.FB80.TXT
> at my.FTPTransferTest.testMF_FTP(FTPTransferTest.java:69)
> ... 24 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13118) Components should not depend on camel-core but camel-support
[ https://issues.apache.org/jira/browse/CAMEL-13118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13118. - Resolution: Fixed > Components should not depend on camel-core but camel-support > > > Key: CAMEL-13118 > URL: https://issues.apache.org/jira/browse/CAMEL-13118 > Project: Camel > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13259) Camel BOM - Add camel catalog and others
[ https://issues.apache.org/jira/browse/CAMEL-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13259: Fix Version/s: (was: 3.0.0-M3) 3.0.0.M4 > Camel BOM - Add camel catalog and others > > > Key: CAMEL-13259 > URL: https://issues.apache.org/jira/browse/CAMEL-13259 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > The Camel BOM includes what end users of Camel may use. And typically its the > components. However camel-catalog and a few other JARs may be good to add. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13643) Change Spring Boot starters Maven group ID
[
https://issues.apache.org/jira/browse/CAMEL-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13643:
Fix Version/s: (was: 3.0.0-M3)
3.0.0.M4
> Change Spring Boot starters Maven group ID
> --
>
> Key: CAMEL-13643
> URL: https://issues.apache.org/jira/browse/CAMEL-13643
> Project: Camel
> Issue Type: Task
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0.M4
>
>
> In order to allow for different kinds of _starters_ in the future, for
> example different versions of Spring Boot we should change the Maven group ID
> of Spring Boot, currently {{org.apache.camel}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13452) Refactor routeId generation and initiation for REST and common DSLs
[ https://issues.apache.org/jira/browse/CAMEL-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13452: Fix Version/s: (was: 3.0.0-M3) 3.0.0.M4 > Refactor routeId generation and initiation for REST and common DSLs > --- > > Key: CAMEL-13452 > URL: https://issues.apache.org/jira/browse/CAMEL-13452 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13141) camel-api - Add API for advising routes
[
https://issues.apache.org/jira/browse/CAMEL-13141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13141:
Fix Version/s: (was: 3.0.0-M3)
3.0.0.M4
> camel-api - Add API for advising routes
> ---
>
> Key: CAMEL-13141
> URL: https://issues.apache.org/jira/browse/CAMEL-13141
> Project: Camel
> Issue Type: New Feature
> Components: came-core
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
>
> We should likely add a nicer API for testing camel routes with the adviceWith
> functionality. Today you have to use a RouteReifier from camel-core. We
> should make a new API in camel-api and make it with a nicer name so its
> easier to understand and use.
> {code}
> RouteReifier.adviceWith(context.getRouteDefinitions().get(0),
> context, new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> // intercept sending to mock:foo and do something else
> interceptSendToEndpoint("mock:foo")
> .skipSendToOriginalEndpoint()
> .to("log:foo")
> .to("mock:advised");
> }
> });
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13435) Create an AWS-Translate component
[ https://issues.apache.org/jira/browse/CAMEL-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13435: Fix Version/s: (was: 3.0.0-M3) 3.0.0.M4 > Create an AWS-Translate component > - > > Key: CAMEL-13435 > URL: https://issues.apache.org/jira/browse/CAMEL-13435 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13201) camel3 - camel-core-minimal - To have core with as few dependencies as possible
[ https://issues.apache.org/jira/browse/CAMEL-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13201: Fix Version/s: (was: 3.0.0-M3) 3.0.0.M4 > camel3 - camel-core-minimal - To have core with as few dependencies as > possible > --- > > Key: CAMEL-13201 > URL: https://issues.apache.org/jira/browse/CAMEL-13201 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > The camel-core includes all the core components from 2.x. However you may > want to choose precisely only the core components you need. > So with a camel-core-minimal you can then add the ones afterwards, such as > log,timer and file etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13118) Components should not depend on camel-core but camel-support
[ https://issues.apache.org/jira/browse/CAMEL-13118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13118: Fix Version/s: (was: 3.0.0-M3) 3.0.0.M4 > Components should not depend on camel-core but camel-support > > > Key: CAMEL-13118 > URL: https://issues.apache.org/jira/browse/CAMEL-13118 > Project: Camel > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13505) Camel-Tracer: New implementation
[ https://issues.apache.org/jira/browse/CAMEL-13505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13505: Fix Version/s: (was: 3.0.0-M3) 3.0.0.M4 > Camel-Tracer: New implementation > > > Key: CAMEL-13505 > URL: https://issues.apache.org/jira/browse/CAMEL-13505 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > We deprecated the 2.x one and removed it, hence we need a new implementation > in Camel 3. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13384) Move camel core implementation into core/camel-engine and keep camel-core as a pom with all dependencies
[ https://issues.apache.org/jira/browse/CAMEL-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13384: Fix Version/s: (was: 3.0.0-M3) 3.0.0.M4 > Move camel core implementation into core/camel-engine and keep camel-core as > a pom with all dependencies > > > Key: CAMEL-13384 > URL: https://issues.apache.org/jira/browse/CAMEL-13384 > Project: Camel > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13371) Make xml and jaxb more optional in camel-base / camel-core
[ https://issues.apache.org/jira/browse/CAMEL-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13371: Fix Version/s: (was: 3.0.0-M3) 3.0.0.M4 > Make xml and jaxb more optional in camel-base / camel-core > -- > > Key: CAMEL-13371 > URL: https://issues.apache.org/jira/browse/CAMEL-13371 > Project: Camel > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16865142#comment-16865142 ] Claus Ibsen commented on CAMEL-13647: - Also we should add option to main to be case insensitive when setting these names, so you can say brokerUrl, brokerURL brokerurl etc and they would all work > 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] [Commented] (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 commented on CAMEL-13647: - So we can add support for - constructor parameters - private setters 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] [Commented] (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=16865128#comment-16865128 ] Claus Ibsen commented on CAMEL-13647: - The org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory sadly dont have setter/getter for brokerUrl which is really bad, so its not easy to configure it via properties. > 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] [Resolved] (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:all-tabpanel ] Claus Ibsen resolved CAMEL-13650. - Resolution: Fixed > 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-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=16865121#comment-16865121
]
Claus Ibsen commented on CAMEL-13651:
-
I think the duplicate id has been fixed in newer Camel version. Try with latest
2.24.0 etc
> 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] [Created] (CAMEL-13651) Rest DSL seems to duplicate the routes, therefore we can experience on having duplicated ids issues
Jonathan Vila created CAMEL-13651:
-
Summary: 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
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] [Created] (CAMEL-13650) Properties component - loadProperties to return properties in order
Claus Ibsen created CAMEL-13650: --- Summary: 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 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)
