I am pretty new at xml-schema. I have been playing with XML Copy Editor for a few days and find it great. I am using version 1.2.0.2 on Windows Server 2003.
I am building a schema, and creating a dummy xml file to test it as I go. So far it is working fine.
As the schema is getting larger, I moved some of it into a separate file, and 'included' the file into the original.
Now when I try to validate, the program crashes with 'Application Error - The instruction at "0x77bd8790" referenced memory at "0x00000000". The memory could not be read'.
I am sure I have done something wrong. Perhaps you can help.
Hi all
I am pretty new at xml-schema. I have been playing with XML Copy Editor for a few days and find it great. I am using version 1.2.0.2 on Windows Server 2003.
I am building a schema, and creating a dummy xml file to test it as I go. So far it is working fine.
As the schema is getting larger, I moved some of it into a separate file, and 'included' the file into the original.
Now when I try to validate, the program crashes with 'Application Error - The instruction at "0x77bd8790" referenced memory at "0x00000000". The memory could not be read'.
I am sure I have done something wrong. Perhaps you can help.
This is the start of the xml document -
<?xml version="1.0" encoding="UTF-8"?>
<BusinessProcess name="AddCustomer" version="1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="bpmn.xsd">
This is the start of bpmn.xsd -
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xsd:include schemaLocation="event.xsd"/>
This is the start of event.xsd -
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
All files are in the same directory.
I tried changing the 'include' line to reference a non-existent file, to see if I got a different error, but it still crashed.
I have a schema-validator called 'minixsv' written in Python, and it validates the document without any problems.
Can you see anything wrong?
Thanks
Frank Millman
Hi Frank, thanks for your message. This is a fault in the application, not in your XML.
I have fixed this problem in the source and am hoping to release 2.0.3 with the fix very shortly.
In the meantime, installing 2.0 will fix the problem. (This is a fault I introduced in the latest release.)
Apologies for the inconvenience!
Best,
Gerald
Thanks for the response, Gerald.
No hurry on my side for the fix. I will just stick with one schema file for now.
Regards
Frank