Hello Claus,
Thank you for your quick answer.
I looked into FileWatcherReloadStrategy and ReloadStrategySupport (onReloadXml)
and it should be possible for me to extend it to reload routecontext's. The
remaining point is how to connect the extended code to the camelcontext just by
using xml on
Still along those lines, the claim check comes to mind.
As you know beforehand whether the file should exist, you can indicate this
to the activemq route, along with an ID or filename etc,
That route will then check if the file has arrived or not before
proceeding, likely recheck several times as
Thanks but I don't think this is what I'm looking for. Anyone have any other
ideas?
--
View this message in context:
http://camel.465427.n5.nabble.com/Synchronizing-SFTP-and-ActiveMQ-tp5799345p5799394.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Giannis,
thank you for testing and providing logs, this is now something we can
turn into tests in order to find the best solution,
thanks :)
zoran
On Fri, May 12, 2017 at 4:26 PM, giannis_k wrote:
> I didn't use SmartLifeCycle for a particular reason, it was just a leftover
> of trying stuf
Hey Zoran,
I didn't use SmartLifeCycle for a particular reason, it was just a leftover
of trying stuff :).
As for the fix in the PR I tried it and it didn't work, I see the same
behaviour as with the workaround without the loop. Here are some logs:
16:58:32.026 [Thread-3] INFO o.a.c.m.MainSuppor
You can turn on DEBUG logging on
org.apache.camel.impl.FileWatcherReloadStrategy and see what it logs
It should be checking for and as the root tags
which is what it attempts to reload.
On Fri, May 12, 2017 at 2:43 PM, Ronny Aerts wrote:
> Hello camel community,
>
> I saw in the camel 2.19.
Hello camel community,
I saw in the camel 2.19.0 release notes that xml routes could be reloaded
automatically which woke my interest (since we only use xml routes and no java
at all). I tried it by specifying the fileWatcherDirectory in my pom.xml (in
the camel-maven-plugin configuration) and
Hi,
Thanks for the support.
I'll note for next version upgrade.
--
View this message in context:
http://camel.465427.n5.nabble.com/OnApplicationEvent-not-called-with-CamelAutoConfiguration-tp5798802p5799363.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
thank you for testing!
I think your workaround: propagating the ContextClosedEvent event to
SpringCamelContext::onApplicationEvent is quite safe and should work
fine. In the end it's how CamelContextFactoryBean does it for a long
time now, only it's not being used by the Spring Boot support in
Hi Giannis,
I don't think you need that while loop, the CamelContext::stop method
should block until CamelContext is stopped, and is there a reason you
implemented SmartLifecycle instaed of Lifeycle? I ask because we had
that discussion on the PR and came to conclusion that SmartLifecycle
in our us
Hello Zoran,
thank you for the input it was really helpful. I tried it and although I can
see that now the camel context definately shuts down first, the other beans
are still shut down before camel context is closed probably because the
shutdown of routes happen asychronously. What I ended up doi
Hi,
Tested in a test project and it seems to work.
I'll prefer not modifying SpringCamelContext class in my project.
Do you have any feedback about my workaround ? Just to know if it is "safe"
to use in production or I might encounter other problems.
--
View this message in context:
http://c
What did you try?
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Friday, May 12, 2017 8:10 AM, Pankaj Kumar wrote:
Hi All,
I'm new to camel
13 matches
Mail list logo
