Hi Asanka,
I was able to figure out the root cause for this issue.
The reason is APIM packs xalan-2.7.1.wso2v1.jar inside
CARBON_HOME/lib/endorsed directory by default and this is being used when
evaluating the above Xpath (org.apache.xpath.jaxp.XPathExpressionImpl). In
ESB, saxon9he.jar is used
Hi Asanka,
If you are using synapse specific xpath functions like get-property()
within a xpath 2.0 function you have to use them with the prefix syn.
i.e:
property xmlns:fn=http://www.w3.org/2005/xpath-functions; name=MY_VALUE
expression=fn:replace(*syn:*
Hi Sumedha,
I have tried this as well.But it also didn't work for me.
On Sun, Nov 9, 2014 at 10:30 PM, Sumedha Kodithuwakku sumed...@wso2.com
wrote:
Hi Asanka,
If you are using synapse specific xpath functions like get-property()
within a xpath 2.0 function you have to use them with the
Hi Sumedha,
With suggested configuration, I am getting below exception.
property xmlns:fn=http://www.w3.org/2005/xpath-functions; name=MY_VALUE
expression=fn:replace(syn:get-property('ERROR_URL_POSTFIX'),'\\/','/')/
2014-11-09 22:41:42,968] INFO - LogMediator STATUS = Message dispatched to
the
Hi All,
When invoke the following proxy service on ESB 481 using soapui, I am
getting the below exception.
Note: ESB runs with synapse.xpath.dom.failover.enabled=true property
Am i getting these exceptions due to any configuration issues on proxy or
is there any more configurations required on
