Thanks for the tip, RoutePolicy or controlling the route from the
CamelContext could do the trick.
The problem that we need to solve is still in a feasibility stage but since
we have the ability to define the interface I am inclined to suggest that
the message producer will include all pending mess
JIRA ticket created:
https://issues.apache.org/jira/browse/CAMEL-5133
Den 31 mars 2012 12:56 skrev Magnus Palmér :
> Sure, I can create a JIRA ticket for it.
> Will have to set up my dev-environment properly to be able to patch it
> though.
> It is in my plan to do anyway but since I am on pater
On Sat, Mar 31, 2012 at 12:55 PM, mgiammarco wrote:
>
> Claus Ibsen-2 wrote
>>
>> Hi
>>
>> Sometimes you can also just use a bean method, and from there use the
>> ProducerTemplate to send your messages wherever you want, and you can
>> send multiple messages to X different endpoints etc. And you
Sure, I can create a JIRA ticket for it.
Will have to set up my dev-environment properly to be able to patch it
though.
It is in my plan to do anyway but since I am on paternity leave it will
take a few days since I only have a few hours every day to stuff like this.
I will migrate a legacy integra
Claus Ibsen-2 wrote
>
> Hi
>
> Sometimes you can also just use a bean method, and from there use the
> ProducerTemplate to send your messages wherever you want, and you can
> send multiple messages to X different endpoints etc. And you don't
> have to wait for replies as you can send the message
RubyTuesdayDONO wrote
>
> Mario,
>
> if you know in advance which beans will be consuming from the endpoint,
> you
> could define them statically using Multicast, without the dynamism of
> Recipient-List.
>
Thank you for your suggestions but the new requirements from my customer
implies a dy
Hi
Sometimes you can also just use a bean method, and from there use the
ProducerTemplate to send your messages wherever you want, and you can
send multiple messages to X different endpoints etc. And you don't
have to wait for replies as you can send the messages as one-way etc.
If you got the Ca
Hi
There is a usePersist option on JPA.
And check the source code of JpaProducer.
It should call merge, which ought to do an insert or update.
I suggest to check JPA documentation about the requirements for the
merge operation.
I would assume somehow you need data in your POJO that can match so
2012/3/29 Magnus Palmér :
> I can confirm, I get the same error as you do when I remove the two last
> fields at the end of the line as you did.
>
> I think this is the where it starts to get wrong:
> BindyCsvDataFormat.java
>
> 138 // Read the line
> 139 String line =
