Re: git commit: upgrade bouncycastle from 1.49 to 1.50
Hi I just committed so we are back on 1.49 which works in OSGi and I added a note to the pom.xml about that. So we need to wait until they fix that osgi issue before we can upgrade. On Thu, Apr 10, 2014 at 2:02 PM, Guillaume Nodet gno...@apache.org wrote: Fwiw, BouncyCastle 1.50 has broken OSGi metadata, see http://www.bouncycastle.org/jira/browse/BJA-476 2014-04-10 21:40 GMT+02:00 cmuel...@apache.org: Repository: camel Updated Branches: refs/heads/master 679c81e9e - 3b61d108c upgrade bouncycastle from 1.49 to 1.50 Project: http://git-wip-us.apache.org/repos/asf/camel/repo Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/3b61d108 Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/3b61d108 Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/3b61d108 Branch: refs/heads/master Commit: 3b61d108cf18b55df7064fba6c7e93a8759b506f Parents: 679c81e Author: cmueller cmuel...@apache.org Authored: Thu Apr 10 21:40:26 2014 +0200 Committer: cmueller cmuel...@apache.org Committed: Thu Apr 10 21:40:26 2014 +0200 -- parent/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/camel/blob/3b61d108/parent/pom.xml -- diff --git a/parent/pom.xml b/parent/pom.xml index a5b87bc..19ea3a0 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -66,7 +66,7 @@ bcel-bundle-version5.2_4/bcel-bundle-version beanio-version2.0.7/beanio-version bsh-version2.0b5/bsh-version -bouncycastle-version1.49/bouncycastle-version +bouncycastle-version1.50/bouncycastle-version build-helper-maven-plugin-version1.8/build-helper-maven-plugin-version c3p0-version0.9.1.2/c3p0-version castor-bundle-version1.3.2_2/castor-bundle-version -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: git commit: upgrade bouncycastle from 1.49 to 1.50
On Mon, Apr 14, 2014 at 6:04 AM, Claus Ibsen claus.ib...@gmail.com wrote: Hi I just committed so we are back on 1.49 which works in OSGi and I added a note to the pom.xml about that. So we need to wait until they fix that osgi issue before we can upgrade. Oh I cannot push to ASF git repo. Not sure if its the wifi here in SFO or something else? davsclaus:~/workspace/camel$ git push origin fatal: Authentication failed On Thu, Apr 10, 2014 at 2:02 PM, Guillaume Nodet gno...@apache.org wrote: Fwiw, BouncyCastle 1.50 has broken OSGi metadata, see http://www.bouncycastle.org/jira/browse/BJA-476 2014-04-10 21:40 GMT+02:00 cmuel...@apache.org: Repository: camel Updated Branches: refs/heads/master 679c81e9e - 3b61d108c upgrade bouncycastle from 1.49 to 1.50 Project: http://git-wip-us.apache.org/repos/asf/camel/repo Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/3b61d108 Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/3b61d108 Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/3b61d108 Branch: refs/heads/master Commit: 3b61d108cf18b55df7064fba6c7e93a8759b506f Parents: 679c81e Author: cmueller cmuel...@apache.org Authored: Thu Apr 10 21:40:26 2014 +0200 Committer: cmueller cmuel...@apache.org Committed: Thu Apr 10 21:40:26 2014 +0200 -- parent/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/camel/blob/3b61d108/parent/pom.xml -- diff --git a/parent/pom.xml b/parent/pom.xml index a5b87bc..19ea3a0 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -66,7 +66,7 @@ bcel-bundle-version5.2_4/bcel-bundle-version beanio-version2.0.7/beanio-version bsh-version2.0b5/bsh-version -bouncycastle-version1.49/bouncycastle-version +bouncycastle-version1.50/bouncycastle-version build-helper-maven-plugin-version1.8/build-helper-maven-plugin-version c3p0-version0.9.1.2/c3p0-version castor-bundle-version1.3.2_2/castor-bundle-version -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/ -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
[GitHub] camel pull request: CAMEL-7118: Hazelcast-based Recoverable Aggreg...
Github user alexlomov closed the pull request at: https://github.com/apache/camel/pull/84 --- 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: git commit: upgrade bouncycastle from 1.49 to 1.50
On Apr 14, 2014, at 9:05 AM, Claus Ibsen claus.ib...@gmail.com wrote: Oh I cannot push to ASF git repo. Not sure if its the wifi here in SFO or something else? davsclaus:~/workspace/camel$ git push origin fatal: Authentication failed Did you reset your password via: https://id.apache.org/reset/enter Due to the heartbleed thing, they’ve required everyone to reset their password. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: git commit: upgrade bouncycastle from 1.49 to 1.50
On Mon, Apr 14, 2014 at 8:30 AM, Daniel Kulp dk...@apache.org wrote: On Apr 14, 2014, at 9:05 AM, Claus Ibsen claus.ib...@gmail.com wrote: Oh I cannot push to ASF git repo. Not sure if its the wifi here in SFO or something else? davsclaus:~/workspace/camel$ git push origin fatal: Authentication failed Did you reset your password via: https://id.apache.org/reset/enter Due to the heartbleed thing, they’ve required everyone to reset their password. No I haven't. Just received the email from ASF INFRA about it. I guess I was one of the guys not received the 1st email from infra about the pw reset. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: git commit: upgrade bouncycastle from 1.49 to 1.50
Hi I also did not receive the first mail as well but got the second one today morning. And it also seemed a bit strange to see the second mail being sent from a yahoo mail account! Babak Claus Ibsen-2 wrote On Mon, Apr 14, 2014 at 8:30 AM, Daniel Kulp lt; dkulp@ gt; wrote: On Apr 14, 2014, at 9:05 AM, Claus Ibsen lt; claus.ibsen@ gt; wrote: Oh I cannot push to ASF git repo. Not sure if its the wifi here in SFO or something else? davsclaus:~/workspace/camel$ git push origin fatal: Authentication failed Did you reset your password via: https://id.apache.org/reset/enter Due to the heartbleed thing, they’ve required everyone to reset their password. No I haven't. Just received the email from ASF INFRA about it. I guess I was one of the guys not received the 1st email from infra about the pw reset. -- Daniel Kulp dkulp@ - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com -- Claus Ibsen - Red Hat, Inc. Email: cibsen@ Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/ -- View this message in context: http://camel.465427.n5.nabble.com/Re-git-commit-upgrade-bouncycastle-from-1-49-to-1-50-tp5750080p5750221.html Sent from the Camel Development mailing list archive at Nabble.com.
[GitHub] camel pull request: Hazelcast aggregation repository
GitHub user alexlomov opened a pull request: https://github.com/apache/camel/pull/134 Hazelcast aggregation repository Camel-7118: Hazelcast-based Recoverable Aggregation Repository You can merge this pull request into a Git repository by running: $ git pull https://github.com/alexlomov/camel hazelcast-aggregation-repository Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/134.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 #134 commit faeeb925f63f087a6cd423d31be5a6e30cdf6395 Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2013-10-15T21:04:42Z Created. commit e8c3b7c78ee2c34662414c1d13f069f417361350 Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2013-10-16T10:29:05Z Persistent repository name handling updated to achieve robustness and consistency. commit a48f3fc1a0dca490774d4fa51d2d42fcce3c103b Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2013-10-20T21:07:24Z Lots of trace logging. commit f254e062c4569b392098450d122da39993f21129 Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2013-10-21T19:19:12Z Tons of javadoc. commit 6b81f29e0acc6c35b50fa3884cef911946e80252 Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2013-10-28T21:09:06Z DefaultExchageHolders introduced. commit e22a96dc9a4447a796cc059d15b1132955d56fac Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2013-10-28T21:09:57Z HazelcastAggregationRepository Constructor Tests were implemented. commit a729ce49efd16dc090be472c9f117184c128ca2e Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2013-10-28T21:10:57Z Removed unused imports and variables. commit 8612ad3e18662c1ee8913051a233f5b88a860309 Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2013-10-28T22:11:05Z useRecovery always default to true. commit 0f34fb97fe1da62d6160ebd9682e4c084a626eb1 Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2013-10-28T22:18:02Z Initial commit (test created). commit 629d60e31fd6009b9132e15b4d03d21b50c0fd57 Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2013-12-13T14:20:15Z useRecovery always default to true. commit bcdcb6485a487a5a944f21874f6098d3e34d8263 Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2014-01-03T22:30:56Z Typo fix. commit 77180f5316d8caf4e1272121a9777fef24676bbf Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2014-01-03T23:03:56Z Superclass was extracted commit 1649c23ff859b4c78a476d92657291287f25de4d Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2014-01-04T00:24:36Z More working tests. commit a9b897c6b27af8ae1a0287b18a10e8f228d2d03e Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2014-01-04T09:28:34Z Moved SumOfIntsAggregationStrategy class from inner level. commit 0fbe03e5cd209932f9faaaf31317077a566b2848 Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2014-01-04T10:03:25Z Created a test case for recoverable HazelcastAggregationRepository. commit 3c84ef285daac9a25fe6e3880ce0d6f99fa3d32f Author: Alexander Lomov alexandr.lo...@gmail.com Date: 2014-04-14T21:01:00Z Export org.apache.camel.processor.aggregate.hazelcast package. --- 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: Expected behaviour of camel-ahc component concerning headers
Hi, I have looked up some other components doing HTTP communication like camel-http4 and camel-cxf and these components do copy the headers. I also found a unit test for copying these headers, so I assume that the documented behavior is the expected one. Unfortunately this unit test contained a bug, so it didn't find the bug in the component. I created a JIRA bug (https://issues.apache.org/jira/browse/CAMEL-7363) and attached a rather trivial patch to it (one line for the test and one line for the component...). Best regards Stephan -Original Message- From: Siano, Stephan [mailto:stephan.si...@sap.com] Sent: Montag, 7. April 2014 15:17 To: dev@camel.apache.org Subject: Expected behaviour of camel-ahc component concerning headers Hi, The documentation of the camel-ahc component (http://camel.apache.org/ahc.html ) says: Message Body Camel will store the HTTP response from the external server on the OUT body. All headers from the IN message will be copied to the OUT message, so headers are preserved during routing. Additionally Camel will add the HTTP response headers as well to the OUT message headers. However this is not how it is implemented: A new (empty) DefaultMessage will be created in the DefaultAhcBinding.onStatusReceived() method by calling exchange.getOut(). Afterwards only the HTTP-Response and the incoming HTTP headers are set to the out message. I discussed this with Aki Yoshida and he believes that the implemented behavior is the correct one as otherwise request and response messages would be mixed. From my perspective both approaches make sense, however the documentation and the implementation should match. So either the line (exchange.getOut().setHeaders(exchange.getIn().getAllHeaders());) should be added to the DefaultBinding.onStatusReceived() method, or the documentation should be adapted like ... OUT body. Camel will replace the OUT message headers by the HTTP response headers, so headers are not preserved during routing. What do you think. Best regards Stephan
