Hi, I have been using camel aggregator 1.6 in service 3.3.1. Now servicemix
is upgraded to 3.3.2 and they have taken camel 2.2 . There were namespace
changes and compilation changes to be done; after this now the xpath filter
does not seem to be working as expected

Here is the  code snippet ( which was working perfectly in 1.6 camel-core)

Namespaces ns = new Namespaces("p", "http://nsn.com/obs/mw/medfra/snmpbc";);

from("jbi:service:http://servicemix.apache.org/test/camel-receiver";)
        .aggregate(new MyAggregationStrategy()) //camel 2
        //.aggregator(new MyAggregationStrategy()) //camel 1.6 signature
        .xpath("string(/p:snmp-getResponse/p:NE/@ipaddr)",String.class, ns)
        //.completedPredicate(header("completed").isEqualTo("true")) //camel
1.6
        .completionPredicate(header("completed").isEqualTo("true")) //camel 2

//.to("jbi:endpoint:http://servicemix.apache.org/test/file_sender_getbulk/endpoint";);
 
// 3 
        .to("log:tutorial");  

-------
And here is the incoming message

<?xml version="1.0" encoding="utf-8"?>
<p:snmp-getResponse xmlns:p="http://nsn.com/obs/mw/medfra/snmpbc";
xmlns:xsi="http://www.w3.org/2001/XMLSchema";>
  <p:NE ipaddr="11.11.12.10" />
  <p:get-response> 1.3.6.1.6.3.1.1.4.1.0
    <p:variable-bindings>
...........
------------

Thanks
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/camel-aggregator-differnce-between-camel-1-6-and-came-2-2-tp2840127p2840127.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to