axis-java-dev mailing list archives

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

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

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

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

It's a limitation of AbstractTransportListenerEx. I've done some modifications (see r947834)
to enable this, but it still requires some finetuning.

> 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


Mime
View raw message