axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boyan Yurukov (JIRA)" <>
Subject [jira] Commented: (AXIS2-3172) Multiple ports in WSDL not supported
Date Fri, 18 Jan 2008 12:30:34 GMT


Boyan Yurukov commented on AXIS2-3172:

It is still not resolved. It was suggested that it is not allowed to have two wsdl ports with
the same transport type. They tell me the idea of different ports is to provide the same functionality
over different transports. I haven't found any clue in the specs, then again I haven't looked
that hard. You could try and use another binding. 

There is a hack that fixes this in adb. You need to create both skeletons and then merge services.xml
and the wsdl skeleton classes. First you copy all the methods in the same class&interface,
then you put the message receivers in different packages and make them use the same class
(the merged one). In the end you need to copy the operations from the services.xml of the
one port, into the other. For the new operations you have to specify a custom message receiver,
because the default is responsible for another port. 

It is possible to merge the message receivers, but it takes a lot of work. You need one wsdl
skeleton class, because axis requires it for the automatic wsdl generation. 

Here is an example of a merged services.xml. It is a cut down version of what I use.

    <service name="ServiceName">
            <messageReceiver mep="" class="org.neon_toolkit.registry.omv.service.lifecyclemanager.NeOnRegistryOMVCentraSiteMessageReceiverInOut"/>
        <parameter name="ServiceClass">org.neon_toolkit.registry.omv.service.NeOnRegistryOMVCentraSiteSkeleton</parameter>
        <parameter name="useOriginalwsdl">true</parameter>
        <parameter name="modifyUserWSDLPortAddress">true</parameter>
        <operation name="approveObjects" mep="">
        /* .....................................  more operations from the port this code
was generated for*/

      /*.............................this is the copied port with a custom message receiver
        <operation name="submitAdhocQuery" mep="">
			<messageReceiver mep="" class="org.neon_toolkit.registry.omv.service.querymanager.NeOnRegistryOMVCentraSiteMessageReceiverInOut"/>

> Multiple ports in WSDL not supported
> ------------------------------------
>                 Key: AXIS2-3172
>                 URL:
>             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 -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="" class=""/>
>         </messageReceivers>
>         <parameter name="ServiceClass"></parameter>
>         <parameter name="useOriginalwsdl">true</parameter>
>         <parameter name="modifyUserWSDLPortAddress">true</parameter>
>         <operation name="submitAdhocQuery" mep="">
>             <actionMapping>urn:com:my:namespace:bindings:OnePortType#submit</actionMapping>
>             <outputActionMapping></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:
For additional commands, e-mail:

View raw message