Hello,
Here is the description of my route camel : I get a message type Bytes in my
queue, I transferred this message to another broker instance in another
machine.
was receiving this message I transformed this message to CSV or XML file.
my problem is that my route works very well for XML file
For information
Version Camel = Camel V1.6.1.2
Version Activemq = Fuse message broker 5.3.0.3
Version Java = V1.6.0_16
titexe wrote:
>
> Hello,
>
> Here is the description of my route camel : I get a message type Bytes in
> my queue, I transferred this message to another broker instance in an
Hi
You are using XPath expressions
$ action = 'AAE'
And they *require* the payload to be XML.
So you cannot use XPath with CSV.
On Wed, Oct 7, 2009 at 10:59 AM, titexe wrote:
>
> For information
>
> Version Camel = Camel V1.6.1.2
> Version Activemq = Fuse message broker 5.3.0.3
> Version Jav
Firstly, thank you for your reply,
Action is a field that exists in the header of the message (Message
proportions), normally xpath ($ action = 'AAE') should not parse the message
body.
if not, it is possible to use another command that allows me to filter the
fields in the header of the message
Hi
Why do you have mixed message on that JMS queue?
Can you not have 1 queue for XML files
And another queue for CSV files?
If not I suggest to use 3 routes
1st route will consume from that JMS queue and check the message
content if its XML or CSV.
And then route to either A or B depending on t
my incoming queue, receives messages of bytes type.
the message content in bytes may be an XML or CSV or PDF file that I
converted a file in the end.
In the header of the message,there's on properties(Action), that allows me
to place this file to the proper directory.
>From where I pu
On Thu, Oct 8, 2009 at 11:22 AM, titexe wrote:
>
>
> my incoming queue, receives messages of bytes type.
>
> the message content in bytes may be an XML or CSV or PDF file that I
> converted a file in the end.
>
> In the header of the message,there's on properties(Action), that allows me
> to place
Thank you for your reply,
now I get no errors for CSV files.
cons by my filter does not work with the simple language, it puts all files
received in the same directory
below my configuration:
${in.header.Action} ==
Hi
Is there a Action header at all?
You can use the tracer to look?
http://camel.apache.org/tracer
I suspect this is the problem.
On Thu, Oct 8, 2009 at 12:49 PM, titexe wrote:
>
> Thank you for your reply,
>
> now I get no errors for CSV files.
>
> cons by my filter does not work with the si
Hi
I created an unit test that simulates your problem.
I works for me
http://svn.apache.org/viewvc?rev=823137&view=rev
On Thu, Oct 8, 2009 at 1:52 PM, Claus Ibsen wrote:
> Hi
>
> Is there a Action header at all?
>
> You can use the tracer to look?
> http://camel.apache.org/tracer
>
> I suspect
Is really a big problem, there's no place for logic:)
I enabled the trace mode, the Action field is in the header of the message,
I tried another solution, by changing the file name by adding at the end
${header.Action}
The result: I get all the files in the directory c:/CAMEL/IN/AAE with a nam
sorry the other configuration is deformed, here is the setup I used
to remember (camel version : 1.6.1, jvm version: 1.6,activemq :
fuse message broker 5.3.0.3 )
and my config camel in activemq.xml
${header.A
Hi
Ah Camel 1.x does NOT support the operators in the language.
You cannot do this in 1.x. You need Camel 2.0 for that.
In Camel 1.x you can use a POJO to do the test
On Thu, Oct 8, 2009 at 3:09 PM, titexe wrote:
>
> sorry the other configuration is deformed, here is the setup I used
you're right, the term simply does not support operators, problem solved in
version 2.0 Camel.
http://fusesource.com/issues/browse/MR-176
Otherwise, I solved the problem by using other language class message filter
as el or jxpath, it works very well with the camel version 1.6.
thank you for
14 matches
Mail list logo
