The question is more what MEP does the remote server use.
The choices you exposed seem to imply that the remote server would return
incoming files, which would be an InOut.
However, an ftp server or file system (an smtp server as well) use an InOnly
pattern (on the producer side) so there is no
Hi guys,
Thanks for your responses.
I realise that Camel is not an IoC container, but it might be a useful
feature for Camel's classes to "lend themselves" to becoming auto injectable
in a standardised way i.e. by following JSR-330.
What'd think?
Kind regards,
Christopher
--
View this message
Bruno,
I couldn't find the code/jar/doc for the camel-oftp component. Odds are
interested users won't either (easily). Your blog post does not show what jars
are needed and where to find them either. Did I miss it?
Could you please provide directed links?
Thanks
Hadrian
On Sep 21, 2010, at 3
Hi Bruno
That is great news.
I have added a link to the FTP2 component at the user stories page
https://cwiki.apache.org/confluence/display/CAMEL/User+Stories
On Tue, Sep 21, 2010 at 9:02 PM, Bruno Borges wrote:
> Hi all!
>
> Some of you might know the Odette File Transfer Protocol, also kno
On Tue, Sep 21, 2010 at 8:24 PM, Bruno Borges wrote:
> So, considering this route:
>
> from("file:/outbox").to("someRemoteServer").to("file:/home/inbox");
>
> What do you consider to be a better design:
>
> 1- a) files from outbox goes to remoteServer-producer
> b) remoteServer-producer sends
Steve and Hadrian,
Thank you for quick responses. Camel and Quickfix are promising combination
for developing apps. I am looking forward to apply your changes for
performance testing in my environment. I will share my performance results
with you guys.
Kind regards,
-Vid-
--
View this message i
Thank you Claus - I will work our team to wait for 2.5.0.
Incidentally we found that using $\ creates the problem but using $/ is a
work-around
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-specify-route-to-folder-with-in-actual-name-tp2839895p2848979.html
Sent from t
On 20/09/10 08:41, Claus Ibsen wrote:
${in.header.foo}=='yes'
You need spaces around the operators
${in.header.foo} == 'yes'
Thanks, I've checked that and you're quite right. It works
fine with the correct syntax.
--
Illtud Daniel illt
Hi all!
Some of you might know the Odette File Transfer Protocol, also know as
OFTP. My work @Neociclo aims to present it to the community and as part of
that, I'm introducing now the Camel Component for the Accord Odette, a OFTP2
Java library.
If you want to know more, please follow this link
So, considering this route:
from("file:/outbox").to("someRemoteServer").to("file:/home/inbox");
What do you consider to be a better design:
1- a) files from outbox goes to remoteServer-producer
b) remoteServer-producer sends file to remote connection
c) remoteServer-endpoint forward re
On Tue, Sep 21, 2010 at 7:17 PM, Bruno Borges wrote:
> Is this statement correct?
>
> Are all endpoint's consumers only created when Endpoint is referenced by a
> from() ?
>
consumers is created when they are needed. And from(xx) is created a
consumer on endpoint xxx.
Where as to(xxx) is created
On Tue, Sep 21, 2010 at 7:04 PM, Bruno Borges wrote:
> Isn't the endpoint associated to "oftpToUrl" supposed to createConsumer for
> this route?
>
You have
.to(oftpToUrl)
which means its a producer
>
> Cheers,
> Bruno Borges
> www.brunoborges.com.br
> +55 21 76727099
>
> "The glory of great me
Is this statement correct?
Are all endpoint's consumers only created when Endpoint is referenced by a
from() ?
Cheers,
Bruno Borges
www.brunoborges.com.br
+55 21 76727099
"The glory of great men should always be
measured by the means they have used to
acquire it."
- Francois de La Rochefoucauld
Isn't the endpoint associated to "oftpToUrl" supposed to createConsumer for
this route?
Cheers,
Bruno Borges
www.brunoborges.com.br
+55 21 76727099
"The glory of great men should always be
measured by the means they have used to
acquire it."
- Francois de La Rochefoucauld
On Tue, Sep 21, 201
In the following Java DSL route, the Endpoint we are developing does not
create a consumer.
from("file:/home/bruno/odette/
outbox")
.to(oftpToUrl)
.choice()
.when(header(OdetteEndpoint.ODETTE_DELIVERY_NOTIFICATION).isNotNull())
On Tue, Sep 21, 2010 at 3:40 PM, Willem Jiang wrote:
> Hi,
>
> Current camel doesn't support the JSR-330 out of box,
> But if you are looking for using Java code to do the route DI work you could
> take a look camel-guice[1] and camel-spring-java config [2]
>
> [1]http://camel.apache.org/guice.htm
Hi,
Current camel doesn't support the JSR-330 out of box,
But if you are looking for using Java code to do the route DI work you
could take a look camel-guice[1] and camel-spring-java config [2]
[1]http://camel.apache.org/guice.html
[2]http://camel.apache.org/spring-java-config.html
Willem
O
Actually I hope to get it in this week, in time for camel-2.5.0.
Hadrian
On Sep 21, 2010, at 7:05 AM, Stephen Bate wrote:
> Hello Vid,
>
> I'm not a Camel committer. I've made the code available to the Camel
> developers and they are reviewing it and will probably want to make a few
> changes.
Has anyone used JSR-330 annotations in place of Spring XML for configuring
Camel? If so then would you be able to report back on your experience and
perhaps point to some example usage?
I find the idea of configuring DI using JSR-330 quite attractive; in a
similar vein to Java being used to conf
Hello Vid,
I'm not a Camel committer. I've made the code available to the Camel
developers and they are reviewing it and will probably want to make a few
changes. My guess is that it will be a week or two before it's available in
the Camel trunk.
Regards,
Steve
On 9/19/10 7:19 PM, "vcheruvu"
20 matches
Mail list logo
