Forum Discussion

NDyukov's avatar
NDyukov
Occasional Contributor
7 years ago

Failed to update the interface: [com.eviware.soapui.impl.support.definition.support.InvalidDefiniti]

"Projects" -- "WSDL Content" - click "Reloads the definition for this interface" error occurred Failed to update the interface: [com.eviware.soapui.impl.support.definition.support.InvalidDefinition...
nmrao's avatar
nmrao
Champion Level 3
Have you tried accessing the wsdl in your browser? And see what happens.
NDyukov's avatar
NDyukov
Occasional Contributor
7 years ago

wsdl opens in the browser, and this project works for other users.

Can you fix this problem?

  • nmrao's avatar
    nmrao
    Champion Level 3
    7 years ago
    Please check if there any network issue on this particular machine.
    • NDyukov's avatar
      NDyukov
      Occasional Contributor
      7 years ago

      No, other users are running on this machine (this is Windows Server) and the same project works for them. Do I need a log to localize the problem?

      • Radford's avatar
        Radford
        Super Contributor
        7 years ago

        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 (while I found this bug in version 1.7 I haven't seen it mentioned in any of the change logs so I assume it's still there).

         

        Try looking at the HTTP log to see if it gives you any clues.