On 3/9/10 5:01 PM, "Scott Cantor" <[email protected]> wrote:
>> I tried to turn on the functionality in the sample apps to control
>> validation as you mentioned but could not find an argument to specify my
>> .xsd file? Only whether or not to do schema validation. How do I plug my
>> file into the validator, and where would I look for the errors?
>
> Badly, and on the console.
>
> Locating schemas is a mess, but in general when validating files with
> precompiled tools you have to use xsi:schemaLocation hints either in the
> document or as a command line option (when supported, I don't recall if the
> sample apps support that).
Hm, I've given it some offort, but cannot seem to get it going. I have a
.xsd and a .xml file, and I just want to test if the XML is compliant with
the XSD.
I tried experimenting with the "count nodes" sample app, but can't get it.
Could you provide the command line commands I need?
>
> Real applications need to prevent schema hijacking and generally have to
> provide schema mapping functionality inside themselves. XML Catalogs are
> also a standard for this, and not one Xerces-C supports.
>
>> I am trying to write an XML validator that I can hand out to other people,
>> so I cannot write the code to do it in the actual app that creates the
> XML.
>
> I didn't mean that, I just meant if you weren't writing your own code, you'd
> have more luck with tools designed for validation.
I'm starting to wonder if I can use a standalone validator and just call it
from my app. The problem is I need to be able to do that from Mac, Linux,
and Windows. That is why I am trying to use xerces. Any other paths you
might suggest?
thanks
tim
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
