The WSDL is automatically generated by Apache's Axis when the system starts-up. As part of normal maintenance arrangements, an application instance can be restarted.

The issue here is that the order in which the services appear in the WSDL is undefined. So, although the structure of the WSDL might change from time to time, the objects and services it correctly defines do not. i.e. The WSDL is valid.

That can have undesired effects downstream, particularly if the client end has generated a checksum of the WSDL to determine if the contents has changed. Moreover, if you're reliant on the overloaded service methods and your language/stub code does not support overloading itself, you might find yourself suddenly calling a method with the wrong number or types of arguments.

If that is a problem for you, we suggest you download the WSDL and use your local copy as a reference instead.