[
https://issues.apache.org/jira/browse/AXIS2-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547126
]
Boyan Yurukov commented on AXIS2-3172:
--------------------------------------
I don't want to create a stub here. What I need is a server side that would
support both WSDL ports. In my WSDL I have two ports with different bindings
that have different porttypes with different operations.
> Multiple ports in WSDL not supported
> ------------------------------------
>
> Key: AXIS2-3172
> URL: https://issues.apache.org/jira/browse/AXIS2-3172
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb, codegen
> Affects Versions: 1.3, 1.2
> Environment: WinXP
> Reporter: Boyan Yurukov
> Assignee: Amila Chinthaka Suriarachchi
>
> I have a wsdl with two ports in one service:
> <service name="DaService">
> <port name="OnePort" binding="tns:OneBinding">
> <soap:address location="http://localhost:28080/soap"/>
> </port>
> <port name="TwoPort" binding="tns:TwoBinding">
> <soap:address location="http://localhost:28080/soap"/>
> </port>
> </service>
> When I try to generate a service with wsdl2java I run this command:
> "%AXIS2_HOME%\bin\wsdl2java.bat" -uri DaService.wsdl -p com.my.namespace -d
> adb -s -ss -sd -ssi -ap
> However only code for the first port is generated. The wsdl in the service
> still contains both ports as it is copied from the original file, but in the
> java code there are methods only for one port. Here is the services.xml:
> <serviceGroup>
> <service name="DaService">
> <messageReceivers>
> <messageReceiver mep="http://www.w3.org/ns/wsdl/in-out";
> class="com.my.namespace.DaServiceMessageReceiverInOut"/>
> </messageReceivers>
> <parameter
> name="ServiceClass">com.my.namespace.DaServiceSkeleton</parameter>
> <parameter name="useOriginalwsdl">true</parameter>
> <parameter name="modifyUserWSDLPortAddress">true</parameter>
> <operation name="submitAdhocQuery"
> mep="http://www.w3.org/ns/wsdl/in-out";>
>
> <actionMapping>urn:com:my:namespace:bindings:OnePortType#submit</actionMapping>
>
> <outputActionMapping>urn:com.my.namespace:OnePortType:submitResponse</outputActionMapping>
> </operation>
> </service>
> </serviceGroup>
> (there may be some names and namespace inconsistencies, because I changed
> them manually for the bug report)
> What I did to make it work is generate the code for both ports and merge it.
> I edited services.xml, the skeleton, the skeleton interface and the message
> receiver so that they are all able to work with all the operations from both
> ports.
--
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]
