Hi!
this isn't a bug, the problem is that the soap response contains a nested XML message inside the actual XML response, and you are trying to use xpath to query into this (string) value. You can work around this though by adding a property-transfer teststep after your soap-request (and before the jdbc request) that transfer the nested response XML to a property in your testcase, then you can use that property as the source for the assertion, in which case it will be handled as a standard XML string and you should be able to use xpath to select inside its content..
makes sense? let us know if not!
regards,
/Ole
eviware.com
