Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 41376 invoked from network); 6 Oct 2007 08:06:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Oct 2007 08:06:19 -0000 Received: (qmail 61087 invoked by uid 500); 6 Oct 2007 08:06:01 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 61025 invoked by uid 500); 6 Oct 2007 08:06:01 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 61014 invoked by uid 99); 6 Oct 2007 08:06:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Oct 2007 01:06:01 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.68.5.15] (HELO relay01.pair.com) (209.68.5.15) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 06 Oct 2007 08:06:04 +0000 Received: (qmail 71402 invoked from network); 6 Oct 2007 08:05:41 -0000 Received: from unknown (HELO ?10.0.0.4?) (unknown) by unknown with SMTP; 6 Oct 2007 08:05:41 -0000 X-pair-Authenticated: 124.43.208.28 Message-ID: <470741D4.8080806@wso2.com> Date: Sat, 06 Oct 2007 13:35:40 +0530 From: "Asankha C. Perera" User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: synapse-dev@ws.apache.org CC: axis-dev@ws.apache.org Subject: Re: Getting axis2 transport out from the kernel References: <4705E8DC.3020506@wso2.com> <9abd5e730710050104k35264b38m30cb555d6dcbe06d@mail.gmail.com> <4705F7AE.8070507@wso2.com> <470677F0.7000906@opensource.lk> In-Reply-To: <470677F0.7000906@opensource.lk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org >> manage the next release of Synapse (i.e. 1.1) the way things are >> using a few tricks like putting our copy of the transport in-front of >> the Axis2-kernel etc. at runtime. > > Why do you need trickery? The transports are coming out of axis2.xml > .. why can you not simply put another transport in and take out the > one(s) you don't like? This is because we depend on the Axis2 1.3 "released" version from Maven2 that now has a JMS and NIO-http/code copy of the code. Remember my points on supporting JMS 1.0.1 for Synapse now, and improvements to NIO-http/s to bring in the latest fixes from HttpCore.. so one solution is for me to "rename" classes or the package, or load the synapse-transports.jar that contains these fixes before the axis2-kernel.jar at runtime. I have choosen the latter as in future, I would like to continue to do fixes as necessary to these transports under Synapse, and merge back into Axis2 at each major/minor Axis2 release. This will allow me to keep Synapse upto-date on transports - as well as give all fixes back into Axis2 easily without asking for Axis2 releases if we had to fix a bug or require an enhancement in a transport asankha --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org