[ 
https://issues.apache.org/jira/browse/AXIS2-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871906#action_12871906
 ] 

Andreas Veithen commented on AXIS2-4723:
----------------------------------------

If configured both UDP and TCP (at transport level) and I get the following 
WSDL snippet (for the default Version service):

        <wsdl:port name="VersionUdpSoap11Endpoint" 
binding="ns:VersionSoap11Binding"> 
            <soap:address 
location="udp://localhost:3333/axis2/services/Version?contentType=text/xml"/> 
        </wsdl:port> 
        <wsdl:port name="VersionTcpSoap11Endpoint" 
binding="ns:VersionSoap11Binding"> 
            <soap:address location="tcp://localhost:5555"/> 
        </wsdl:port> 

For TCP, that would not be enough to dispatch to the right service.

> Make it Possible to Configure the TCP Transport at Service Level
> ----------------------------------------------------------------
>
>                 Key: AXIS2-4723
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4723
>             Project: Axis2
>          Issue Type: Improvement
>          Components: transports
>    Affects Versions: 1.5
>            Reporter: Hiranya Jayathilaka
>             Fix For: 1.6
>
>         Attachments: AXIS2-4723-update1.patch, AXIS2-4723-update2.patch, 
> AXIS2-4723.patch
>
>
> Currently the TCP transport can only be configured in the axis2.xml 
> (globally). It would be nice to be able to configure the transport at service 
> level. We can do this by using the Axis2TransportListenerEx API. (I will soon 
> attach a patch)

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

Reply via email to