Forum Discussion
omatzura
16 years agoSuper Contributor
Hi Ali,
hm... When specifying an xpath-expression without a namespace declaration, soapUI will internally build a list of all namespaces available in the response and then assign them to sequentially generated namespace prefixes. In the process it will try to retain prefixes used in the message but there is no guarantee that this will succeed; in your case I am guessing that this algorithm is failing to assign the prefix "ns1" to your namespace for some reason, which will result in this behavior.
You are correct though, there might be room for improvement here.. if you can show the actual response message that will not work with your initial version I can check it out!
regards!
/Ole
eviware.com
hm... When specifying an xpath-expression without a namespace declaration, soapUI will internally build a list of all namespaces available in the response and then assign them to sequentially generated namespace prefixes. In the process it will try to retain prefixes used in the message but there is no guarantee that this will succeed; in your case I am guessing that this algorithm is failing to assign the prefix "ns1" to your namespace for some reason, which will result in this behavior.
You are correct though, there might be room for improvement here.. if you can show the actual response message that will not work with your initial version I can check it out!
regards!
/Ole
eviware.com