Hi Camel users
To process arbitrary logic in my Camel routes, I use simple bean calls.
That is fine because I can test all these pieces of logic with standard
unit tests.
However, often the bean calls produce results that are saved in the message
header (if I need to save it for later) or
Hi pcana,
Is there a way smpp splitter might be discarded?
Unfortunately I'm not aware of any splitting logic within the XMPP
component. Could you elaborate this splitting term a little bit?
Sample route snippet would be helpful as well :) .
Cheers.
--
Henryk Konsek
Hi,
I did try it .. and got on the marshal part:
It looks like you are sending String to the CSV marshaller. Am I
right? You need to send CSV-friendly data to CSV formatter, like
ListMapString,String or ListListString.
BTW Code of csvReportsHandler bean would make answering your question
Hi,
I don’t think you need to use mock framework to mock the bean.
You can just write a simple bean which implement the bean’s interface to setup
the message headers and exchange properties for you camel route.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog:
Hi Stephan,
My problem arised in the route tests where I mock away the whole bean. I
can mock the method call, but I cannot add entries to the header- or
property-maps. So if the header or property entry is expected later in the
route, it fails.
Keep in mind that in tests you can send
Hi
Yeah not sure. Sounds like camel-stax could be improved to let
@XmlElement override @XmlType if both are present. Though I suggest to
dive into the docs of these annotations to make sure element is more
specialized than xml type etc, so what you do would be a valid
use-case.
If so you are
Hello Claus,
I was looking at the JIRA for this issue.
Could you please let me know on which version of camel is this fixed which
supports quartz-1.
I tried quartz 2.11.2, but this is not fixed in that.
Regards,
Manish
--
View this message in context:
We provide a hosted integration product. We'd like to replace the internals
of this product with Camel.
Users currently add processing steps to our product using Groovy via an
online editor. Our users are technical and currently have access to a rich
DSL making the scripts much shorter and more
@Henryk: Yes, that works fine for message headers, I use it a lot to pass
expected message headers. But it is not possible for Exchange properties.
@Willem: Yes, that's true. It feels a bit cumbersome, but it works.
Based on your answers, I guess there is no fundamental Camel concept I am
Hi pcana!
You have multiple options:
1) Camel provides out of the box 3 different splitter. May be one of the
others are useful for you? You can control which splitter is used by
checking the SmppSmCommand class.
2) You can provide and configure your own SmppBinding class.
3) In newer version of
Sorry, I didn't get it. Would you please elaborate it in more detail.
Do you have the issue by sending or receiving long sms?
What kind of load balancer do you use (external, the Camel load balancer
capabilities, ...)?
Best,
Christian
-
Software Integration Specialist
Apache
Hi,
Thanks for your swift answer!
Does this mean I need to manage sending messages to the DLQ from within the
route in the error handler?
If so, this means the route needs to be aware of the DLQ destination (in
stead of managing this centrally in the broker) and what happens to the
message if
Hi Christian,
We changed SmppBinding class and the solution worked for us.
We will consider upgrading to 2.12.
Thanks for the explanation that was really helpful.
pcana
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-9-0-SMPP-Splitter-tp5745315p5745362.html
Sent
Hi
We are trying to setup Master slave for ActiveMQ using camel-context. Our
current architecture is like this.
1. A camel route which subscribes to MQ topics (these MQ topics are IBM
topics).
2. This camel route then takes the message from the topic and transforms
it
3. The
Hi,
You don’t need to let the Slave run when the Master is in charge. I think you
can take a look at the camel-zookeeper[1].
[1]http://camel.apache.org/zookeeper.html#Zookeeper-ZooKeeperenabledRoutepolicy.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog:
Dear Willem Jiang,
Still I am not able to call Web Service Please help me.
Thanks in Advance.
--
View this message in context:
http://camel.465427.n5.nabble.com/SOAP-Web-service-Calling-using-camel-tp5745180p5745371.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Current camel-cxf doesn't support the JaxWsDynamicClientFactory out of box,
so you need to generate the SEI yourself before calling the service.
--
View this message in context:
http://camel.465427.n5.nabble.com/SOAP-Web-service-Calling-using-camel-tp5745180p5745372.html
Sent from the Camel -
Hi,
You can find a simple example here[1]
[1]https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/CxfProducerTest.java
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog:
18 matches
Mail list logo