On Thu, Oct 25, 2012 at 11:02 PM, Daniel Gredler
wrote:
> Hi guys,
>
> I did some testing and it does indeed appear that cold restarts do not
> cause any properties files to be reloaded by the PropertiesComponent.
> However, looking at the code, it seems to me that there is a very good
> chance th
Have you considered using the dynamic router or recipient list DSL to look
up at runtime the value of the endpoints that could change?
You could cache the properties and then "watch" the file for changes
thereon. Or you could also expose via JMX an operation to invalidate the
cache so that the nex
I have this same exact issue - have you been able to figure out a solution?
Thanks -
Hugh
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-test-blueprint-tp5720280p5721570.html
Sent from the Camel Development mailing list archive at Nabble.com.
Thanks Daniel. Comments inline.
Hadrian
On 10/25/2012 04:52 PM, Daniel Gredler wrote:
Hi Hadrian,
The description from my first email is out of date (see the later
emails), however here's our specific scenario:
We have a user-facing application deployed to a JEE container that
contains an embe
Hi guys,
I did some testing and it does indeed appear that cold restarts do not
cause any properties files to be reloaded by the PropertiesComponent.
However, looking at the code, it seems to me that there is a very good
chance that this is a bug in Camel, and not by design.
PropertiesComponent c
Hi Hadrian,
The description from my first email is out of date (see the later
emails), however here's our specific scenario:
We have a user-facing application deployed to a JEE container that
contains an embedded Camel instance to help us do some async system
integration behind the scenes. We don
> +1 for 2 x e + 1 s
I see no vetos for 2e1s ('org.apacheextras'), so I'll stage another
2.10 release candidate soon.
Thank you for all comments.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
We can discuss some ideas at ApacheCon EU (I will be there). But we have to
make sure we share the content of our discussion afterwards here at this
list.
Looking forward to meeting you there...
Best,
Christian
Sent from a mobile device
Am 25.10.2012 15:55 schrieb "Christian Ohr" :
> I would ne
Ended up on private emails. Forwarding back to the dev list.
On Thu, Oct 25, 2012 at 10:05 AM, Scott England-Sullivan
wrote:
> That would be great!
>
> I created improvement https://issues.apache.org/jira/browse/CAMEL-5743
> to track the patch and comments. Upload your patch there and I will
>
I would never dare to subvert the Camel community - in fact that's why
I started this thread here.
Christian
2012/10/25 Rob Davies :
> +1
>
>
>
> On 25 Oct 2012, at 12:44, Hadrian Zbarcea wrote:
>
>> There will be quite a few Camel committers at ACEU. Technical discussions
>> must be inclusive
Hi,
I will be at the conference and would like to join the event too if it's open.
thanks.
regards, aki
2012/9/26 Christian Müller :
> planners@ wrote yesterday:
> The conference is taking place from Monday 5th to Thursday 8th November. On
> the Monday we have hackathons, coding sprints etc, to wh
+1
On 25 Oct 2012, at 12:44, Hadrian Zbarcea wrote:
> There will be quite a few Camel committers at ACEU. Technical discussions
> must be inclusive of the community and take place on this dev@ list though.
>
> Hadrian
>
>
> On 10/25/2012 03:47 AM, Christian Ohr wrote:
>> Let me quickly sum
Could you please describe more your situation and why a cold restart
would be needed? There may be other better solutions for your problem.
Cheers,
Hadrian
On 10/19/2012 03:51 PM, Daniel Gredler wrote:
Hi guys,
I was thinking about creating a feature request, but it involves such a
fundam
There will be quite a few Camel committers at ACEU. Technical
discussions must be inclusive of the community and take place on this
dev@ list though.
Hadrian
On 10/25/2012 03:47 AM, Christian Ohr wrote:
Let me quickly summarize -
there appears to be quite some interest from the community (a
Let me quickly summarize -
there appears to be quite some interest from the community (and
apparently a number of homegrown solutions to fill the gap) and some
plans around a Message History EIP (at the bottom of
http://camel.apache.org/camel-30-roadmap.html) for a yet unscheduled
future Camel rel
15 matches
Mail list logo