Can you please provide us the java stack trace as a gist file ?
On Fri, Nov 22, 2013 at 2:43 AM, Claire wrote:
> Hi Guru,
>
> I am newbie to apache camel. I'm now trying to test bean injection in
> spring
> using java. I used following code and it gives me error:
>
> ApplicationContext context =
Hi Guru,
I am newbie to apache camel. I'm now trying to test bean injection in spring
using java. I used following code and it gives me error:
ApplicationContext context =
new ClassPathXmlApplicationContext("routes.xml");
The error is about "The constructor ClassPathXmlAppl
Longer day than I hoped. I think a new bug was introduced this week.
Other than that I looks like we're ready for the release. I am planning
on building it tomorrow.
Claus any luck with CAMEL-6988? Please advice if it could get in this
release or not.
Hadrian
On 11/20/2013 02:23 PM, 7erry
Well, this ticket is about log statements tossed by the Log EIP (and
possibly the Log component too) carrying incorrect values for the
bundle.name and bundle.id MDC entries.
They invariably refer to the camel-core bundle, because that's where the
Logger was initialised from.
So my first attempt t
Why is it you need that ClassLoader in the first place?
On Wed, Nov 20, 2013 at 1:31 AM, Raul Kripalani wrote:
> Hey guys,
>
> To solve CAMEL-6694, I'm having to enhance the constructors of the
> CamelLogger and CamelLogProcessor to pass in either:
>
> - the ClassLoader of the Camel context (ob
Hi Claus,
I thought about that, but I don't think it'll work.
Definitely not for the CamelLogger class; and I'm 90% confident that it
won't work either for the CamelLogProcessor, as it doesn't live in the
Registry. It is constructed programmatically.
Given that route initialization/construction
Hi Johan
Any other ideas that could help solve the issue?
Thoughts welcome.
Thanks,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | t
Hi Willem,
Unfortunately this is not the case, as endpoints and EIPs are constructed
at route initialisation time. So we have no Exchange to work with.
Regards,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkri
Use bean:myBean to tell Camel its a bean. And you can also specify the method
"bean:myBean?method=myMethod"
On Thu, Nov 21, 2013 at 10:00 AM, flovansi
wrote:
> I tried and I got the exception:
>
> Caused by: org.apache.camel.NoSuchEndpointException: No endpoint could be
> found for: ref:consu
Hi,
working on a small project (https://bitbucket.org/nottrz/when) I noticed
that it's not easy to pass arguments for expression evaluation (or at least
I did not found out how).
The idea is to add a method similar to isEqualTo to perform a generic
"match" on the left part of the expression.
head
I tried and I got the exception:
Caused by: org.apache.camel.NoSuchEndpointException: No endpoint could be found
for: ref:consumerBean, please check your camel registry with id consumerBean
By looking into the code, I figured out that the bean must be an Endpoint
(which was not my case).
So
11 matches
Mail list logo
