Hi Raul
upgraded to 2.9.2 (and set all headers on the In message)
all works now!
thx a lot for ur help finally i see the light after 5hrs of failures :)
w/kindest regards
marco
On Sat, Sep 22, 2012 at 7:20 PM, Raul Kripalani wrote:
> Can you try with the expression ${in.header.jsonHeade
Can you try with the expression ${in.header.jsonHeader} == 'foo'?
The notation you are using is available as of Camel 2.9.2 as I mentioned in
the other thread.
Thanks,
Raúl.
Sent from a mobile device
On Sep 22, 2012 7:14 PM, "Marco Mistroni" wrote:
> Hello Raul
>i understand , but in my
Hello Raul
i understand , but in my i am routing basing on headers. i
am not really concerned with
body, only with headers.
I have now modified my processor
exchange.getIn().setHeader("jsonHeader", action);
exchange.getIn().setHeader("jsonContent", jsonData);
exc
The processor is not transferring the original IN message body to the OUT
message body, so the result is a Message with headers but with a null body.
Take a look at [1] and you should be fine.
I suggest you set the headers in the IN message, and Camel will take care
of reusing the modified IN mes
May be this FAQ entry helps:
http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
Best,
Christian
On Sat, Sep 22, 2012 at 7:16 PM, Marco Mistroni wrote:
> Hi all
> i have a camel app in which i am using a jetty route to process json
> messages. those messages are then routed
2.9.0..
but i believe camel is fine, i have something dodgy going on somewhere else
as my message does not get routed properly.
I have posted a more completed message for that :(
thanks in advance and regards
marco
On Sat, Sep 22, 2012 at 6:08 PM, Raul Kripalani wrote:
> While all keys are con
While all keys are converted to lower case as Christian suggests, your
routing rule should work because comparison also converts to lower case
IIRC.
The syntax in your expression is valid from Camel 2.9.2 onwards. What
version are you on?
- Raúl.
On Sep 22, 2012 5:20 PM, "Marco Mistroni" wrote:
It's expected. Internally we use a CaseInsensitiveMap [1].
[1]
https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/main/java/org/apache/camel/impl/DefaultMessage.java
Best,
Christian
On Sat, Sep 22, 2012 at 6:20 PM, Marco Mistroni wrote:
> Hi all
> i have a camel processor which sets
Hi all
ignore my prev message, i am doing something dodgy somewhere
camel is working fine
sorry for bothering
w/kindest regards
marco
On Sat, Sep 22, 2012 at 5:20 PM, Marco Mistroni wrote:
> Hi all
> i have a camel processor which sets a header before passing the message
> to a component
Marking the JMS component as "transacted" and giving it a reference to
the JmsTransactionManager will cause it to do JMS transactions.
On Fri, Sep 21, 2012 at 4:55 PM, mabahma wrote:
> Hello all,
>
> We are using distributed transaction in a Camel route where messages are
> sent to a JMS queue (A
Created
https://issues.apache.org/jira/browse/CAMEL-5641
and patch attached.
On Sat, Sep 22, 2012 at 7:02 AM, James Carman
wrote:
> Will do, with patch. Thanks!
>
> Sent from my iPad
>
> On Sep 22, 2012, at 2:51 AM, Claus Ibsen wrote:
>
>> On Fri, Sep 21, 2012 at 6:27 PM, James Carman
>> wro
Will do, with patch. Thanks!
Sent from my iPad
On Sep 22, 2012, at 2:51 AM, Claus Ibsen wrote:
> On Fri, Sep 21, 2012 at 6:27 PM, James Carman
> wrote:
>> According to the documentation:
>>
>> "The values must be primitives or their counter objects (such as
>> Integer, Long, Character). The
Hi Claus,
Yep - I've come around to thinking exactly as you state above, and in fact I
did get everything working fine with 'adviceWith()'.
But as I stated originally, I still think for newbies (like me!), the
following code is far more intuitive than using 'adviceWith()':
Processor emulator
On Tue, Sep 18, 2012 at 9:11 AM, Claus Ibsen wrote:
> On Tue, Sep 18, 2012 at 7:25 AM, Siano, Stephan wrote:
>> There are actually two potential usages for idempotent repositories in
>> conjunction with (S)FTP endpoints: usage in the endpoint itself or with an
>> idempotent consumer in the pipe
On Tue, Sep 18, 2012 at 3:54 PM, Claus Ibsen wrote:
> On Tue, Sep 18, 2012 at 2:08 PM, Hilde wrote:
>> Hello Claus!
>>
>> Sorry for answering late.
>>
>> Yes, I have enabled the option /throwExceptionOnConnectFailed=true/
>> Is that ok?
>>
>
> Yeah that would be needed to allow the bridge error h
On Thu, Sep 20, 2012 at 10:00 AM, pmcb55 wrote:
> Hi Claus,
>
> I don't think your idea will work for me. In my example above I did
> statically list all the query parameter combinations, but in my real code
> they are generated dynamically. So really my route looks more like:
>
> from("direct:s
Hi
If you want to use response code 500, then you can set it as a header
on the message.
message.setHeader("Response-Code", 500);
On Fri, Sep 21, 2012 at 3:40 PM, tnk wrote:
> Hello,
>
> I have the following camel context:
>
>
>
> and my FatalProcesor just throws fault defined in wsdl:
>
>
>
Hi Claus,
Thanks for your feedback. For the meantime i have implemented a temporary
solution which based on that updated Netty component in order to get a
reference to an existing Consumer object(attached to an endpoint) from
inside Producer object. Then will be able to access active channel creat
On Sat, Sep 22, 2012 at 1:10 AM, alireza wrote:
>
> Hi,
>
> I have a question in using Netty component, let me explain the scenario:
>
> 1- We have a tcp server(consumer endpoint, using netty listening on port
> 1234)
> 2- A tcp client connects to the server (port 1234)
> 3- Once tcp client is con
19 matches
Mail list logo
