[GitHub] camel pull request #1156: The interface SpringApplicationConfiguration is de...
Github user Pogorelov closed the pull request at: https://github.com/apache/camel/pull/1156 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Getting ready for Apache Camel 2.18 Release
On Sun, Aug 28, 2016 at 11:28 AM, Claus Ibsen wrote: > Hi > > Hope everybody had good summer vacation. I had my vacation in parts > and have next week as PTO. > > We should get started to close down on the upcoming Camel 2.18 release. > > > There is some outstanding work (in no particular order) > > 1) > Finish the spring boot stuff with the starter components. > Nicola comes back from PTO and will work on this. > Still pending. > 2) > rest-dsl to support calling REST services. I am working on this and > have some outstanding work still around binding and other > improvements. > Implemented. > 3) > Tidy up the log4j v2 upgrade. Some of the examples do not start with > the jetty plugin. > Fixed. > 4) > Migrate the last wiki pages to adoc files. There is not so many pages > left and you can find a report when running camel-catalog build that > output what is missing. > > This will help us with a base-line for maintaining the documentation > going forward in the source code adoc files instead of wiki, and we > can then generate a new website and documentation for the following > release (2.19 or 3.0) etc. But this is a discussion we should IMHO > take post 2.18. > Pending. Andreas have migrate a bunch more wiki pages, but we still have a few left for languages: [WARNING] Missing .adoc language documentation : 4 [WARNING] file-language [WARNING] simple-language [WARNING] xpath-language [WARNING] xquery-language And then we need to migrate all the EIP patterns. We may postpone this to post 2.18, as I would like to also get EIPs generate their options automatic as we do for components. Also we have a experiment with generate a list of the EIPs at https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc > 5) > camel-test-karaf module. This module is in the works but could use > some review and finishing so its easier to use for end users. > > Notice the existing camel-test-blueprint is still favored for doing > unit tests which you can run fast and easily debug. The new > camel-test-karaf is for running integration tests in a running karaf > instance. > Pending. Need to find time to help review and finish this. > 6) > We should look at the JIRA tickets that are assigned to 2.18.0 and try > to fix / implement them, or move them to 2.18.1 or 2.19.0 for next > releases. > Pending. > 7) > Keep an eye on the CI server to make sure the tests are green. > https://builds.apache.org/view/A-D/view/Camel/ > In general good state but the CI servers sometimes cannot build due to low memory or other jenkinis issues. > > If all goes well then hopefully in 2-3 weeks we are ready to cut the 2.18.0 > RC. > > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Getting ready for Apache Camel 2.18 Release
For the docs, I should be able to complete the languages this week. :-) -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Tuesday, September 6, 2016 1:05 PM, Claus Ibsen wrote: On Sun, Aug 28, 2016 at 11:28 AM, Claus Ibsen wrote: > Hi > > Hope everybody had good summer vacation. I had my vacation in parts > and have next week as PTO. > > We should get started to close down on the upcoming Camel 2.18 release. > > > There is some outstanding work (in no particular order) > > 1) > Finish the spring boot stuff with the starter components. > Nicola comes back from PTO and will work on this. > Still pending. > 2) > rest-dsl to support calling REST services. I am working on this and > have some outstanding work still around binding and other > improvements. > Implemented. > 3) > Tidy up the log4j v2 upgrade. Some of the examples do not start with > the jetty plugin. > Fixed. > 4) > Migrate the last wiki pages to adoc files. There is not so many pages > left and you can find a report when running camel-catalog build that > output what is missing. > > This will help us with a base-line for maintaining the documentation > going forward in the source code adoc files instead of wiki, and we > can then generate a new website and documentation for the following > release (2.19 or 3.0) etc. But this is a discussion we should IMHO > take post 2.18. > Pending. Andreas have migrate a bunch more wiki pages, but we still have a few left for languages: [WARNING] Missing .adoc language documentation : 4 [WARNING] file-language [WARNING] simple-language [WARNING] xpath-language [WARNING] xquery-language And then we need to migrate all the EIP patterns. We may postpone this to post 2.18, as I would like to also get EIPs generate their options automatic as we do for components. Also we have a experiment with generate a list of the EIPs at https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc > 5) > camel-test-karaf module. This module is in the works but could use > some review and finishing so its easier to use for end users. > > Notice the existing camel-test-blueprint is still favored for doing > unit tests which you can run fast and easily debug. The new > camel-test-karaf is for running integration tests in a running karaf > instance. > Pending. Need to find time to help review and finish this. > 6) > We should look at the JIRA tickets that are assigned to 2.18.0 and try > to fix / implement them, or move them to 2.18.1 or 2.19.0 for next > releases. > Pending. > 7) > Keep an eye on the CI server to make sure the tests are green. > https://builds.apache.org/view/A-D/view/Camel/ > In general good state but the CI servers sometimes cannot build due to low memory or other jenkinis issues. > > If all goes well then hopefully in 2-3 weeks we are ready to cut the 2.18.0 > RC. > > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Getting ready for Apache Camel 2.18 Release
Hi I added to our maven tool that it can fail the build if our component docs has problems. You can set this value to true https://github.com/apache/camel/blob/master/components/pom.xml#L286 And then do a mvn clean install -Dtest=false in the components directory. There seems to be a bunch of .adoc files which have no START .. END markers. I fixed a bunch in the start, but only got as far as to camel-dropbox to fail. We should get all these corrected as well. On Tue, Sep 6, 2016 at 1:08 PM, Andrea Cosentino wrote: > For the docs, I should be able to complete the languages this week. > > :-) > -- > Andrea Cosentino > -- > Apache Camel PMC Member > Apache Karaf Committer > Apache Servicemix Committer > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > On Tuesday, September 6, 2016 1:05 PM, Claus Ibsen > wrote: > On Sun, Aug 28, 2016 at 11:28 AM, Claus Ibsen wrote: >> Hi >> >> Hope everybody had good summer vacation. I had my vacation in parts >> and have next week as PTO. >> >> We should get started to close down on the upcoming Camel 2.18 release. >> >> >> There is some outstanding work (in no particular order) >> >> 1) >> Finish the spring boot stuff with the starter components. >> Nicola comes back from PTO and will work on this. >> > > Still pending. > >> 2) >> rest-dsl to support calling REST services. I am working on this and >> have some outstanding work still around binding and other >> improvements. >> > > Implemented. > >> 3) >> Tidy up the log4j v2 upgrade. Some of the examples do not start with >> the jetty plugin. >> > > Fixed. > >> 4) >> Migrate the last wiki pages to adoc files. There is not so many pages >> left and you can find a report when running camel-catalog build that >> output what is missing. >> >> This will help us with a base-line for maintaining the documentation >> going forward in the source code adoc files instead of wiki, and we >> can then generate a new website and documentation for the following >> release (2.19 or 3.0) etc. But this is a discussion we should IMHO >> take post 2.18. >> > > Pending. > > Andreas have migrate a bunch more wiki pages, but we still have a few > left for languages: > > [WARNING] Missing .adoc language documentation : 4 > [WARNING] file-language > [WARNING] simple-language > [WARNING] xpath-language > [WARNING] xquery-language > > > And then we need to migrate all the EIP patterns. We may postpone this > to post 2.18, as I would like to also get EIPs generate their options > automatic as we do for components. > > Also we have a experiment with generate a list of the EIPs at > https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc > > >> 5) >> camel-test-karaf module. This module is in the works but could use >> some review and finishing so its easier to use for end users. >> >> Notice the existing camel-test-blueprint is still favored for doing >> unit tests which you can run fast and easily debug. The new >> camel-test-karaf is for running integration tests in a running karaf >> instance. >> > > Pending. Need to find time to help review and finish this. > > >> 6) >> We should look at the JIRA tickets that are assigned to 2.18.0 and try >> to fix / implement them, or move them to 2.18.1 or 2.19.0 for next >> releases. >> > > Pending. > >> 7) >> Keep an eye on the CI server to make sure the tests are green. >> https://builds.apache.org/view/A-D/view/Camel/ >> > > In general good state but the CI servers sometimes cannot build due to > low memory or other jenkinis issues. > >> >> If all goes well then hopefully in 2-3 weeks we are ready to cut the 2.18.0 >> RC. >> >> >> >> >> -- >> Claus Ibsen >> - >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 > > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Java8 DSL (CAMEL-7831)
Hello everyone, I've started working on CAMEL-7831 to create a Java8 example to use Expressions and I've ended up with a simple example - see [1]. Of course it is only for demonstrative purpose. Java8 lambda support to Expressions has been added to - ExpressionClause to avoid adding overload method for every method accepting an Expressions definition - ExpressionBuilder so you can use something like transform(function(e -> ...)) There are some additional functional interfaces to select the argument of the lambda - ExchangeFunction - MessageFunction - BodyFunction Any feedback would be really appreciated. Regards, Luca [1] https://github.com/lburgazzoli/apache-camel/blob/CAMEL-7831/examples/camel-example-dsl-java8/src/main/java/org/apache/camel/example/dsl/java8/MyRoute.java --- Luca Burgazzoli
Re: Java8 DSL (CAMEL-7831)
Oh nice, I really like the choice DSL there. On 6 September 2016 at 10:37, Luca Burgazzoli wrote: > Hello everyone, > I've started working on CAMEL-7831 to create a Java8 example to use > Expressions and I've ended up with a simple example - see [1]. > Of course it is only for demonstrative purpose. > > Java8 lambda support to Expressions has been added to > - ExpressionClause to avoid adding overload method for every method > accepting an Expressions definition > - ExpressionBuilder so you can use something like transform(function(e -> > ...)) > > There are some additional functional interfaces to select the argument > of the lambda > - ExchangeFunction > - MessageFunction > - BodyFunction > > > Any feedback would be really appreciated. > > Regards, > Luca > > > [1] https://github.com/lburgazzoli/apache-camel/blob/ > CAMEL-7831/examples/camel-example-dsl-java8/src/main/ > java/org/apache/camel/example/dsl/java8/MyRoute.java > > > --- > Luca Burgazzoli > -- Matt Sicker
[GitHub] camel pull request #1159: CAMEL-10242 - add timeout
GitHub user hqstevenson opened a pull request: https://github.com/apache/camel/pull/1159 CAMEL-10242 - add timeout You can merge this pull request into a Git repository by running: $ git pull https://github.com/hqstevenson/camel CAMEL-10242 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1159.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1159 commit 1fe263c3fc46664b58e4eec2cf099c8e3d7f1707 Author: Quinn Stevenson Date: 2016-09-06T18:11:05Z CAMEL-10242 - added support for connection timeout commit 164aa417c9bb97e2d258da22091e8d7656346be6 Author: Quinn Stevenson Date: 2016-09-06T18:13:45Z resync CAMEL-10242 with master --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Help adding logic to camel component that executes before onComplete
I would like to enhance the camel-mllp component to set a message header containing the MLLP Acknowledgement when the component is automatically generating the acknowledgment. This code would need to execute after the last element in the main route, but before any onCompletion elements are invoked, but I can’t figure out the right way to make this happen. Can someone point me in the right direction?
Re: Help adding logic to camel component that executes before onComplete
If you talk about UoW completions with Synchronization: org.apache.camel.spi.Synchronization Then you can implement Ordered, and then set the value to be HIGHEST so this one is run before the others. On Tue, Sep 6, 2016 at 9:20 PM, Quinn Stevenson wrote: > I would like to enhance the camel-mllp component to set a message header > containing the MLLP Acknowledgement when the component is automatically > generating the acknowledgment. This code would need to execute after the > last element in the main route, but before any onCompletion elements are > invoked, but I can’t figure out the right way to make this happen. > > Can someone point me in the right direction? > > -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
[GitHub] camel pull request #1159: CAMEL-10242 - add timeout
Github user hqstevenson closed the pull request at: https://github.com/apache/camel/pull/1159 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Help adding logic to camel component that executes before onComplete
Thank you for the prompt reply :-) This sounds like exactly what I need, but I’m a little unclear about how to implement it. I tried creating a UnitOfWork, adding a Synchronization, and then setting the UnitOfWork on the exchange when I create it, but my Synchronization isn’t getting called. is there another component somewhere that does something similar that I could look at? > On Sep 6, 2016, at 1:25 PM, Claus Ibsen wrote: > > If you talk about UoW completions with Synchronization: > org.apache.camel.spi.Synchronization > > Then you can implement Ordered, and then set the value to be HIGHEST > so this one is run before the others. > > > On Tue, Sep 6, 2016 at 9:20 PM, Quinn Stevenson > wrote: >> I would like to enhance the camel-mllp component to set a message header >> containing the MLLP Acknowledgement when the component is automatically >> generating the acknowledgment. This code would need to execute after the >> last element in the main route, but before any onCompletion elements are >> invoked, but I can’t figure out the right way to make this happen. >> >> Can someone point me in the right direction? >> >> > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
Re: Help adding logic to camel component that executes before onComplete
There is an addOnCompletion on the exchange you can use. Then your onCompletion can implement that interface, or extend SynchronizationAdapter On Tue, Sep 6, 2016 at 9:52 PM, Quinn Stevenson wrote: > Thank you for the prompt reply :-) > > This sounds like exactly what I need, but I’m a little unclear about how to > implement it. I tried creating a UnitOfWork, adding a Synchronization, and > then setting the UnitOfWork on the exchange when I create it, but my > Synchronization isn’t getting called. > > is there another component somewhere that does something similar that I > could look at? > > >> On Sep 6, 2016, at 1:25 PM, Claus Ibsen wrote: >> >> If you talk about UoW completions with Synchronization: >> org.apache.camel.spi.Synchronization >> >> Then you can implement Ordered, and then set the value to be HIGHEST >> so this one is run before the others. >> >> >> On Tue, Sep 6, 2016 at 9:20 PM, Quinn Stevenson >> wrote: >>> I would like to enhance the camel-mllp component to set a message header >>> containing the MLLP Acknowledgement when the component is automatically >>> generating the acknowledgment. This code would need to execute after the >>> last element in the main route, but before any onCompletion elements are >>> invoked, but I can’t figure out the right way to make this happen. >>> >>> Can someone point me in the right direction? >>> >>> >> >> >> >> -- >> Claus Ibsen >> - >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Help adding logic to camel component that executes before onComplete
I’m struggling with this, and I can’t seem to get what I’m after. I added a SynchronizationAdapter (via addOnCompletion), but the exchange passed to the onComplete portion of the route still doesn’t have the headers I’m setting in the Syncronizationadapter. I’ve tried setting the header in both the onAfterRoute and onComplete methods, but no luck. The only place that seems to work is if I add the header in the onBeforeRoute method, but I don’t have enough information at that point to set the header correctly. The other thing I’d tried previously that I thought would work was simply setting the headers in the Consumer, after it called getProcessor().process(exchange) - but that doesn’t work either. I’m not sure why that doesn’t work - I set headers before I call getProcessor().process(exchange), and they behave as I’d expect. However, anything I do to the exchange after I call getProcessor().process(exchange) doesn’t seem to have any effect? Maybe I need to do something different than just call getProcessor().process(exchange)? Somehow intercept the flow of the exchange after the last processor in the route, but before before camel does whatever it does that makes my copy of the exchange irrelevant? > On Sep 6, 2016, at 2:02 PM, Claus Ibsen wrote: > > There is an addOnCompletion on the exchange you can use. Then your > onCompletion can implement that interface, or extend > SynchronizationAdapter > > On Tue, Sep 6, 2016 at 9:52 PM, Quinn Stevenson > wrote: >> Thank you for the prompt reply :-) >> >> This sounds like exactly what I need, but I’m a little unclear about how to >> implement it. I tried creating a UnitOfWork, adding a Synchronization, and >> then setting the UnitOfWork on the exchange when I create it, but my >> Synchronization isn’t getting called. >> >> is there another component somewhere that does something similar that I >> could look at? >> >> >>> On Sep 6, 2016, at 1:25 PM, Claus Ibsen wrote: >>> >>> If you talk about UoW completions with Synchronization: >>> org.apache.camel.spi.Synchronization >>> >>> Then you can implement Ordered, and then set the value to be HIGHEST >>> so this one is run before the others. >>> >>> >>> On Tue, Sep 6, 2016 at 9:20 PM, Quinn Stevenson >>> wrote: I would like to enhance the camel-mllp component to set a message header containing the MLLP Acknowledgement when the component is automatically generating the acknowledgment. This code would need to execute after the last element in the main route, but before any onCompletion elements are invoked, but I can’t figure out the right way to make this happen. Can someone point me in the right direction? >>> >>> >>> >>> -- >>> Claus Ibsen >>> - >>> http://davsclaus.com @davsclaus >>> Camel in Action 2: https://www.manning.com/ibsen2 >> > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
Camel.trunk.notest - Build # 2866 - Failure
The Apache Jenkins build system has built Camel.trunk.notest (build #2866) Status: Failure Check console output at https://builds.apache.org/job/Camel.trunk.notest/2866/ to view the results.
