[
https://issues.apache.org/jira/browse/AXIS2-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870701#action_12870701
]
Hiranya Jayathilaka commented on AXIS2-4723:
--------------------------------------------
> Therefore we should keep the existing unit tests.
I will look into this. Should be able to get it done without much trouble. Some
minor changes will be required anyway though since the listener impl has
changed. (TCPServer --> TCPTransportListener)
> Thus, the generated WSDL will have no EPRs for the TCP transport.
Endpoints configured at the service level show up on the WSDLs. Only the
endpoints configured at transport level do not. Does other implementations of
AbstractTransportListenerEx also suffer from this limitation, or have I done
something wrong here?
> 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.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]
