ws-kandula-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] Commented: (AXIS2-4723) Make it Possible to Configure the TCP Transport at Service Level
Date Mon, 24 May 2010 15:14:25 GMT


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:
>             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:
For additional commands, e-mail:

View raw message