Thanks, it was indeed a name-space problem !
I was able to fix it by using the workaround: Rest support, method body is not created from the schema
(
http://soapuiwww.eviware.com/forum/view ... 528b2ffaaf )
Now, I'm able to see my WADL Content correctly. I need those information in order to be able to have the Schema Compliance assertion available.
Unfortunately it seems that the Schema Compliance assertion is not working for WADL. I've changed the server output, and I've double check that in my WADL Content I have the correct XSD information. Still the Schema Compliance assertion is saying that the output compared with my schema is correct, when it is not the case. More details: I've changed a mandatory attribute name in the output sent from the server, or I've added in the client XSD a new mandatory attribute that the server is not sending etc.
Could you please let me know if there is any bugs open for the Schema Compliance with REST, or what could be the problem ?
Thanks,
Sorin
