axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiranya Jayathilaka (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-4723) Make it Possible to Configure the TCP Transport at Service Level
Date Thu, 27 May 2010 06:01:36 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hiranya Jayathilaka updated AXIS2-4723:
---------------------------------------

    Attachment: AXIS2-4723-update4.patch

Added the contentType parameter to the generated EPRs (will be added only if it is different
from the default)

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


Mime
View raw message