Win a copy of The Way of the Web Tester: A Beginner's Guide to Automating Tests this week in the Testing forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Migrating between versions of SOAP web service

Chris Reed
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am writing a Java app that connects to a SOAP web service. I am developing in NetBeans. The owner of the web service makes updates quarterly and I was very frustrated the first time because I couldn't figure out how to update my app. I did finally figure out I had to delete the web service clients and recreate them using the update WSDL URL.

Having said all that, I'm trying to get my head around migrating this to a production Web Service. The web service owner provides a "staging" environment with the next version to develop against. Once I get ready to move to production, I have to change to the production URL. Below is the vendor's description of the two environments and their URLs. I am trying to confirm that my current process of deleting and re-adding the web service clients will work for the move to Production. I hope this is enough info to provide feedback?

Using Cloud Based Web References (This applies to Staging)

When developing, if you are adding a web reference that is cloud based (Any URL with or you must specify the version of ConnectWise when trying to visit the WSDL. You can find your version by looking at the top left of your ConnectWise instance. For example, if you are developing for the Service Ticket API and viewing the WSDL under version 2.0, the URL will be:

When you make your actual calls to the environment, you can switch the v2015_x to v4_6_release. When you pass a request that includes XML, it will route correctly and come back. If you are not passing XML, it won’t know where to route and gives a 404 error. This is designed to allow integrations to work on a variety of versions without issues.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic