Praveen Oruganti,
You could build a servicemix-bean component that extracts commonly XPath
expression bits and stores their value in the message headers. For
example: If a lot of your XPath expression are using the customer id,
you can store that in the headers as 'customer' and put $customer in
your CBR XPath expressions to access it. This way, you would avoid
having to evaluate XPath over and over again for comparing customer
information.
Gert
sachin2008 wrote:
Hi,
I am facing performance problems while using the EIP CBR.
I am having lots of configuration rules in the EIP CBR for example of about
280.
In my workflow i am using a CBR as the end component for checking some
specific criterias. As it is the end component in the work flow, the
amount of data coming into EIP CBR may be morethan 500KB.As it is using
xpath for condition checking , it will be parsing the complete xml.There by
the performance will get degraded.
Can anyone please help me in resolving this particular issue...
-----
Cheers
Praveen Oruganti
"Think before you act and act on what you believe"
