[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456449 ] Gul Onural commented on AXIS2-1810: -----------------------------------
- First of all, currently, Axis2 doesn't allow to create 2 different service repository. For example if I want to deploy v1 of my service under http://localhost/axis2/services/v1.0/MyService and v02 of the same service under http://localhost/axis2/services/v2.0/MyService It is not possible to configure Axis to have two different repository directories. This doesn't allow me to change the location of my service from one version to another. - Second of all, It is almost impossible to maintain service code if I need to invent an new service implementation class name every time I make some changes in the Service interface. What you are suggesting is completely removing the concept of "service upgrading/up versioning". Based on your suggestion, every change in the service interface makes a new Service product, rather than a new version of the service product. Most of the time, %90 of the service interfaces stay stable between the service versions while %10 might changed. That is the reason I want to be able to use the same service name between the upgrades. About the benefit of having an up versioning strategy for the services developed using Axis2, well I would think it is an essential requirement for any commercial product developed with Axis2. Almost every commercial product needs to be "upgrade-able". Most of them even requires in service upgrades... As far as I know, currently it is possible to deploy multiple versions of a "module". Wouldn't you use similar strategy for deploying multiple versions of a service ? i.e. different class loaders perhaps ? Gul > 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]
