Surya,
Thank you for a response. I'll look into your suggestions. In the mean time
here all the the dependencies in my current pom.xml. Let me know if you
think I'm missing something I need to have to make camel-drools component
running on Apache Tomcat with Spring 3.0.7.
Thanks again !
hi,
this could generally happen due to classloading mismatch. Check if all
drools-camel dependencies libraries and camel libraries are loaded by same
class loader. there are several other dependencies that are required when
using drools, check if you have them all as well.
give it a shot and if
hi,
I would map my business/domain object to fixedlengthrecord object before
marshaling or vice versa for unmarshalling. Remember fixedlength record is
generally v flat with each field having unique start position within the
record, otherwise gets simply overwritten.
peace,
surya
--
View this me
Can someone help me with the following exception. I'm using Apache Camel
(2.10-SNAPSHOT) and Spring (3.0.7.RELEASE) with Tomcat (7.0.26).
(NOTE: I've also posted this on Stackoverflow at
http://stackoverflow.com/questions/9762861/drools-and-camel-failed-to-load-type-converters-cannot-find-any-typ
Claus
I am getting this error:
Error setting property values; nested exception is
org.springframework.beans.NotWritablePropertyException: Invalid property
'functionStartToken' of bean class
[org.apache.camel.language.simple.SimpleLanguage]: Bean property
'functionStartToken' is not writable or ha
The bytes message still contains just text. The only difference to text
messages in that case is that it needs to specify an encoding (like UTF-8).
As far as I know CXF can not handle text messages well as it internally
also uses an InputStream.
So I think it is not easy to change that and I th
I created a simple transport for my cxf jax-ws client which is backed with
jaxb bindings. I noticed that when I put the request out on the jms
transport the message body is treated as a bytes message. I wish to
decouple the data format for my messaging system, as in, there will be
services that may
well, this proved to be a "bug" of camel-netty component, I will post a fix
to camel project later on. Before that, please be careful using the
camel-netty component, especially do not use encoders/decoders not mark with
@sharable annotation, it will lead to the problem since state maybe shared
am
Hi
I assume Koseki Nonuyuki should know more about this "Japan Apache Camel
User Group":
http://camel.465427.n5.nabble.com/Is-there-any-conditions-to-launch-Camel-user-group-in-Japan-td4782527.html
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/Apache-Camel-Demonstrat
Thank you, Babak! This is great improvement I'll give it a try!
(in meanwhile I did some "dirty hack" in the CsvDataFormat class which
solves my particular problem and put it locally into my classpath as
workaround)
--
View this message in context:
http://camel.465427.n5.nabble.com/CSV-dateform
Yes. That is a big problem in the camel examples. The parent poms make
it very difficult for users to use these examples as a starting point
for their own projects or
in your case to upgrade the example.
Christian
Am 17.03.2012 23:14, schrieb gsilverman:
I see where the errant jar was introd
Thanks for the response.
But when I use spring-ws the header params are retained. why this behaviour
is differing in cxfrs?
--
View this message in context:
http://camel.465427.n5.nabble.com/CXFRS-producer-removing-JMS-headers-tp5568925p5574037.html
Sent from the Camel - Users mailing list arch
Hi
The twitter searches for Apache Camel sometimes shows tweets from the far east.
And recently there has been a fair number apparently from Japan.
However this tweet is actually a bit surprisingly
https://twitter.com/#!/asy_exe/status/181265766941868032/photo/1
Seems pretty cool to me, that peo
13 matches
Mail list logo
