[ http://issues.apache.org/jira/browse/DERBY-563?page=all ]
     
Andrew McIntyre resolved DERBY-563:
-----------------------------------

    Resolution: Fixed

Committed to trunk with revision 280680.

> Create an XML test suite in the Derby harness to allow testing of the basic 
> XML datatype and related operators.
> ---------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-563
>          URL: http://issues.apache.org/jira/browse/DERBY-563
>      Project: Derby
>         Type: Improvement
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: A B
>     Assignee: A B
>      Fix For: 10.2.0.0
>  Attachments: xmlsuite.patch
>
> Back with DERBY-334 some experimental XML support was added to Derby, 
> including an XML datatype and three corresponding operators (see that issue 
> for more details).  Two tests (lang/xml_general.sql and lang/xmlBinding.java) 
> were included in that patch but were "disabled" because current XML support 
> requires Apache Xerces to be in classpath and I didn't want to force people 
> to download Xerces in order to get a clean run of "derbyall".
> That said, I think an XML suite should be created to include the two tests 
> mentioned above for now, and as Derby's support for XML grows in the future, 
> that suite can hold additional tests.
> Also, I tried running the tests with Xerces in my classpath and they both 
> failed--it turns out that entries for the tests are missing from the 
> .../functionTests/tests/lang/copyfiles.ant file.  So that problem should be 
> fixed as part of this issue, as well.
> NOTE: This issue involves creating a suite to run the existing tests while 
> assuming that the person running the tests has Xerces in his/her classpath.  
> Another improvement, for which I will file a different Jira issue, would be 
> to change Derby so that it can somehow find the XML parser that comes with 
> the user's JVM (current XML support requires at least a 1.4 JVM), in which 
> case no additional XML parser would be required.  More coming on that in a 
> separate Jira issue...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to