Forum Discussion

AndiKoll's avatar
AndiKoll
Contributor
13 years ago

refactoring of WSDL

Hello,

we have to refactor some projects because of changed WSDL definitions.
Using the refactoring feature of SoapUI some questions popped up.

We got the screen with the graphical presentation of the changes between the original WSDL and the new one.
A lot of links point to definitions in the new file which are marked as ‘not in schema.
Disconnecting the links enables us to reconnect the previous xpaths to the new ones – partly.

The following problem occurs: if a field moves to a lower level – which means in the new WSDL definition a level has been inserted – it cannot be connected to the new structure. In the screenshot attached you’ll find a field aeaBorder cannot be connected to the aeaBorder in the new WSDL because the level AreaLayout has been inserted.

Is there any solution how to link the two fields?

Request definitions and Response definitions created in some test cases get lost after finishing the refactoring process.
Because we have a lot of test cases (about 400) we shall to find a solution how to migrate also the test case request definitions to the new schema.

Please let me know what’s possible to migrate to the new schema without loosing request and response definitions and how to migrate properly when levels have been inserted in the new schema.

Thanks in advance

Greetings
Andi Kollenbach

4 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    Hi,

    Unfortunately the refactoring functionality does not currently support moving of elements up/down the document structure - I'll add a feature request for this internally.

    Regarding the loss of request/response definitions - this sounds like a bug - could you provide us with a sample project and WSDL to refactor from so we can try to reproduce?

    thanks!

    /Ole
    SmartBear Software
    • ecsmmek's avatar
      ecsmmek
      Occasional Contributor
      11 years ago

      Hello Ole,

       

      It has been a while since you posted this reply.

       

      Has there been any progress in the support of refactoring where elements have been moved up/down the document structure?

       

      Currently running Ready! API version 1.2.2 and I feel this might become an issue for us in the near future if it is not improved.

       

      Best regards

      Mathias

       

       

      • sqetransunion's avatar
        sqetransunion
        Occasional Visitor
        11 years ago

        This has been a major struggle several times for our organization. We requested this about 1.5 years ago and were basically told they were not going to support this. Which is sad because this costs our organization quite a bit of money to fix when a WSDL definition changes. That said it is like pulling teeth to get SmartBear to actually fix something in a timely manner. It is equally difficult to get your fixes in something other than a nightly or SNAPSHOT build. I have been waiting several months for features they fixed in a build they gave me to actually be released to the public. It could have went in 1.2.1 or 1.2.2 but did it? Nope. They said 1.3 but would not tell me when that is going to be released. Well today is finally the day it is released. We shall see if my fixes are in there.

         

        Moral of the story. Don't hold your breath.

  • AndiKoll's avatar
    AndiKoll
    Contributor
    13 years ago
    Hi,

    thanks for raising the feature request.
    Because of a pending, not yet signed NDA I am not allowed to send any project specific information at the moment.
    I will come back ASAP.

    Greetings