Hi Tomer
Not as far as I know, what is your usecase?
Best
Souciance
On Thu, Sep 8, 2016 at 8:39 AM, Tomer [via Camel] <
ml-node+s465427n5787346...@n5.nabble.com> wrote:
> All,
> Is Camel support get list of files from FTP/SFTP?
>
> Thanks,
> Tomer
>
> --
> If you rep
All,
Is Camel support get list of files from FTP/SFTP?
Thanks,
Tomer
--
View this message in context:
http://camel.465427.n5.nabble.com/FTP-Get-list-files-from-FTP-SFTP-tp5787346.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hello,
I am using camel version 2.10.0.redhat-60024 ( the redhat version of the jar
) and jboss-a-mq-6.2.0.redhat-133 as my JMS provider and trying to do a
simple request reply pattern with the following two routes
*Producer side*
from(endPointUrl).routeId("2")
.setHeader
Hi,I found that the Camel Docker component does not work in the OSGi
environment unless I add the following at startup (in a Scala Object in my
case, as soon as the object is loaded then this runs).The error I get is:
java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider
org.glass
I just wanted to reach out to the Camel team to let them know the work they
have done on the Camel-BeanIO code is excellent. This allows parsing of CSV
files and errors to be handled and added to the exchange, so no records are
lost. The means users can add custom records into the exchange so work
Finally I have been able to reproduce/identify the issue.
Given that we are using a relative path to move the processed files into
once successfully ftp-ed to the destination servers:
../../../u/4gl_upload/warehouse_integration_2/trs-server/export/in_progress_bpo/201609081030/done
However, for
Hi,
camel JMS component client connects to Weblogic queue. Fuse restart
requires whenever Web logic bounced.
Jms pulls mgs from wbelogic server. Whenever weblogic bounced , JMS retry
every 5000 ms but it never connected automatically when weblogic is up. we
need to restart Fuse every-time.
Yeah it is hard one to replicate but once you do, it happens consistently.
I actually got to the bottom of this. So according to the OSGi spec, the
"entries" inside a bundle are returned in the order they were originally
attached:
https://osgi.org/javadoc/r4v43/core/org/osgi/framework/Bundle.html#
Hi All
Having an issue with Camel context shutdown taking much longer than expected.
The trace below shows it quite well.
There's 2 seconds "graceful" shutdown, but then it takes 2x10 seconds to
"really" shutdown.
Any ideas why that could be? Also, how can I reduce the 10 seconds termination
time
Hi,
I have a CXF route and I noticed that we're able to stop the route by
executing
the stop method through CamelContext.
I'm trying to see whether I can leverage on this feature to switch my system
into maintenance mode, and reject all the incoming requests. It works fine,
but the error message
As Chris said tthe splitter can work well if this is a simple file. Are
all new records starting with EEASTDE? If so then a splitter with
tokenize("\n") would cut every single line and send it down the Camel
route. You could then have a simple handler bean like:
public class BeanBuilder {
@End
That's odd. I've never run into that problem and I have
blueprint-properties.xml in almost all my bundles. Are your blueprint files
all in the bundles? Also I have run into problems with the cm-property
place holder name creating problems if the PID has character it doesn't
expect. I think "-" c
Thanks for all your responses. I am looking at the BeanIO data format and
will get back on this in a day or two.
--
View this message in context:
http://camel.465427.n5.nabble.com/Unmarshal-fixed-length-Binary-data-tp5787125p5787306.html
Sent from the Camel - Users mailing list archive at Nabbl
Yep, I have all those changes in my version of camel-test-blueprint. But
anyway I think I narrowed down the problem.
It has nothing to do with Gradle vs. Maven. I have replicated it in both.
Also the directory path matters but it is not as simple as more or fewer
than 6.
Basically this is a sympt
14 matches
Mail list logo
