You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Gul Onural (JIRA)" <ji...@apache.org> on 2006/12/02 22:14:20 UTC
[jira] Created: (AXIS2-1810) Cannot deploy multiple versions of the
same service
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: Bug
Components: kernel
Affects Versions: 1.1
Reporter: Gul Onural
Priority: Blocker
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Reopened: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Daniels reopened AXIS2-1810:
---------------------------------
This isn't fixed.
> Cannot deploy multiple versions of the same service
> ---------------------------------------------------
>
> Key: AXIS2-1810
> URL: https://issues.apache.org/jira/browse/AXIS2-1810
> Project: Axis 2.0 (Axis2)
> Issue Type: New Feature
> Components: kernel
> Affects Versions: 1.1
> Reporter: Gul Onural
> Assignee: 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Christopher Sahnwaldt (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12458992 ]
Christopher Sahnwaldt commented on AXIS2-1810:
----------------------------------------------
You say you want to 'deploy the same service twice without changing the service name'. But you want the two versions to be reachable under different URLs:
- http://localhost/axis2/services/v1.0/MyService
- http://localhost/axis2/services/v2.0/MyService
As you said, that's not possible with Axis2.
Glen suggests that you use URLs like this instead:
- http://localhost/axis2/services/MyService
- http://localhost/axis2/services/MyService2
This should be easy with Axis2. (Haven't tried it.)
These solutions are almost identical - in both cases, the client has to use a different URL. I'd say the latter suits your needs just as well as the former, don't you think? What can you (or your clients) do with the first solution that you cannot do with the second?
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Christopher Sahnwaldt (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Gul Onural (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12459037 ]
Gul Onural commented on AXIS2-1810:
-----------------------------------
The second version suggested below requires me to change the name of the
service for every new version of the service,
while the first version allows me to keep the service name the same but
change the "version" of the service.
Changing name of the service is literally means "introducing a new
service", rather than up-versioning it.
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Christopher Sahnwaldt (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12459783 ]
Christopher Sahnwaldt commented on AXIS2-1810:
----------------------------------------------
I didn't know that modules can be versioned. You are right, it would make sense then that services can be versioned too.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456502 ]
Glen Daniels commented on AXIS2-1810:
-------------------------------------
Hi Gul:
Why would you need two different repository directories? I'm not sure I understand your first paragraph. Can't you just have http://...services/MyService and http://...services/MyService2 in the same repo?
Unless I'm mistaken (certainly a possibility!), Axis2 does indeed have a different classloader for each .aar deployment. So your repository would look like:
axis2/
axis2.xml
services/
MyService.aar
MyService2.aar
You would put the old class in the old aar, the new class in the new aar. Both would work, both classes would be named the same, and you'd get one version at /MyService and another at /MyService2. Doesn't this get you what you want?
It seems to me that this kind of versioning problem is easy. The hard part is when you want to enable the new version to live at the SAME URL as the old one - then it needs to be able to accept old-style messages, including knowing default values for missing elements, as well as new-style messages. That is a different problem.
Another interesting versioning issue is how to let users know (via a standard WSDL or SOAP header extension) that there is a new version of the service that they might want to check out - or even that the old version will be going away on such-and-such a date/time.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Tomer Ben-David (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778794#action_12778794 ]
Tomer Ben-David commented on AXIS2-1810:
----------------------------------------
Hi John, I'm facing the same issue, Could you please tell me what you have decided to do? did you go along with what you suggested in your comment? or decided to perform something different
Thanks,
Tomer
> Cannot deploy multiple versions of the same service
> ---------------------------------------------------
>
> Key: AXIS2-1810
> URL: https://issues.apache.org/jira/browse/AXIS2-1810
> Project: Axis 2.0 (Axis2)
> Issue Type: New Feature
> Components: kernel
> Affects Versions: 1.1
> Reporter: Gul Onural
> Assignee: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456162 ]
Glen Daniels commented on AXIS2-1810:
-------------------------------------
Hi Gul:
Deepal and I are sitting here at XML2006 discussing this issue, and we're having trouble seeing what the benefit would be to having the name of the v2 service match the name of the v1 service... Why can't v2 simply be a new service?
I think we need a deeper use-case for this... can you outline precisely what you'd like to do and why? Then we can try to map it into usable Axis2 functionality from there.
Thanks!
--Glen
> 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: Bug
> Components: kernel
> Affects Versions: 1.1
> Reporter: Gul Onural
> Assigned To: Deepal Jayasinghe
> Priority: Blocker
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=all ]
Deepal Jayasinghe reassigned AXIS2-1810:
----------------------------------------
Assignee: Deepal Jayasinghe
> 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: Bug
> Components: kernel
> Affects Versions: 1.1
> Reporter: Gul Onural
> Assigned To: Deepal Jayasinghe
> Priority: Blocker
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Gul Onural (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456170 ]
Gul Onural commented on AXIS2-1810:
-----------------------------------
If you design the service upgrade strategy around the assumption of
every change in a service interface makes a new service
rather than making a new version of the same service, then :
Every time I change one parameter in one service interface then I have
to introduce a new service class which is extremely
inconvenient. I want to be able to upgrade my service rather than
introducing a brand new service when I make one non-backwards compatible
change.
If you think about cost of making every change introduce a brand new
service, I have to clone my entire service code to introduce one
parameter change. Because I have to put a new class name for the "new"
service which is different than the old service, in the services.xml.
If you provide with ability to change the location (location in the
wsdl, in the axis2 repository) of the service for the v2 service, I can
manage the continue provide service for old and new clients, by
modifying my service namespace and location in the new wsdl file.
Does this help ?
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: Bug
> Components: kernel
> Affects Versions: 1.1
> Reporter: Gul Onural
> Assigned To: Deepal Jayasinghe
> Priority: Blocker
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "John Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779162#action_12779162 ]
John Miller commented on AXIS2-1810:
------------------------------------
Tomer,
Currently under Axis, we have versioned our services by basically duplicating the WSDL and schemas into a directory that represents the new version. Then, we modify the namspace to reflect the version, i.e.: www.sample.org/v2.0/ServiceName. This has worked well. However, you can see that as the system/services grow duplication of the schemas and WSDL just creates a lot of extra code as well as if you decide to keep some of the versioned service online and need to make a change to a common schema or fixed a issue with an older schema you'll need to replicate that throughout your source tree of versioned schemas. The sample above worked as designed under Axis and provides a single source tree.
An Example...
resources/wsdl/myservice/MyService.wsdl
resources/wsdl/myservice/v1/MyService.xsd
resources/wsdl/myservice/v2/MyService.xsd
resources/xsd/common/Common.xsd
When you use wsdl2java to generate the code, it not only creates the versioned package names i.e.: org.sample.www.v1_0.myservice and org.sample.www.v2_0.myservice but it also creates a SOAPBindingImpl class for each version SOAPBindingImplV1 and SOAPBindingImplV2.
Now migrating to Axis2, this also works under Axis2 and Axis2 does handle creating Axis style code as well as it can generate a services.xml file that gives you a better handle on creating/defining classes to handle/receive the SOAP requests for a given service or service group. However, it does create different classes and class names (Axis' biggest problem). I'm trying several different approaches to handle the different classes created by codegen (Axis2) vs wsdl2java (Axis). I'm also looking at using Axis2 AXIOM functionality/Raw XML (ReceiverInOut class) and convert the messages using the TypeMapping classes under Axis in order to reuse the legacy code which can be upgraded as time permits.
Hope this helps. Please let me know what you find/discover via your development.and testing.
John
> Cannot deploy multiple versions of the same service
> ---------------------------------------------------
>
> Key: AXIS2-1810
> URL: https://issues.apache.org/jira/browse/AXIS2-1810
> Project: Axis 2.0 (Axis2)
> Issue Type: New Feature
> Components: kernel
> Affects Versions: 1.1
> Reporter: Gul Onural
> Assignee: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-1810.
--------------------------------------
Resolution: Fixed
Once we have the OSGI support , then we can easily support this.
> Cannot deploy multiple versions of the same service
> ---------------------------------------------------
>
> Key: AXIS2-1810
> URL: https://issues.apache.org/jira/browse/AXIS2-1810
> Project: Axis 2.0 (Axis2)
> Issue Type: New Feature
> Components: kernel
> Affects Versions: 1.1
> Reporter: Gul Onural
> Assignee: 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-1810) Cannot deploy multiple versions of the
same service
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=all ]
Glen Daniels updated AXIS2-1810:
--------------------------------
Issue Type: New Feature (was: Bug)
Priority: Major (was: Blocker)
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "John Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768296#action_12768296 ]
John Miller commented on AXIS2-1810:
------------------------------------
I going through the same issue right now. Currently, we are upgrading from Axis 1.x to Axis 2.x and are facing issues with schema and wsdl changes/versioning changes during this upgrade due to additional requirements from our clients.
I understand what Gul is asking. I tried to handle this by making modifications to our WSDL files to include 2 different ports (see below) under the Service element as well as 2 different binding elements. This allows me to use the same operation names and gives me the ability to point these to a specific schema version. The autogenerate code works as desired as well as generating separate package names per version. However, this also generates 2 soap binding implementations i.e.: SOAPBindingImplV4.java and SOAPBindingImplV5.java. Now, I need to either create a separate request/response handling class or duplicate code in each soap binding impl class. Neither is really desirable.
My question, is there a better method to this madness? What is the industry standard or Axis's methodology/architecture to accompolish/tackle this type of verioning issue? Would a global handler that intercepts all incoming and outgoing messages work better from an architecture standpoint? If so, what code or framework is available under Axis 2.x? Does the Axis team have any examples that would so this type of architect/code samples?
================================== MyWsdl File ====================================
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://example/platforms"
xmlns:v5="http://example/v5.0/platforms"
xmlns:v4="http://example/v4.0/platforms"
xmlns:ns="http://example/v4.0/common"
xmlns:ns1="http://example/v4.0/error"
targetNamespace="http://example/platforms" name="Platforms">
<types>
<xs:schema targetNamespace="http://example/v5.0/platforms">
<xs:include schemaLocation="v5/Platforms.xsd"/>
</xs:schema>
<xs:schema targetNamespace="http://example/v4.0/platforms">
<xs:include schemaLocation="v4/Platforms.xsd"/>
</xs:schema>
</types>
<message name="PlatformSummaryRequestMessage">
<part name="request" element="v5:PlatformSummaryRequest"/>
</message>
<message name="PlatformSummaryResponseMessage">
<part name="request" element="v5:PlatformSummaryResponse"/>
</message>
<message name="ShipQueryRequestMessage">
<part name="request" element="v5:ShipQueryRequest"/>
</message>
<message name="ShipQueryResponseMessage">
<part name="request" element="v5:ShipQueryResponse"/>
</message>
<message name="PlatformModRequestMessage">
<part name="request" element="v5:PlatformModRequest"/>
</message>
<message name="PlatformModResponseMessage">
<part name="request" element="v5:PlatformModResponse"/>
</message>
<portType name="PlatformsPortTypeV5">
<operation name="PlatformSummaryRequestOperation">
<input message="tns:PlatformSummaryRequestMessage"/>
<output message="tns:PlatformSummaryResponseMessage"/>
</operation>
<operation name="ShipQueryRequestOperation">
<input message="tns:ShipQueryRequestMessage"/>
<output message="tns:ShipQueryResponseMessage"/>
</operation>
<operation name="PlatformModRequestOperation">
<input message="tns:PlatformModRequestMessage"/>
<output message="tns:PlatformModResponseMessage"/>
</operation>
</portType>
<portType name="PlatformsPortTypeV4">
<operation name="PlatformSummaryRequestOperation">
<input message="tns:PlatformSummaryRequestMessage"/>
<output message="tns:PlatformSummaryResponseMessage"/>
</operation>
<operation name="ShipQueryRequestOperation">
<input message="tns:ShipQueryRequestMessage"/>
<output message="tns:ShipQueryResponseMessage"/>
</operation>
<operation name="PlatformModRequestOperation">
<input message="tns:PlatformModRequestMessage"/>
<output message="tns:PlatformModResponseMessage"/>
</operation>
</portType>
<binding name="PlatformsSOAPBindingV5" type="tns:PlatformsPortTypeV5">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="PlatformSummaryRequestOperation">
<soap:operation soapAction="PlatformSummaryRequestOperationAction/v5"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="ShipQueryRequestOperation">
<soap:operation soapAction="ShipQueryRequestOperationAction/v5"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="PlatformModRequestOperation">
<soap:operation soapAction="PlatformModRequestOperationAction/v5"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<binding name="PlatformsSOAPBindingV4" type="tns:PlatformsPortTypeV4">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="PlatformSummaryRequestOperation">
<soap:operation soapAction="PlatformSummaryRequestOperationAction/v4"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="ShipQueryRequestOperation">
<soap:operation soapAction="ShipQueryRequestOperationAction/v4"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="PlatformModRequestOperation">
<soap:operation soapAction="PlatformModRequestOperationAction/v4"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="Platforms">
<port name="PlatformsV5" binding="tns:PlatformsSOAPBindingV5">
<soap:address location="http://localhost:8080/ws/services/Platforms/v5"/>
</port>
<port name="PlatformsV4" binding="tns:PlatformsSOAPBindingV4">
<soap:address location="http://localhost:8080/ws/services/Platforms/v4"/>
</port>
</service>
</definitions>
===================================================================================
Thanks. Any information or comment is welcome.
> Cannot deploy multiple versions of the same service
> ---------------------------------------------------
>
> Key: AXIS2-1810
> URL: https://issues.apache.org/jira/browse/AXIS2-1810
> Project: Axis 2.0 (Axis2)
> Issue Type: New Feature
> Components: kernel
> Affects Versions: 1.1
> Reporter: Gul Onural
> Assignee: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Gul Onural (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456519 ]
Gul Onural commented on AXIS2-1810:
-----------------------------------
Hi,
Currently, repository setup as following doesn't work if you want to
deploy the same service twice (without changing the service name, but
changing the aar name. I have tried it). In this case Axis2 deployment
gives you an error saying you cannot deploy a service with the same name
if the service is previously deployed.
axis2/
axis2.xml
services/
MyService.aar
MyService2.aar
I believe there is some additional work needs to be done in Axis2 to let
people to deploy two different versions of the same service,
without changing the service class name. Allowing creation of multiple
repository directories is one enabler down this path. In your example,
you still rely on changing the service name again (/MyService and
another at /MyService2). But we are talking about an ability to leave
the service name as is, but changing the location of the service EPR.
The idea again, changing the service wsdl namespace and deployment
locations but keeping the service name as is. So old clients can
continue using the old version while the new clients can get additional
capabilities by using the new version.
The old clients would use the old EPR (repository location) and old
namespace :
ServiceName = MyService
Location (target EPR) = http://localhost/axis2/services/v1.0/MyService
Wsdl namespace = http://www.mycompany.com/Namespace1
While the new clients can use the new EPR and new namespace :
ServiceName = MyService
Location (target EPR) = http://localhost/axis2/services/v2.0/MyService
Wsdl namespace = http://www.mycompany.com/Namespace2
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456443 ]
Glen Daniels commented on AXIS2-1810:
-------------------------------------
OK, so old clients use the old URL and the old .aar. New clients use the new URL and the new .aar. That sure sounds like two different services to me! :) Why can't you just deploy a new service and get exactly what you want?
The only commonality you seem to be asking for here is the service name, and I don't see the value in that - especially in that right now Axis2 uses the service name to construct the URL, which is a very convenient convention.
This certainly doesn't seem to qualify as a "blocker" in any case - it's really an enhancement request. I'm going to change the status for now, but please feel free to further flesh out specific changes you'd like to see and how they would benefit users.
> 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: Bug
> Components: kernel
> Affects Versions: 1.1
> Reporter: Gul Onural
> Assigned To: Deepal Jayasinghe
> Priority: Blocker
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Gul Onural (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Gul Onural (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12459362 ]
Gul Onural commented on AXIS2-1810:
-----------------------------------
Currently, Axis2 allows multiple versions of the same module. I am
thinking that the similar idea can be perhaps implemented for the
services.
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456185 ]
Glen Daniels commented on AXIS2-1810:
-------------------------------------
OK, here's an example. You've got:
class Service {
public String getWeather(int zipcode) { ... }
}
And you deploy this class as "weather", so http://localhost:8080/axis2/services/weather gets to it. The service gets a three day forecast as a String.
Now you want to add the ability to control how many days the returned forecast will cover, so you do:
class Service {
public String getWeather(int zipcode, int days) { ... }
}
So here is where the interesting questions start... I'm assuming you put the compiled code for Service in the weather.aar file, right? You're either going to have to REPLACE the class in that .aar with the new one, or make a new .aar file. If you do the former, then old clients are going to be missing an argument/element when they call the service with the new class. If you do the latter, then it's just a new service anyway, isn't it?
Is this the kind of thing you're talking about? We really need a detailed precise use-case to figure out the right thing (if anything) to do here.
> 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: Bug
> Components: kernel
> Affects Versions: 1.1
> Reporter: Gul Onural
> Assigned To: Deepal Jayasinghe
> Priority: Blocker
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1810) Cannot deploy multiple versions of
the same service
Posted by "Gul Onural (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456204 ]
Gul Onural commented on AXIS2-1810:
-----------------------------------
Based on your example :
- The existing system will have an weather.aar file under let say
"http://localhost/services/v1.0.0/WeatherService". This version will
have say NS1 in the weatherService.wsdl file.
- The new version of the Weather Service will be deployed under for
example : "http://localhost/services/v2.0.0/WeatherService"
We may need to change the .air file name for the new version of the
service.
Yes the two .aar files will have the same class with different
implementations and they will be deployed to different folders in axis2
service repository.
Old clients won't even know that there is a new version of the service.
They will continue to use old target EPR
(http://localhost/services/v1.0.0/WeatherService) and old namespace as
specified in the old wsdl file.
But new clients will use the new target EPR of
"http://localhost/services/v2.0.0/WeatherService".
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: Bug
> Components: kernel
> Affects Versions: 1.1
> Reporter: Gul Onural
> Assigned To: Deepal Jayasinghe
> Priority: Blocker
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org