Contributions
Nillable namespace issue
Hi Team, I have defined an element as Nillable in my XSD but when I am importing the WSDL in SOAP UI, the nillable namespace is not getting generated and I get the "Attribute not allowed (no wildcards allowed) : xsi:nil in element" error. I even tried by manually adding the namespace in the xsd (and I can see that it is present in the WSDL) but when imported in SOAPUI it doesn't reflect. The only solution that works is that I manually add the namespace in SOAPUI request but I cannot ask my consumers to do the same. Kindly suggest. Regards, Geeta2.6KViews0likes1CommentNillable namespace not getting added automatically
Hi Team, I have defined an element as Nillable in my XSD but when I am importing the WSDL in SOAP UI, the nillable namespace is not getting generated and I get the "Attribute not allowed (no wildcards allowed) : xsi:nil in element" error. I even triedbymanually adding the namespace in the xsd (and I can see that it is present in the WSDL) but when imported in SOAPUI it doesn't reflect. The only solution that works is that I manually add the namespace in SOAPUI request but I cannot ask my consumers to do the same. Kindly suggest. Regards, Geeta617Views0likes0CommentsRe: How do I sending null values in requests
Hi Team, I have defined the element as nillable in my XSD but when I am importing the WSDL in SOAP UI, the nillable namespace is not generated and I get theAttribute not allowed (no wildcards allowed): nil@xsi in element error. I even tried by manually adding the namespace in XSD (and I can see that it is present in WSDL) but when imported in SOAPUI, it does not reflect. The only solution that works is that I manually add the namespace in SOAP UI Request but I cannot ask my consumers to do the same. Kindly suggest. Regards, Geeta8 years agoPlace ReadyAPI QuestionsReadyAPI Questions4.3KViews0likes0Comments