Forum Discussion
SmartBear_Suppo
Alumni
16 years agoHi Nico,
sorry for the delay on this; the reason for this behavior is that soapUI extracts the just the value only if there aren't any attributes; in your case there are a number of XSI-related attributes that will cause soapUI to extract them all. You could work around this by adding "/text()" to the generated XPath expression.
We could change soapUI to ignore these specific namespaces, but that would have to be optional to not break any existing usage that relies on current behavior.
Hope this helps!
regards,
/Ole
eviware.com
sorry for the delay on this; the reason for this behavior is that soapUI extracts the just the value only if there aren't any attributes; in your case there are a number of XSI-related attributes that will cause soapUI to extract them all. You could work around this by adding "/text()" to the generated XPath expression.
We could change soapUI to ignore these specific namespaces, but that would have to be optional to not break any existing usage that relies on current behavior.
Hope this helps!
regards,
/Ole
eviware.com