We combine namespace and the version id. We do a namespace change for
non-backwards compatible changes and a version id attribute change if
the change is backwards compatible. And we use the date pattern in the
namespace to distinguish the versions.
- Yagiz -
How about your source packages? I have found that I need to manage the endpoint classes as well. I suppose all additional properties could be omitted from the wsdl, but at some point a complete refactor may be in order. In this case, I will need to branch the source too. Package names cannot
What is the best way(s) to version SOAP applications. Since these are externally facing APIs, they must provide a reliable means for third parties to consume services. I must ensure that the wsdl that I provide will not change. However, change is inevitable. Therefore, there must be a way to
