Hi Christian,
Can you send us your maven project as I do not use now GIT repo for camel
and cannot apply your patch to build the project using subversion ?
Regards,
Charles
On Fri, Apr 8, 2011 at 11:32 PM, Christian Müller <
christian.muel...@gmail.com> wrote:
> Hello Ade, Willem, Charles,
>
>
Hi,
Now i am using camel(version 2.7) in the osgi bundle, but when it started,
some problem have been catched like these:
Caused by: org.apache.camel.TypeConverterLoaderException: Failed to load
type converters because of: Cannot load type converters using OSGi bundle: 2
at
org.apache.camel
In the JCA 1.5 specification, the message activation need a
ActivationSpec and a MessageEndpointFactory, ActivationSpec is used to
provide parameters to the adapter, the parameter values are defined in
MDB's ejb-jar.xml; MessageEndpointFactory is used to create
MessageEndpoints, and the MessageEndp
I guess middleware vendors may have pull/push/buffering/all sorts of
implementation specifics. JMS API shields camel from that specifics.
So I agree with the comment that putting together a simple yet
production-like test would be a good idea.
And with "production-like" i mean
- Same JMS provider
Hello,
thanks for response but I don't understand how i can call my remote method.
Explanation:
1: Camel rounting information looks like this
from("timer://myTimer?period=3").to("bean:helloServiceBean").bean(new
SomeBean());
2: helloServiceBean is defined in a file xml called camel-context.xm
This has been fixed and will be part of the Camel 2.8 release.
-
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
--
View this messag
You need Camel 2.7 or better for SI 2.0 support.
And yes you can mix and match Camel and SI.
-
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning
You can use the timer or quartz endpoint to trigger the scheduling.
And then invoke the rmi service, and then after that the bean.
Something like:
from(timer)
.to(rmi)
.to(bean)
On Sun, Apr 10, 2011 at 8:55 AM, Filippo Balicchia wrote:
> Hello,
> I need to implement an example that Sched
On Sun, Apr 10, 2011 at 2:46 AM, vcheruvu wrote:
> Is this feature only supported for Java DSL?If not do you have an example on
> how to use onPrepare in Spring DSL?
>
As always Camel you can use any kind of DSL with Camel. So yes of
course you can use it in the XML DSL as well. There is an onPre