Has anyone had any luck using a readLock strategy other than "changed"? I've
tried them all, and "changed" seems to be the only one that works consistently
when I'm copying a large file into a directory the File Component is monitoring.
All other's allow the File Component to execute before the
Also, I assume the "map_object" bean would take CustomPOJO as the input
parameter -- correct?
-Original Message-
From: Russell, Brian [mailto:bruss...@medplus.com]
Sent: Wednesday, October 06, 2010 3:51 PM
To: users@camel.apache.org
Subject: RE: Splitter Question
Thanks Claus. I tried
Thanks Claus. I tried that also and still not working. I verified the List
coming out of my bean contains multiple CustomPOJO objects with values.
I just wanted to make sure I am approaching this the correct way.
Brian.
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.c
Hi Bruno,
I still didn't have a chance to look at it but I promise to do it this week.
One question I have is if you are using opensocial for it or some other api?
I am very curious to see if there's any oauth integration as well.
This is more certainly a cool component which opens camel to a w
On Wed, Oct 6, 2010 at 8:23 PM, Russell, Brian wrote:
> In addition to testing my clustered quartz configuration, I have the
> following question...
>
> I have a bean returning a java.util.List (see get_list
> below). I then try to use the body to route each
> CustomPOJO. See following...
>
>
Thanks Claus.
The Twitter provider is, in my concept of "done"... done.
It can produce and consume tweets.
It is easily possible to implement with EIPS, a "retweet" route.
Next on my TODO is a Camel Processor to implement the ReTweet process (which
requires some headers to be set).
Cheers,
Bru
In addition to testing my clustered quartz configuration, I have the
following question...
I have a bean returning a java.util.List (see get_list
below). I then try to use the body to route each
CustomPOJO. See following...
body
On Wed, Oct 6, 2010 at 2:57 PM, Russell, Brian wrote:
> I did get this working for a single server -- thank you.
>
> As a follow-up, how can I implement this in a singleton mode across a cluster?
>
> I need the trigger to only fire on one server in the cluster at a time.
>
This is what Quartz can
That's not currently possible afaik using camel quartz configuration. I'd have
to try that though to answer for sure.
Camel works great on cluster deployments with stateless routes. There is a bit
more work to do for stateful routes, we'll address in 3.0.
Maybe somebody on the list did that alr
On Wed, Oct 6, 2010 at 3:15 PM, Russell, Brian wrote:
> That makes sense logically in terms of what is needed, but quartz does
> this by default. In doing this in a straight quartz context, I was able
> to do this through configuration (and setting up the quartz database
> tables).
>
> Is this ty
On Wed, Oct 6, 2010 at 2:31 PM, Olivier.Roger wrote:
>
> I understand why direct: does not work now. Because it is limited to a single
> camelContext.
>
> However, could vm: be used for this use case ?
In OSGi with for example SMX / FUSE ESB you can use the nmr to pass
data between different bund
That makes sense logically in terms of what is needed, but quartz does
this by default. In doing this in a straight quartz context, I was able
to do this through configuration (and setting up the quartz database
tables).
Is this type of functionality not implemented yet in camel or do I need
to
Yes, it is fairly easy. You have to have a way though to communicate across
instances in a cluster. So you will need a processor that sets the lock and a
filter that will drop the quartz message (trigger event) if not the first.
I hope this helps.
Hadrian
On Oct 6, 2010, at 8:57 AM, Russell, B
I did get this working for a single server -- thank you.
As a follow-up, how can I implement this in a singleton mode across a cluster?
I need the trigger to only fire on one server in the cluster at a time.
I have this implemented using quartz outside of the camel context where the
clustered
I understand why direct: does not work now. Because it is limited to a single
camelContext.
However, could vm: be used for this use case ?
--
View this message in context:
http://camel.465427.n5.nabble.com/Hookpoint-Extensible-routes-tp3201249p3201305.html
Sent from the Camel - Users mailing li
Hello Camel!
I was wondering how routes could be extensible.
I thougth I could use the following idea to do it but I appears to be
otherwise:
The route I created is pretty simple: It picks up message from A, transform
it then send it to B.
I would like to make it extensible so that another rout
On Wed, Oct 6, 2010 at 9:23 AM, Charles Moulliard wrote:
> 2.2
>
Check the documentation:
http://camel.apache.org/simple
It says that you need 2.3 for OGNL support in simple language.
>
> On Wed, Oct 6, 2010 at 9:22 AM, Claus Ibsen wrote:
>> What version of Camel are you using?
>>
>> On Wed, O
2.2
On Wed, Oct 6, 2010 at 9:22 AM, Claus Ibsen wrote:
> What version of Camel are you using?
>
> On Wed, Oct 6, 2010 at 8:47 AM, Charles Moulliard
> wrote:
>> Hi,
>>
>> The following syntax works
>>
>> from(directTest)
>> .inOut(toQueue)
>> .to(log
What version of Camel are you using?
On Wed, Oct 6, 2010 at 8:47 AM, Charles Moulliard wrote:
> Hi,
>
> The following syntax works
>
> from(directTest)
> .inOut(toQueue)
> .to(logTest);
>
> from(toQueue)
> .transform().sim
19 matches
Mail list logo
