j Jozef
on

 

I get the following error with some (but not all) Dataset-XML files:

-------- System Information ---------
 Version: 1.5
     JRE: 1.6.0_24
      OS: Windows 7 6.1 x86
--------------------------------------

org.opencdisc.validator.data.InvalidDataException
    at org.opencdisc.validator.data.DatasetXmlDataSource.parseVariables(DatasetXmlDataSource.java:184)
    at org.opencdisc.validator.data.AbstractDataSource.getVariables(AbstractDataSource.java:103)
    at org.opencdisc.validator.DefaultValidator.validate(DefaultValidator.java:407)
    at org.opencdisc.validator.gui.ValidatorClient$ProcessMonitor.run(ValidatorClient.java:1418)

The XML file with SDTM data is schema-valid against the latest (team) Dataset-XML Schema.

Any idea what is wrong?

 

Forums: Troubleshooting and Problems

j Jozef
on April 19, 2014

I could find the reason myself now by inspecting the source code.
OpenCDISC seems to be extremely strict on the rules, even causing the program to crash.
I had two problems in my files which cause OpenCDISC to give an exception and stop parsing.

a) If an empty "BasicDefinitions" is found in the define.xml, an exception is thrown and the program crashes.
However "BasicDefinitions" should be regarded as an extension, so i.m.o. a WARNING should be issued and the program should continue.

b) The MetaDataVersion OID of the define.xml and in the Dataset-XML did not exactly match. The Dataset-XML specification states that these should match, so in this case OpenCDISC should report an error (or at least a warning) instead of throwing an exception.

Best regards,

Jozef
Dataset-XML team

l Lex
on April 20, 2014

According to the Define-XML spec these BasicDefinitions should just generate informational messages:

"That is, define.xml files that use extensions are not wrong, but instead the extensions may be ignored unless the sender and receiver have agreed otherwise.  This also means that validators should flag ODM metadata not explicitly mentioned in the Define-XML specification with informational messages, and not with errors or warnings."

j Jozef
on April 20, 2014

Thanks Lex - of course you are right ...

So I guess this should be "INFO" or "NOTICE" in the report generated by OpenCDISC.
Currently, the program throws an exception, and stops parsing.
I already looked into the source code and commented the lines out that throw the exception, but I must still look into how it would generate an INFO message in the report.

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.