[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12459103 ] Christopher Sahnwaldt commented on AXIS2-1810: ----------------------------------------------
"change the name of the service" - you mean you have to edit the services.xml file? I don't see how you could avoid "introducing a new service" anyway. For the web service engine (Axis), the two service versions are in no way related, no matter if the URL is v2.0/MyService or MyService2. But maybe I just don't understand what you would like to achieve... I guess you want the container (Axis) handle different versions of one service. But that would be pretty hard to do. And take the example of other kinds of 'containers' that don't provide that functionality either: a Servlet engine has only one version of each Servlet; an SQL database has only one version of each table. The container is usually not the right place to handle versioning problems. > Cannot deploy multiple versions of the same service > --------------------------------------------------- > > Key: AXIS2-1810 > URL: http://issues.apache.org/jira/browse/AXIS2-1810 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: kernel > Affects Versions: 1.1 > Reporter: Gul Onural > Assigned To: Deepal Jayasinghe > > I am trying to deploy multiple versions of the same web service without > changing the name of the service and wsdl. Instead, I want to be able to do > that by changing namespace of the service in the wsdl file and location of > the service. For example : > MyService - version 1 > ================= > ServiceName = MyService > Location = http://localhost/axis2/services/v1.0/MyService > Wsdl namespace = http://www.mycompany.com/Namespace1 > MyService - version 2 > ================= > ServiceName = MyService > Location = http://localhost/axis2/services/v2.0/MyService > Wsdl namespace = http://www.mycompany.com/Namespace2 > Currently Axis2 doesn't have a mechanism to deploy multiple versions of the > same service by chaging its location and wsdl namespace. The services > repository has not been designed to accomadate multiple versions of the same > service (you can have only one service repository). > It can probably be done providing support for deploying multiple versions of > the same service similar to the mechansim provided for deploying multiple > versions of the same "module". > Gul -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
