[
https://issues.apache.org/jira/browse/AXIS2-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488287
]
Desmond Whewell commented on AXIS2-352:
---------------------------------------
Could I ask, what does the 1.2 nightly snapshot now support with respect to
multiple ports in a service?
In short, what will the Java skeleton interface contain given the following
definition:
<service name="MYSERV">
<port name="Part1" binding="ns:Part1">
<soap:address location="http://anyema.anyprovisioningprovider.com/serv";
/>
</port>
<port name="Part2" binding="ns:Part2">
<soap:address location="http://anyema.anyprovisioningprovider.com/serv";
/>
</port>
<port name="Part3" binding="ns:Part3">
<soap:address location="http://anyema.anyprovisioningprovider.com/serv";
/>
</port>
</service>
I have tried a similar experiment with 1.2 nightly (11th Apr) and there is no
sign of multiple ports in the generated code.
> Support for multiple Services specified in WSDL
> -----------------------------------------------
>
> Key: AXIS2-352
> URL: https://issues.apache.org/jira/browse/AXIS2-352
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: codegen
> Reporter: Davanum Srinivas
> Assigned To: Amila Chinthaka Suriarachchi
> Fix For: 1.2
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
