I'm not sure if this is relavent in your case, but in a totally different scenario I was getting a strange InvalidDefinitionException. It turns out that the functionality that adds/updates WSDL always assumes a HTTP 200 OK response and that the reply contents is a WSDLdocument, thus if ever some other response is returned e.g. HTTP 401 Unauthorised, the add/update functionality ignores it and tries to process the associated reply contents as WSDL when it is not, hence the unexpected InvalidDefinitionException. This issue was reproduced by SmartBear support and logged as defect number SOAP-5946.
Try looking at the HTTP log to see if it gives you any clues.
Hi Radford, thanks for the insight.
As I have no clue about what the problem would be, maybe might be the case. Is there any fix or workaround for this defect you shared with us?
Thanks a lot!
I'm sorry, I don't know what your specific problem is. I was just trying to highlight that it might not be an InvalidDefinitionException due to defect SOAP-5946.
I identified the root cause of my issue by examining he HTTP log within Ready API, perhaps this log will help you, good luck.
