I wrote below code to FTP files from remote server. I need to do FTP only one
time and get all files from remote system. But with below code, I need to
specify how much time to wait before stopping the context. Is it possible to
specify stop only after all files FTP.
{
final CamelContext camel
The Apache Jenkins build system has built Camel.trunk.notest (build #2721)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2721/
to view the results.
GitHub user sbcd90 opened a pull request:
https://github.com/apache/camel/pull/946
CAMEL-9869 Create Apache Flink Component
Hello,
This is the PR to create Apache Flink component.
You can merge this pull request into a Git repository by running:
$ git pull https://gith
Github user hqstevenson closed the pull request at:
https://github.com/apache/camel/pull/944
---
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
It was quite hard for me to get confluence styling right/cleaned up.
On 14 April 2016 at 12:46, Claus Ibsen wrote:
> Hi
>
> Okay so the good thing is that the cache is only in use if you specify
> a cacheKey, so people can then easily turn on the cache by providing a
> key.
>
> I am adding compon
On Thu, Apr 14, 2016 at 2:51 PM, Siano, Stephan wrote:
> Hi Claus,
>
> I have filed CAMEL-9868 for the Camel 3.0 changes.
>
> I will try out both options for Camel 2.x at least on a POC level and come
> back with the results. For comparing the results is it better to create a
> JIRA item for tha
Hi Claus,
I have filed CAMEL-9868 for the Camel 3.0 changes.
I will try out both options for Camel 2.x at least on a POC level and come back
with the results. For comparing the results is it better to create a JIRA item
for that or should I better post it at this list?
One question concerning
Hi
Okay removed the last one, so its all nice and clean with only master
and camel-2.xx branches for our releases. And camel-1.xx for the 1.x
releases.
On Wed, Apr 13, 2016 at 9:27 AM, Gregor Zurowski
wrote:
> Looks good to me as well. Let's remove 2.11.x, master-dev and trunk.
>
> Thanks,
> Gr
Hi
Okay so the good thing is that the cache is only in use if you specify
a cacheKey, so people can then easily turn on the cache by providing a
key.
I am adding component docs for the options that lacks those.
On Thu, Apr 14, 2016 at 11:57 AM, Bilgin Ibryam wrote:
> All changes sounds good t
Hi
Yeah both approaches are doable. But I think the first one is the
least invasive and fits 2.x the best.
On Thu, Apr 14, 2016 at 11:19 AM, Siano, Stephan wrote:
> Hi Claus,
>
> OK, I will file a JIRA task for Camel 3.0 to renovate the attachment handling
> in the message interface as we disc
All changes sounds good to me. I'd like it have default behaviour that
is expected by a Camel developer... like no caching and all the rest.
On 14 April 2016 at 10:06, Claus Ibsen wrote:
> Hi
>
> Okay done some improvements.
>
> I wonder if the caching should not be disabled by default. Its a bit
Hi Claus,
OK, I will file a JIRA task for Camel 3.0 to renovate the attachment handling
in the message interface as we discussed below.
As for the 2.18 extensions:
What exactly do you mean with "you can try using headers"?
One option would be to introduce a header (or maybe better an exchange
Hi
Okay done some improvements.
I wonder if the caching should not be disabled by default. Its a bit
annoying to have to specify a cache key for de-dups, if you are really
not using that. I am not sure I would like that enabled by default,
so I would have to disable it all the time.
Also I thin
Github user trohovsky closed the pull request at:
https://github.com/apache/camel/pull/945
---
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 en
On Sun, Apr 10, 2016 at 3:41 PM, Claus Ibsen wrote:
> Hi
>
> Maybe the endpoint can be specified as both id an uri.
> Then if you want to refer to an existing by id as it does today, you
> just use ref:
>
> runEndpoint=ref:foo
> runEndpoint=direct:foo
>
> This also allows to route to seda / jms et
On Wed, Apr 13, 2016 at 11:51 AM, Siano, Stephan wrote:
> Hi Claus,
>
> Sorry for the late reply, but I had to do some thinking about this issue (and
> was busy with other things yesterday).
>
> Having the different interfaces for Messages (without attachment) and
> Attachment Capable messages (
On Wed, Apr 13, 2016 at 8:44 PM, Walzer, Thomas
wrote:
> Hi,
>
> I tried to give the docs for recipient list
> (https://cwiki.apache.org/confluence/display/CAMEL/Recipient+List) some love.
>
> However I struggled with the following items:
> * delimiter: disabled: what does that mean?
You can spe
Hi
Just an update on some of these tasks lined
On Wed, Mar 23, 2016 at 11:07 AM, Claus Ibsen wrote:
> Hi
>
> So Camel 2.17 was the last release supporting Java 1.7.
> The next Camel 2.18 is requiring Java 1.8.
>
> Here is some thoughts of mine about this release up for discussion.
>
>
>
> a)
> I
Hi
I got some karaf features fixed that was also wrong, and some due the
spring-dm stuff. Also fixed the karaf commands and upgraded so its
working again.
The camel-spring-dm module has been merged to master branch and the
9521 branch is deleted.
On Wed, Apr 13, 2016 at 4:09 PM, Claus Ibsen wro
19 matches
Mail list logo
