Return-Path: Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: (qmail 96551 invoked from network); 2 Oct 2010 04:51:53 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Oct 2010 04:51:53 -0000 Received: (qmail 6865 invoked by uid 500); 2 Oct 2010 04:51:53 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 6685 invoked by uid 500); 2 Oct 2010 04:51:50 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 6678 invoked by uid 99); 2 Oct 2010 04:51:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Oct 2010 04:51:49 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.161.42] (HELO mail-fx0-f42.google.com) (209.85.161.42) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Oct 2010 04:51:45 +0000 Received: by fxm11 with SMTP id 11so3496667fxm.15 for ; Fri, 01 Oct 2010 21:51:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.169.65 with SMTP id n1mr799957hbe.69.1285995082256; Fri, 01 Oct 2010 21:51:22 -0700 (PDT) Received: by 10.239.178.143 with HTTP; Fri, 1 Oct 2010 21:51:22 -0700 (PDT) In-Reply-To: References: Date: Sat, 2 Oct 2010 10:21:22 +0530 Message-ID: Subject: Re: Synapse configuration namespace From: Sanjiva Weerawarana To: dev@synapse.apache.org Content-Type: multipart/alternative; boundary=001636498aa30f91ff04919b10a7 --001636498aa30f91ff04919b10a7 Content-Type: text/plain; charset=ISO-8859-1 I realize this is a bit of a late response :(. This change will break all existing users. How about at least supporting both namespaces? (Maybe this is too late now for the release ... in which case there's no point doing it later.) Sanjiva. On Mon, Apr 26, 2010 at 10:22 PM, Ruwan Linton wrote: > Folks, > > We have been using the http://ws.apache.org/ns/synapse as the synapse > configuration namespace, since synapse was graduated on to the WS project > and we didn't want to introduce a configuration incompatibility because of > becoming a new TLP, and with the new 2.0 release planned to be out, I am > planning to change the synapse configuration namespace to a more meaning > full namespace; > > http://synapse.apache.org/ns/2010/04/configuration > > Provided that the migration tool will be there this change should be OK > with the 2.0 release. > > Thoughts?? > > Thanks, > Ruwan > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 Inc.; http://wso2.org > email: ruwan@wso2.com; cell: +94 77 341 3097 > blog: http://ruwansblog.blogspot.com > -- Sanjiva Weerawarana, Ph.D. Founder, Director & Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2; http://wso2.com/ Founder & Director; Thinkcube Systems; http://www.thinkcube.com/ Member; Apache Software Foundation; http://www.apache.org/ Member; Sahana Software Foundation; http://www.sahanafoundation.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/ --001636498aa30f91ff04919b10a7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I realize this is a bit of a late response :(.

This change will bre= ak all existing users. How about at least supporting both namespaces?=A0

(Maybe this is too late now for the release ... in w= hich case there's no point doing it later.)

Sanjiva.

On Mo= n, Apr 26, 2010 at 10:22 PM, Ruwan Linton <ruwan.linton@gmail.com> wrote:=
Folks,

We have been using the http://ws.apache.or= g/ns/synapse as the synapse configuration namespace, since synapse was = graduated on to the WS project and we didn't want to introduce a config= uration incompatibility because of becoming a new TLP, and with the new 2.0= release planned to be out, I am planning to change the synapse configurati= on namespace to a more meaning full namespace;

http://synapse.apache.org/ns/2010/04/configuration

P= rovided that the migration tool will be there this change should be OK with= the 2.0 release.

Thoughts??

Thanks,
Ruwan

--
Ruwan Linton
Technical Lead & Product Manager; WSO2 = ESB; http://wso2.org/esb<= /a>
WSO2 Inc.;
http://wso2.org
email:
ruwan@wso2.com; cell: +94 77 341 3097
blog:
http://ruwansblog.blogspot.com



--
Sanjiva Weerawar= ana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Found= ation; http://www.o= pensource.lk/
Founder, Chairman & CEO; WSO2; http://wso2.com/
Founder & Director; Thinkcube Systems; = http://www.thinkcub= e.com/
Member; Apache Software Foundation; http://www.apache.org/
Member; Sahana Software Foundat= ion; http://= www.sahanafoundation.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weera= warana.org/

--001636498aa30f91ff04919b10a7--