Forum Discussion

robjahn's avatar
robjahn
Contributor
14 years ago

Seeking information on Updating WSDL

I need to establish a procedure for updating my SoapUI projects files following our application under test build.

Knowing what each of the options on the update of the WSDL does will save us a lot of time and ensure that we do not "mess-up" our projects.

The one-line sentence on the dialog box is for each option is some help, but is there any more information you can share or other threads you can direct me to that talk to anything more specific?
  • Hi,

    not sure what you mean here - the "Refactoring" functionality in soapUI Pro is documented at http://soapui.org/SOAP-and-WSDL/wsdl-refactoring.html, and the "Update Interface" functionality basically just replaces the WSDL in your project with the new one, optionally recreating requests for the updated schema (losing old values on the way...)

    Does this help?

    regards!

    /Ole
    SmartBear Software
  • Thanks Ole.

    This helps....but can you explain when one should use "update definition" versus "refactor definition"?

    Also, I just tried the "refactor definition" on one WSDL used in my project and I had huge list of items marked in red that require manual edits to xpath. Any way to export this for seems need to do this out-side or your wizard.

    I cut-n-pasted out of dialog box into excel. Doing a sort I can get a list of items like this using pre-fix "XPathRefactoringData XPath for ..." this is a snippet.

    XPathRefactoringData XPath for User Type XPathContainsAssertion in Step3: call GetUserProfileinfo to verify initial registation
    XPathRefactoringData XPath for User Type XPathContainsAssertion in Step5: Call GetUserProfileinfo to Verify Initial Registation
    XPathRefactoringData XPath for User Type XPathContainsAssertion in Step5: Call GetUserProfileinfo to Verify User after submission of

    But this does not let me see the xpath that I need to edit. Any suggestions?
  • Here is screen shot of the update that shows the red xpaths.

    And another question...on the refactor I see a "-->" symbol for just one of the operations. What does that mean? Its not a new operation and the wizard does not show a change. I ran the "refactor" a few times and seems to remain as an arrow.
  • Hi,

    The read XPaths / XQuery statements are those that soapUI wasn't able to update automatically for some reason - you need to check (and update) these yourself in the wizard to be in line with the new WSDL.

    this just means that the operation itself is a one-way operation, ie it only sends a request and doesn't receive a response.

    regards!

    /Ole
    SmartBear Software
  • Is there a way to configure the default input element values? currently ours get set to "?".
  • I should add that that I want the default to be <blank> not a "?". With the "?" value, its gets passed on the request thus breaking our test cases.