Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 29275 invoked from network); 11 Nov 2005 15:53:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Nov 2005 15:53:54 -0000 Received: (qmail 60792 invoked by uid 500); 11 Nov 2005 15:53:51 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 60760 invoked by uid 500); 11 Nov 2005 15:53:51 -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 60749 invoked by uid 99); 11 Nov 2005 15:53:51 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2005 07:53:51 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.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; Fri, 11 Nov 2005 07:53:43 -0800 Received: (qmail 4525 invoked from network); 11 Nov 2005 15:53:28 -0000 Received: from unknown (HELO ?192.168.1.2?) (unknown) by unknown with SMTP; 11 Nov 2005 15:53:28 -0000 X-pair-Authenticated: 220.247.245.154 Subject: Re: [Axis2] SOAPMessageContext From: Sanjiva Weerawarana To: axis-dev@ws.apache.org Cc: chinthaka@opensource.lk In-Reply-To: References: <4374B09B.3070501@opensource.lk> <88f5d710511110705sca0ee68odb79adf80e22c222@mail.gmail.com> <4374B4B9.7040602@opensource.lk> Content-Type: text/plain Organization: Lanka Software Foundation Date: Fri, 11 Nov 2005 21:52:35 +0600 Message-Id: <1131724355.6389.36.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Fri, 2005-11-11 at 07:40 -0800, Ajith Ranabahu wrote: > Hi all, > I see that folks have different views on putting this particular > SOAPMessageContext, most probably as part of Axis2 itself would be > slightly inappropriate since Axis2 can survive nicely without it :). > Here's my plan to make both worlds happy. Instead of just creating > message contexts inside, we provide a MessageContextFactory that is > settable from outside (probably through Axis2.xml). This makes it > flexible enough for Synapse to introduce it's own context and Axis2 > never needs to know about Synapse or anything! SOAPMsgCtxt can remain > as part of Synapse rather than Axis2 The idea was to simply define an interface named SOAPMessageContext with the proposed methods (which are a strict subset of the MessageContext APIs, IIUC) and then declare that MessageContext implements that. Thus Axis2 does not have to change but the Synapse APIs are clean and simple to Synapse rule engine and mediator writers. To do this really cleanly would require quit a bit of surgery to move the addressing stuff from core to the xml module. I'm not a fan of doing that at this point .. I'd rather define the interface inside o.a.axis2.context package and live with it. This does not achieve total independence of Synapse from Axis2; IMO that's not an easy task .. unless you go down to StAX as the API to the SOAP message. Even then you have to figure out how to represent other contextual information. Sanjiva.