Contributions
Invalid xsi:type qname
Hello, actually we have some problems working with Assertions in SoapUI. As a standard, we have in each request an Assertion "Schema Compliance". In some requests these assertions fail, we recieve following message: Schema Compliance - FAILED -> line 17: Invalid xsi:type qname: 'StringValue' in element Property@http://www.xxx.com/xxx/xxx In request, line 17 is: Asking developers, telling that there are no errors in our product. SoapUI use XMLBeans for SchemaCompliance. Does not work with xsi:types. Is there any chance to use Schema Compliance for our tests? Thanks in advance!16 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.1KViews0likes1CommentNamespace Definitions lost
Hello, actually we are working with SoapUI Pro for some weeks and have the more or less problems: 1) we fill-in data in xml editor, when switching to form editor data is lost. This occurs when you have a choice-element. So far as I have read this is a known problem and will fixed with next release. When will be the release available? 2) In all of our requests we need to insert the namespace definitions twice. The first time it is automatically in between at line nr. 1. After lines of Authentication we need to insert namespace definitions manually. Then test case runs and everything is ok until we switch to form editor. After this, namespace definition is lost and test fails. Why do I have to insert namespace twice and why is it lost switching editors? What am I doing wrong? Here is an example of a request: ${#Project#Tenant} ${#Project#User} ${#Project#Password} xmlns:ns1="http://www.xxx.com/xxx/xxx/1.0"> ... the bold lines have to be inserted manually. This occurs when we have choice elements. Thank you in advance vor your response.16 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes1Comment