Hi everybody, I have a question and theory about how to handle service versioning...
As you may guess, in our project for backward .compatiblity purposes, we are offering older versions of our services up-to 6 months.... Our current way of solving this way is to created differently named artifacts in our maven structures (like service_a_v1, service_a_v2m...). I find this extremely ugly and I have another idea but I am not sure I can implement it or not (may be you can give me a better idea...) The best solution would be naturally is to provide a common endpoint and this endpoint decide itself where delegate the service implementation. Every service version naturally has another wsdl, this is actually an advantage and disadvantge... It is an advantage, while with the wsdl I can understand which implementation I have to call. It is a disadvantage, while calls to this one endpoint can't satisfy the three wsdl... So what I think, also like to ask that is possible or not, is to provide a http endpoint that is not bound to a wsdl, accepts the request and looks to the namespace of the request and redirects the message a real webservice endpoint with correct wsdl and implementation.... Do you think is it possible? Or how do you solve this versioning problem in your projects.... Thx for the answers... T-Mobile Deutschland GmbH Aufsichtsrat: Timotheus Hottges (Vorsitzender) Geschaftsfuhrung: Niek Jan van Damme (Sprecher), Thomas Berlemann, Thomas Dannenfeldt, Albert Henn, Dr. Christian P. Illek, Dr. Bruno Jacobfeuerborn, Dr. Dirk Rohweder Handelsregister: Amtsgericht Bonn, HRB 59 19 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr.: DE60800328
