Forum Discussion

lloydbax's avatar
lloydbax
New Contributor
9 years ago
Solved

Bug importing WSDL

Hi all,   .. Whilst writing this post a 'work-a-round' has been discovered...   I was wondering if anybody else has encountered this issue?    Preconditions: A WSDL pointing towards a live def...
  • nmrao's avatar
    nmrao
    9 years ago
    Hmm. ok.

    Please see if the below alternative helps:

    Access the wsdl using browser, save a local copy of the same and then import / update wsdl which should avoid (password blank ) problem.
nmrao's avatar
nmrao
Community Hero
9 years ago
Ok.
Are you stuck or do not have a workaround?
lloydbax's avatar
lloydbax
New Contributor
9 years ago

Hi nmrao,

 

I'm not stuck as the work-a-round specified above allows me to import the WSDL again.

However, the bug is not solved as I'd have to follow the work around steps every time I want to update the WSDL.

It is pretty irritating :catsad:, but as long as I save often it isn't too much of an issue.

  • nmrao's avatar
    nmrao
    Community Hero
    9 years ago
    The steps to reproduce says that exit soapui without saving.
    But I would think that you may want to save the after updating the wsdl which is ok, right?
    • lloydbax's avatar
      lloydbax
      New Contributor
      9 years ago

      Just to clarify, I specified without saving as either way (Saving or not) the same outcome is reached.

      This being, the next time the WSDL update is attempted the basic authentication windows pops up and is blank, forcing the user to end the SoapUI process in task manager. 

      • nmrao's avatar
        nmrao
        Community Hero
        9 years ago
        Hmm. ok.

        Please see if the below alternative helps:

        Access the wsdl using browser, save a local copy of the same and then import / update wsdl which should avoid (password blank ) problem.