Steve,
The transactional EIP supports crossing multiple routes as long
as each one of those routes are transactionally aware (transaction
demarcation) and your JMS connection factory is configured properly and
set-up to use a transaction manager. I personally use camel under an OSGI
c
Hello Steve,
It seems to work for me, let me know if you want to see a sample
maven project for it. Are you sure that your "jms" component is
configured correctly and has a transactionManager set and has transacted =
true?
The sample project I created has a scheduled route that writ
Personally, I've used blueprint with OSGI, Camel for several years now -
still works just fine even with the latest version of Karaf (4.3.X -
haven't tried 4.4.1), Camel (3.18.1), and JDK 11.
On Tue, Sep 6, 2022 at 4:03 AM Bert Speckels
wrote:
> Some (all) good points Raymon
>
> I think this is
RINT with the JAVA DSL. The camel-context.xml file embedded
in the META-INF folder just bootstraps the Java DSL routebuilders. You
can bundle POJO's and standard Java code when implementing Processors etc,
the only XML file needed is that camel-context.xml.
On Tue, Sep 6, 2022 at 4:36 AM Geo
unsubscribe
On Fri, Feb 2, 2024 at 2:29 AM Jono Morris wrote:
>
> The Throttler previously employed a fixed windows algorithm, allowing a
> fixed number of calls in a particular period. This is susceptible to
> request bursts, e.g. for a limit of 100 requests/hour, all 100 requests
> might be ma
Are you using it to parse CSV files? or produce CSV files?
I suggest you use Camel-CSV instead. BIndy CSV has a couple of problems with
the first being it doesn't properly support RFC-4180 CSV files, and the second
being it uses reflection to set properties..
On Tue, Aug 27, 2019 at 12:17 AM
