[jira] Commented: (AXIS2-4723) Make it Possible to Configure the TCP Transport at Service Level

["Andreas Veithen (JIRA)" <ji...@apache.org>]

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

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

I'm a bit uneasy with the fact that you changed the test cases to set up the TCP endpoints at the service level. We need to make sure that the new version of the TCP transport still supports the scenarios that were supported by the old version (i.e. configuring the TCP endpoint at the transport level). Therefore we should keep the existing unit tests.

BTW, I think there will be a regression because AbstractTransportListenerEx#getEPRsForService doesn't yet support protocol endpoints configured at the transport level. Thus, the generated WSDL will have no EPRs for the TCP transport.

> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org