Hi Bryan
thanks for your post and sorry for the delayed response. You've stumbled on to a bit of an unusual situation which soapUI obviously doesn't handle very well; the content of the out element is just a string that happens to contain XML, but soapUI tries to assert as if it were actually XML (which it isn't from a document-point-of-view). I've fixed this so that the created assertion will pass instead of fail now (ie soapUI handles the expected content as a string and not as XML).
Since the content is a string, the wildcard feature will not work inside the content of it (this only works on an element/attribute level), but the example you gave with the property-expansion should work, ie specifying an expected result as
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<GetProxyInfoResponse xmlns="http://amp.avocent.com/licensing">
<out><?xml version="1.0" encoding="UTF-8"?>
<proxyinfo address="${ProxyProperties#proxyaddress}" host="" password="*******" port="8080" requiresLogin="false" useProxy="true" userID=""/></out>
</GetProxyInfoResponse>
</soapenv:Body>
</soapenv:Envelope>
should pass provided that the referenced property contains the same value as the underlying response. If this is still not working could you please mail me your project file so I can have a more detailed look? (
ole@eviware.com)
Also, if you want to try out the fix I mentioned above, let me know and I'll make it available to you.
Sorry for this inconvenience!
regards,
/Ole
eviware.com
