Mailing-List: contact j-dev-help@xerces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: j-dev@xerces.apache.org
Received-SPF: pass (athena.apache.org: domain of hiranya911@gmail.com
 designates 209.85.219.217 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=rF9pyM0L7NI5DpcHL2X2xm2uzKm87AODz2s39QpLtykv/iJXNcM1UmaORMXGk3AzTl
         a2znCPZKB5N8D5sPSoB8pHZGwdy8QqLll5l8lpCWlX/LmAaGAy9iTb3SXSljrj3e3OVe
         DQuDC6a/gQPvYT7ioCdW0Zs5VDlimqKEt69NQ=
MIME-Version: 1.0
Date: Tue, 11 Aug 2009 09:41:50 +0530
Message-ID: <558af1840908102111v27826682p41b62642089e48da@mail.gmail.com>
Subject: Changing the CTA API to Support Arbitrary Inputs
From: Hiranya Jayathilaka <hiranya911@gmail.com>
To: j-dev@xerces.apache.org
Content-Type: multipart/alternative; boundary=0015174c1aace36ebe0470d5e64b

--0015174c1aace36ebe0470d5e64b
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Devs,

The XML schema 1.1 conditional type assignment (CTA) API we currently have
restricts passing additional information to the test expression evaluator.
We can only pass the attributes information as of now. In an offlist
discussion, Khaled pointed out the benefits we can gain by changing the
current API to support passing of arbitrary data (for example through a map)
so that we don't have to change the API everytime when a requirement comes
up to pass a new data item to the XPath evaluator. FYI with Mukul working on
inheritable attributes feature such a requirement has already shown up :)

So what do you think about changing the existing API to accept a map of
objects instead of a fixed number of arguments? Changing the Test class
which is the high level entry point to XPath evaluator is easy. Should we
also change the low level classes which are responsible for processing the
actual XPath?

Thanks,
Hiranya

-- 
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

--0015174c1aace36ebe0470d5e64b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Devs,<br><br>The XML schema 1.1 conditional type assignment (CTA) API we=
 currently have restricts passing additional information to the test expres=
sion evaluator. We can only pass the attributes information as of now. In a=
n offlist discussion, Khaled pointed out the benefits we can gain by changi=
ng the current API to support passing of arbitrary data (for example throug=
h a map) so that we don&#39;t have to change the API everytime when a requi=
rement comes up to pass a new data item to the XPath evaluator. FYI with Mu=
kul working on inheritable attributes feature such a requirement has alread=
y shown up :)<br>
<br>So what do you think about changing the existing API to accept a map of=
 objects instead of a fixed number of arguments? Changing the Test class wh=
ich is the high level entry point to XPath evaluator is easy. Should we als=
o change the low level classes which are responsible for processing the act=
ual XPath?<br>
<br>Thanks,<br>Hiranya<br clear=3D"all"><br>-- <br>Hiranya Jayathilaka<br>S=
oftware Engineer;<br>WSO2 Inc.; =A0<a href=3D"http://wso2.org">http://wso2.=
org</a><br>E-mail: <a href=3D"mailto:hiranya@wso2.com">hiranya@wso2.com</a>=
; =A0Mobile: +94 77 633 3491<br>
Blog: <a href=3D"http://techfeast-hiranya.blogspot.com">http://techfeast-hi=
ranya.blogspot.com</a><br>

--0015174c1aace36ebe0470d5e64b--