Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (herse.apache.org: domain of msatoor@gmail.com designates
 209.85.132.245 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=tTprlDVZMlNOAG5Dornf/DUFQ/Ccw9t0GUJ8C91mvtWhsMZJZohCZoJo9zDJ1xDPD8/gQcSSDUCriwQ2F2G3zmY1yGufIGAO/J5jCCXgE3ls3HILM5T50VeZn68rcIFWWBnclxeruj+5f5FiXI8jpw/HoAyyGXAQ2Fuaw6CoIl4=
Message-ID: <d9619e4a0706081527i42909699odc321981a5bc8c0a@mail.gmail.com>
Date: Fri, 8 Jun 2007 15:27:43 -0700
From: "Mamta Satoor" <msatoor@gmail.com>
To: derby-dev@db.apache.org
Subject: Re: svn commit: r545639 -
 /db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/lang/CollationTest.java
In-Reply-To: <4669D0E4.2070003@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_84400_21460105.1181341663520"
References: <20070608214111.A45F11A981A@eris.apache.org>
	 <4669D0E4.2070003@gmail.com>

------=_Part_84400_21460105.1181341663520
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Army, I added this additional test case for parameter and XMLSERIALIZE just
as a place holder so in future, at some point, if we do support parameters
for
XMLERSERIALIZE, we will have a test case which probably will fail and will
be a safety check to make sure parameter and XMLSERIALIZE will work fine.

Mamta


On 6/8/07, Army <qozinx@gmail.com> wrote:
>
> mamta@apache.org wrote:
>
> > DERBY-2777
> > I realized that there are no negative test case for parameter inside
> XMLSERIALIZE funciton.
> ...
> > Parameters are not supported inside XMLSERIALIZE and that's what the new
> test
> > cases are checking.
>
> Just curious: is this different from the check in the
> "testInvalidXMLBindings()"
> method of lang/XMLBindingTest.java?  I.e. are we adding this test case
> here for
> collation purposes, or just as a general test case for XMLSERIALIZE?
>
> Army
>
>

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

<div>Army, I added this additional test case for parameter and XMLSERIALIZE just as a place holder so in future, at some point, if we do support parameters for </div>
<div>XMLERSERIALIZE, we will have a test case which probably will fail and will be a safety check to make sure parameter and XMLSERIALIZE will work fine.</div>
<div>&nbsp;</div>
<div>Mamta<br><br>&nbsp;</div>
<div><span class="gmail_quote">On 6/8/07, <b class="gmail_sendername">Army</b> &lt;<a href="mailto:qozinx@gmail.com">qozinx@gmail.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><a href="mailto:mamta@apache.org">mamta@apache.org</a> wrote:<br><br>&gt; DERBY-2777<br>&gt; I realized that there are no negative test case for parameter inside XMLSERIALIZE funciton.
<br>...<br>&gt; Parameters are not supported inside XMLSERIALIZE and that&#39;s what the new test<br>&gt; cases are checking.<br><br>Just curious: is this different from the check in the &quot;testInvalidXMLBindings()&quot;
<br>method of lang/XMLBindingTest.java?&nbsp;&nbsp;I.e. are we adding this test case here for<br>collation purposes, or just as a general test case for XMLSERIALIZE?<br><br>Army<br><br></blockquote></div><br>

------=_Part_84400_21460105.1181341663520--