|
Hi Khaled, Thanks for
the reply. Here is the zip file
with all of the schema files I am using and the sample XML instance file and
error logs. I ran the
test with two different command lines, and they produced different errors. For the first test the command line
was: DOMPrint.exe
-v=auto -s -f -e –n descriptionExample016.xml See
ErrorLog-1.txt for the results. For the
second test I ran: DOMPrint.exe
-v=auto -s -e –n descriptionExample016.xml See
ErrorLog-2.txt for the results. The
results in the first test regarding the ##any and <some schema item>
violating unique particle attribution wasn’t clear at all. Perhaps if possible you wouldn’t mind
explaining the message in English.
The first test always produces a stack overflow which isn’t clear
either. Can you see why the –f “Full
Schema Validation” would create a stack overflow? The
<import> directive specifically applies to the use of the xml:lang
attribute which doesn’t appear to be recognized or work yet. Thanks for
any help you can be on these matters. -----Original
Message----- Hi Elisha, The C++ parser has support for the W3C
schema language except for some limitations as noted in http://xml.apache.org/xerces-c/schema.html.
o The problem with <include>
directive is one of the limitations and will be fixed in the next release. If you find any problems with the parser,
you can use bugzilla (http://nagoya.apache.org/bugzilla)
to open a bug against the C++ parser. Regards, Elisha Berns wrote: Hi, �
<include schemaLocation=”…”> appears to only work when
the order of the include statements is in the same order as the dependency
order of the declarations inside the file(s) included much in the same way as
.h files needs to be #included in the order of dependencies in C++. If you
include a schema document that attempts to reference schema declarations that
are found in a document included later, the validator appears to not recognize
the declarations and the validation fails. �
The validator doesn’t like complexType elements of
complexContent in which some of the member elements have a “minOccurs=0”
attribute. It seems to expect the actual element in an instance document
nevertheless. So, the minOccurs
attribute isn’t implemented? |
TestSchema.zip
Description: Zip compressed data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
