Sriram,
Yes, you understand this correctly. However, note that you still need to
build a Bean SU POJO to add the information to the message headers
yourself first. Once the message headers contain cached values for some
of the XPath sub-expressions you commonly use, you can reference them
with the $-syntax you mentioned.
Regards,
Gert
Sriram83 wrote:
Hi Gert,
If I understand you correctly,
1/. We can acess message property in the Xbean?
2/. In the routing rule for the already existing CBR, instead of using the
XPATH, we can directly use the message property.
Eg: <eip:xpath-predicate xpath = (customer/number = '1203')>
Translates into
<eip:xpath-predicate xpath = ($customer = '1203')>
Is this what you are suggesting ? Is this possible ?
Regards,
Sriram
Gert Vanthienen wrote:
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"
-----
---
Gert Vanthienen
http://www.anova.be
