Return-Path: 
 <synapse-dev-return-4329-apmail-ws-synapse-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-synapse-dev-archive@www.apache.org
Received: (qmail 99017 invoked from network); 20 Sep 2007 06:46:12 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 20 Sep 2007 06:46:12 -0000
Received: (qmail 93916 invoked by uid 500); 20 Sep 2007 06:46:03 -0000
Delivered-To: apmail-ws-synapse-dev-archive@ws.apache.org
Received: (qmail 93882 invoked by uid 500); 20 Sep 2007 06:46:03 -0000
Mailing-List: contact synapse-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: synapse-dev@ws.apache.org
list-help: <mailto:synapse-dev-help@ws.apache.org>
list-unsubscribe: <mailto:synapse-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:synapse-dev@ws.apache.org>
List-Id: <synapse-dev.ws.apache.org>
Delivered-To: mailing list synapse-dev@ws.apache.org
Received: (qmail 93867 invoked by uid 99); 20 Sep 2007 06:46:03 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2007 23:46:03 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of ruwan.linton@gmail.com
 designates 209.85.128.188 as permitted sender)
Received: from [209.85.128.188] (HELO fk-out-0910.google.com) (209.85.128.188)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Sep 2007 06:45:59 +0000
Received: by fk-out-0910.google.com with SMTP id f40so410568fka
        for <synapse-dev@ws.apache.org>; Wed, 19 Sep 2007 23:45:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
        bh=/pw0WGBIODY2b9WZlrHVIqLHov4gUFz+aZzKZwaS4pA=;
        b=hBpXq8GGtn/x6d16/wEJ3ZsmcaAbCo/a36ku8tHuHvTVGJxSNZ5Di5DYQIFbu6cfF4jK5RSW70x+Wu04BxMi+frjbHEcgaJi6A82bFzPGBSYdk41eczuAc9q3uk0jbpiBo7w+4IDBakIK2AbfEN40CIePU4yw1MTKQ5yu1Ari1g=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=Lxw+XbmuhFJ23taYdaYFYI2jG5vk8hvP88Fzko6Ti5V99xQTLqfiMTeZPGWnTH+9EVcjlmxKY9FQxU15hXBLsD5+PR3PimUpV9HPNRo9H6TsbEz6OziDAUw1eo6fFu9jPfg0Zqhc9uJwyq5PYh0rQir4m+irSaO5Smf2PLyzQsw=
Received: by 10.82.170.2 with SMTP id s2mr1914669bue.1190270738152;
        Wed, 19 Sep 2007 23:45:38 -0700 (PDT)
Received: by 10.82.179.18 with HTTP; Wed, 19 Sep 2007 23:45:38 -0700 (PDT)
Message-ID: <672a01200709192345w3b7b99d9v9c94de920578fd88@mail.gmail.com>
Date: Thu, 20 Sep 2007 12:15:38 +0530
From: "Ruwan Linton" <ruwan.linton@gmail.com>
To: synapse-dev@ws.apache.org
Subject: Job language syntax in the Synapse configuration
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_19217_27520318.1190270738141"
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_19217_27520318.1190270738141
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi all,

For the moment the configuration for the jobs seems to be like following;

<definitions>
 <startup>
  <job ...../>*
 </startup>
 ......
</definitions>

The <startup> element is wrapping all the jobs. With compared to other
elements in the configuration like <sequence>, <endpoint> and all they are
top level elements even mediators can appear in the top level in which case
that collection is treated as the main sequence. So I propose to bring the
<jobs> element to the top level as follows;

<definitions>
 <registry ..../>?
 <proxy .../>*
 <sequence .../>*
 <endpoint ..../>*
 <job .../>*
 <localEntry .../>*
 (mediator)*
</definitions>

If we do have multiple types of jobs then we can let the FactoryFinder to
handle that. Is there any particular reason that I am missing here? If not
shall we bring these jobs to the top level before 1.1 release?

Thanks,
Ruwan

-- 
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

------=_Part_19217_27520318.1190270738141
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi all,<br><br>For the moment the configuration for the jobs seems to be like following;<br><br>&lt;definitions&gt;<br>&nbsp;&lt;startup&gt;<br>&nbsp; &lt;job ...../&gt;*<br>&nbsp;&lt;/startup&gt;<br>&nbsp;......<br>&lt;/definitions&gt;<br><br>
The &lt;startup&gt; element is wrapping all the jobs. With compared to other elements in the configuration like &lt;sequence&gt;, &lt;endpoint&gt; and all they are top level elements even mediators can appear in the top level in which case that collection is treated as the main sequence. So I propose to bring the &lt;jobs&gt; element to the top level as follows;
<br><br>&lt;definitions&gt;<br>&nbsp;&lt;registry ..../&gt;?<br>&nbsp;&lt;proxy .../&gt;*<br>&nbsp;&lt;sequence .../&gt;*<br>&nbsp;&lt;endpoint ..../&gt;*<br>&nbsp;&lt;job .../&gt;*<br>&nbsp;&lt;localEntry .../&gt;*<br>&nbsp;(mediator)*<br>&lt;/definitions&gt;
<br><br>If we do have multiple types of jobs then we can let the FactoryFinder to handle that. Is there any particular reason that I am missing here? If not shall we bring these jobs to the top level before 1.1 release?<br>
<br>Thanks,<br>Ruwan<br clear="all"><br>-- <br>Ruwan Linton<br><a href="http://www.wso2.org">http://www.wso2.org</a> - &quot;Oxygenating the Web Services Platform&quot;

------=_Part_19217_27520318.1190270738141--