Return-Path: Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: (qmail 49450 invoked from network); 24 May 2010 17:00:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 24 May 2010 17:00:50 -0000 Received: (qmail 61955 invoked by uid 500); 24 May 2010 17:00:49 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 61777 invoked by uid 500); 24 May 2010 17:00:49 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 61769 invoked by uid 99); 24 May 2010 17:00:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 May 2010 17:00:49 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 May 2010 17:00:47 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o4OH0Pf8010113 for ; Mon, 24 May 2010 17:00:25 GMT Message-ID: <10961181.12961274720425296.JavaMail.jira@thor> Date: Mon, 24 May 2010 13:00:25 -0400 (EDT) From: "Hiranya Jayathilaka (JIRA)" To: java-dev@axis.apache.org Subject: [jira] Commented: (AXIS2-4723) Make it Possible to Configure the TCP Transport at Service Level In-Reply-To: <6318569.4491274678784521.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AXIS2-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870710#action_12870710 ] Hiranya Jayathilaka commented on AXIS2-4723: -------------------------------------------- BTW rest assured that this new version of the TCP transport also supports endpoints configured at transport level. I have tested and verified the functionality. However I ran into a series of issues with the existing test cases due to the way they are currently organized. Basically I ended up getting a bunch of bind exceptions. I just fixed the tests for the moment since I wanted to put forward the patch for review. I will work on the tests and get them back to their original state. Expect a new patch fairly soon. > 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