Altova Mailing List Archives


Re: XSV 2.10 IDC-XPath problem when using "child::"

From: ht@---.--.--.-- (----- -. --------)
To: Kasimier Buchcik <K.Buchcik@---------.-->
Date: 10/21/2005 11:13:00 AM
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kasimier Buchcik writes:

> An XSV 2.10 crash; probably due to the "child::" in the
> <xsd:selector xpath="child::foo:item"/>.
> It works fine if I change the XPath expression to "foo:item".

Never implemented, but not hard, will be in next release.

ht
=2D -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@i...
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged sp=
am]
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDWLEqkjnJixAXWBoRAuzLAJ9HqhjefTN8QM7qFX2bVmBVT1Z8eQCeI2cN
KaDM+cxVdXG3PsZoOONck4w=
=v0Gf
=2D----END PGP SIGNATURE-----

From ht@i... Fri Oct 21 09:14:57 2005
Received: from maggi

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.