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
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/
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 <
> dkulp@
> > wrote:
>>
>> On Apr 14,
On Mon, Apr 14, 2014 at 8:30 AM, Daniel Kulp wrote:
>
> On Apr 14, 2014, at 9:05 AM, Claus Ibsen 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
On Apr 14, 2014, at 9:05 AM, Claus Ibsen 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
Du
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 ena
On Mon, Apr 14, 2014 at 6:04 AM, Claus Ibsen 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 t
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 wrote:
> Fwiw, BouncyCastle 1.50 has broken OSGi metadata, see
>
