Mailing-List: contact synapse-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: synapse-dev@ws.apache.org
Received-SPF: pass (athena.apache.org: domain of ruwan.linton@gmail.com
 designates 209.85.134.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=wzKW1goBCwSH8INnYQSzeUyq/iIvQQTEUNHGPXtGl7An0cw7CzWfWxEe7FUU1fCYO742EWmSlbeAb6A4Yu9zae6oCHf08a9X1rE32skTFA/4Kh9ed3WJBrH+WKxCPJON1eOdH8CeyUdnY2bEgltELsmjZw3xFpbBU60KFjzc7Rk=
Message-ID: <672a01200712140208o56b83c86h50d845956e5c4766@mail.gmail.com>
Date: Fri, 14 Dec 2007 15:38:19 +0530
From: "Ruwan Linton" <ruwan.linton@gmail.com>
To: synapse-dev@ws.apache.org
Subject: Re: POJOCommand mediator synatx
In-Reply-To: <88f5d710712140022i32c7a531p9a24f1b0356b2ac9@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_431_21777401.1197626899899"
References: <672a01200712112210r10f95215la6afccb1f7841b78@mail.gmail.com>
	 <88f5d710712130747p26a12a17gaeb8b1523e1ff9@mail.gmail.com>
	 <672a01200712131942g3304c7fen62896848416c6959@mail.gmail.com>
	 <88f5d710712140022i32c7a531p9a24f1b0356b2ac9@mail.gmail.com>

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

Paul,

On Dec 14, 2007 1:52 PM, Paul Fremantle <pzfreo@gmail.com> wrote:

> Ruwam


I think you are referring to me (Ruwan) not some one named Ruwam :)

Well, even though we need to keep the consistency, at the same time we have
to keep the things simpler to understand and the implementation solid. But I
don't see this as simple to understand.

To me this syntax is cleaner than what you suggested.

Thanks,
Ruwan


>
> What I don't like about this is that everywhere else in Synapse we have a
> consistent access to message context properties. Nowhere else do we use this
> syntax.
>
> Whatever we do we need to sync it up with all the other places where we
> get and set mc properties I think - e.g. DBLookup, etc.
>
> Paul


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

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

Paul,<br><br><div class="gmail_quote">On Dec 14, 2007 1:52 PM, Paul Fremantle &lt;<a href="mailto:pzfreo@gmail.com">pzfreo@gmail.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ruwam</blockquote><div><br>I think you are referring to me (Ruwan) not some one named Ruwam :)<br><br>Well, even though we need to keep the consistency, at the same time we have to keep the things simpler to understand and the implementation solid. But I don&#39;t see this as simple to understand.
<br><br>To me this syntax is cleaner than what you suggested.<br><br>Thanks,<br>Ruwan<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br>What I don&#39;t like about this is that everywhere else in Synapse we have a consistent access to message context properties. Nowhere else do we use this syntax. <br><br>Whatever we do we need to sync it up with all the other places where we get and set mc properties I think - 
e.g. DBLookup, etc.<br><font color="#888888"><br>Paul</font></blockquote></div><br><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_431_21777401.1197626899899--