axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-352) Support for multiple Services specified in WSDL
Date Sun, 01 Jan 2006 23:36:02 GMT
    [ http://issues.apache.org/jira/browse/AXIS2-352?page=comments#action_12361495 ] 

Sanjiva Weerawarana commented on AXIS2-352:
-------------------------------------------

In WSDL 1.1 (which is what Axis1 deals with) a /wsdl:definitions/wsdl:service element could
have ports which come from different portTypes and different bindings. Can you explain the
rules that Axis1 uses for the case when a single <wsdl:service> contains ports bound
to different porTypes? Also, please explain the rules it uses when the WSDL contains multiple
<wsdl:service> elements, each potentially with multiple ports of different portTypes.


I'm +1 for supporting the WSDL 2.0 like scenario of one wsdl:service element containing multiple
ports all of the same portType. Going beyond that, I don't agree is a critical requirement
for 1.0. 

For the client side, we'd need something like ServiceGroupClient in addition to ServiceClient
which we have now to make the multiple clients work. Again I'm not convinced this is a critical
requirement for 1.0.

> Support for multiple Services specified in WSDL
> -----------------------------------------------
>
>          Key: AXIS2-352
>          URL: http://issues.apache.org/jira/browse/AXIS2-352
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>     Reporter: Davanum Srinivas

>
> If one runs Axis1.X's wsdl2java to generate both server and client, in the deploy.wsdd
there are entries for each of the services specified in the /wsdl:definitions/wsdl:service.
However in Axis2, we generate only 1 service in services.xml
> Secondly, Axis 1.X generates a ServiceLocator which has information on *ALL* the endpoints
and methods to access each of them. We need something similar for Axis2.

-- 
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


Mime
View raw message