Hi Peter,
Thanks for the info. We're using RxTx and Java Serial with camel at
the moment, but specifically sending and receiving SMS via Hayes/AT
commands. Will keep an eye on MINA.
Alex
On 29 March 2012 19:21, c031917 wrote:
> Hi Alex,
>
> no way today to collect data from serial/parallel
By the way the environment dictates currently Camel version 2.2 -
therefore I cannot using the new Aggregator2 component
On Thu, Mar 29, 2012 at 14:31, Stefan Burkard wrote:
> Hi
>
> I have to implement the following usecase:
> - messages are processed and finally delivered to a queue
> - fr
Hi
Instead of the 1st "process" unless there's more going on there, use setHeader
[1] , and instead of the 2nd "process", use header[2].
[1] http://camel.apache.org/constant.html
[2] http://camel.apache.org/header.html
Taariq
On 30 Mar 2012, at 7:52, Filippo Balicchia wrote:
> Hello All,
> I
Hi,
I have the same need with Informix db on Servicemix environmemt.
I chose DBCP because an OSGi version was available:
org.apache.servicemix.bundles
org.apache.servicemix.bundles.commons-dbcp
1.4_2
It worked nicely until now with a ConnectionFactory service.. And should work
not only on Servi
Hi,
In order to do this, you need to send an Exchange instead of body and
headers...
Please check out the code below...
Cheers,
Ashwin...
===
Exchange exchange =
context.getEndpoint("direct:exception").createExchange(ExchangePattern.I
Hi,
Have you looked into Scheduled Route Policies in Camel. These or the quartz
component should allow you to perform periodic activity using camel
routes...
http://camel.apache.org/scheduledroutepolicy.html
http://camel.apache.org/scheduledroutepolicy.html
http://camel.apache.org/simpleschedul
My idea is to use camel to decouple modules. In order to support scalability
and failover, I am wondering if the following architecture is adviced?
I have two applications with Camel embedded AppCamel1 and AppCamel2. Then I
have standalone camel nodes Camel1 and Camel2.
AppCamel1 would have a rou
Thanks for the suggestion but does not address my question of how to
instruct the mail component in a manner that does
not regard the 'headers'.
Cheers
--Filippo
Il 30 marzo 2012 10:04, Taariq Levack ha scritto:
> Hi
> Instead of the 1st "process" unless there's more going on there, use
> set
When running this program I get the message 'defaultEndpoint must be
specified'. Could you help me understand why?
Thank you!
public static void main(String args[]) throws Exception
{
// create CamelContext
CamelContext context = new DefaultCamelContext();
// add o
If you look at the JavaDoc, you will see that:
template.requestBody("seda:backend");
will send the String "seda:backend" to the default Endpoint which you
didn't specify.
You have to possible solutions:
1) set the default endpoint:
createProducerTemplate.setDefaultEndpointUri("seda:backend")
2) p
You have many possibilities. And the best solution depends on multiple
criteria:
- What's your payload?
- How big is it?
- Do you have ambitious performance requirements?
- Do you have ambitious throughput requirements?
- Do you also have to process the requests (later) if Camel1 and Camel2 is
not
It's related to this question which is already answered:
http://camel.465427.n5.nabble.com/ProducerTemplate-for-sending-mails-with-attachements-td5605511.html#a5606572
Best,
Christian
On Fri, Mar 30, 2012 at 7:06 PM, bjacob wrote:
> Hello Everyone -
>
> I'm new to Apache camel and my question m
Be aware that camel headers are not jms headers and camel properties are
not jms properties.
The producerTemplate always means camel headers and properties. You have
to consult the camel-jms component to see what camel headers
you need to set to change jms headers and properties. As far as I kn
Hello All,
I have a simple recipient list in Camel 2.8.4:
cxf:bean:someEndpoint?dataFormat=PAYLOAD&&synchronous=true
routingSlipHeader
I have my dead letter error handler set up with a redelivery policy.
However, the recipie
Please ignore this question. The error was with the bindingOperationInfo so
it was fatal to the point where it wasn't a delivery issue.
Once I fixed that, the redelivery policy works fine.
Thanks!
Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/Recipient-List-Error-H
Thank you for the response.
Now I'm able to send the request but on the server side(or consumer side), I
see a temporary queue name and not the queue name that I'm setting to
'JMSReplyTo'. Other than the output not getting pushed to the correct queue,
everything else seems to be fine.
I'm sure t
template.send() will send inOnly exchanges. What you really want to do is
template.request().
Checkout [1] and read the section about the different cases for
ExchangePattern and JMSReplyTo set or not.
[1] http://camel.apache.org/jms.html
Best,
Christian
On Fri, Mar 30, 2012 at 9:02 PM, bjacob
Hey,
Once I saw servicemix had its own bundle of the commons-dbcp. I switched it
and the thing started to work like as it should.
Much appreciated for listing out that artifact.
--
View this message in context:
http://camel.465427.n5.nabble.com/C3P0-cannot-load-Jtds-Driver-in-OSGi-env-tp56
Thanks for your answer.
I'd like to have a response as fast as possible and can afford loosing
messages.
Actually I would like to see if I can avoid activemq in the middle.
--
View this message in context:
http://camel.465427.n5.nabble.com/scalable-bus-with-multiple-Camel-instances-tp5606593p56
Thank you so much. It is working now.
--
View this message in context:
http://camel.465427.n5.nabble.com/Using-Apache-Camel-ProducerTemplate-class-to-create-a-JMS-message-with-headers-and-properties-tp5607229p5607650.html
Sent from the Camel - Users mailing list archive at Nabble.com.
On Fri, Mar 30, 2012 at 3:09 PM, Filippo Balicchia wrote:
> Thanks for the suggestion but does not address my question of how to
> instruct the mail component in a manner that does
> not regard the 'headers'.
>
The headers ought to be preserved by the mail component, as sending an
email does not
> Is it possible ?
Sure it is possible.
If you give me a little bit more details I can show you what to do.
--
View this message in context:
http://camel.465427.n5.nabble.com/extract-header-from-camel-mail-component-tp5605751p5606151.html
Sent from the Camel - Users mailing list archive at Na
On Fri, Mar 30, 2012 at 2:56 PM, Ashwin Karpe wrote:
> Hi,
>
> In order to do this, you need to send an Exchange instead of body and
> headers...
>
> Please check out the code below...
>
> Cheers,
>
> Ashwin...
>
> ===
> Exchange exchange
23 matches
Mail list logo