The Apache Jenkins build system has built Camel.2.12.x.notest (build #68)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.12.x.notest/68/
to view the results.
Ah okay, yeah you can do from(bean) but then Camel will just keep
calling the method on the bean in endless loop, using a single
threaded consumer.
So if there is no messages on the JMS queue to process you would need
to sleep the thread or something as there is no message for Camel to
route.
You
Ideally 2.12.2 will resolve an issue that 2.12.1 introduced. We need the
ability to disable the caching of groovy that was introduced in 2.12.1 since
it fails to invoke the groovy OGNL call and thus returns dirty data.
See CAMEL-6988
7erry
--
View this message in context:
http://camel.4654
I m not sure it'll be possible with the @Consume annotation.
I want to be able to create an exchange in the POJO and to manage manually the
JMS transaction when consuming message.
If I've well understood, the @Consume annotation cannot fit in this case as we
have to specify an endpoint t
Hi
Yeah see
http://camel.apache.org/pojo-messaging-example.html
You dont need a route if you use a pojo with the @Consume annotation
as shown in that example.
On Wed, Nov 20, 2013 at 5:29 PM, flovansi wrote:
> Hi all,
>
> Is it possible to consume message from a Java bean?
>
> Something like:
Hi all,
Is it possible to consume message from a Java bean?
Something like:
where myBean could be a custom bean to get JMS message from a queue, or
anything you can think of.
I know that I can achieve that by creating custom Camel Component but a Java
Bean could be simpler in my case.
If it'
Am 20.11.13 13:37 schrieb "Babak Vahdat" unter
:
>
>
>Am 20.11.13 12:22 schrieb "Claus Ibsen" unter :
>
>>Its not really a bug, its the namespace the JAXB classes in camel-core
>>has been used since early days.
>
>Hi Claus,
>
>Thanks for your feedback!
>
>IMHO when you say "Its not really a bug"
Am 20.11.13 12:22 schrieb "Claus Ibsen" unter :
>Its not really a bug, its the namespace the JAXB classes in camel-core
>has been used since early days.
Hi Claus,
Thanks for your feedback!
IMHO when you say "Its not really a bug" then it depends whose hat you
have on. As an Apache Camel commi
Its not really a bug, its the namespace the JAXB classes in camel-core
has been used since early days.
Back then Spring was the only XML DSL supported. And its the namespace
the model classes is hardcoded to use.
In Camel 3.0 we can consider having a /core namespace instead of
/spring for the JAXB
Hi
As working on CAMEL-6985 last night I spotted a bug concerning the blueprint
based Camel apps. Following the steps to reproduce:
- Install the Twitter-Websocket-Blueprint example into the Karaf and then
make use of the 'route-info' command for it as below:
~/dev/apache-karaf-2.3.3/bin>./karaf
10 matches
Mail list logo