TODO: This is all overkill. ConfigurationLoader doesn't need its own validator,
nor does it need to use the ConstructingParser which is used for TDML only because
it deals with CDATA nodes differently than the regular loader (DaffodilXMLLoader,
which is based on scala.xml.XML's loader, which is based on the sax parser
built into the JVM (which is xerces?), and which validates.
For the configuration loader, we only need plain old loading.
I suspect this was just cloned from the TDML loader code, and so copied its
more complicated arrangements.
TODO: This is all overkill. ConfigurationLoader doesn't need its own validator, nor does it need to use the ConstructingParser which is used for TDML only because it deals with CDATA nodes differently than the regular loader (DaffodilXMLLoader, which is based on scala.xml.XML's loader, which is based on the sax parser built into the JVM (which is xerces?), and which validates.
For the configuration loader, we only need plain old loading.
I suspect this was just cloned from the TDML loader code, and so copied its more complicated arrangements.