Howell, David wrote: > > Hi, > > Is there a recommended or commonly used approach to versioning a > service (SOAP, doc/literal) that is to be deployed on Axis2? I’m > trying to provide some means of not breaking consumers of an existing > service if I have to deploy a new version that isn’t backwards > compatible. We’re using AXIOM / no data binding for the service > consumers and producers. > Actually we had some discussion on how to do the version support in Axis2 (for service) , but we have not implement that. So only option is to manage service yourself. > > In a lot of cases I think I’ll just want to move from deploying > MyService_V1.aar to deploying MyService_V2.aar. V1 can stay deployed > on the Axis2 server until the consumers have all moved on to V2. > > I’ve been looking at including version information in the target > namespace specified in the WSDL for the service as a mechanism for > consumers to specify which version of the service they want to use. > I’m struggling to understand what my options are for deploying the old > and new versions of my service. Specifically: > > - I don’t seem to need to deploy MyService_V1 and MyService_V2 on > different endpoint addresses, but > > - I assume I do have to give them different names in the <service> > element of the wsdl. > > Is this correct? > > Finally, is there any way of using a single endpoint and service name > that accepts requests from consumers that may have different XML > namespaces depending on the version of the service they are using? > > Thanks, > > Dave >
-- Thank you! http://blogs.deepal.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
