We had a requirement to validate XML during unmarshalling against the .xsd specified in the root element e.g.
<TOPELEMENT xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:noNamespaceSchemaLocation="top.xsd"> So we first of all enabled castor validation (org.exolab.castor.parser.validation=true). However the Castor .validate() methods only validate at a high level, and not rigourously against the schema. The only way we could achieve this was to enable the SAX 2 feature :- org.exolab.castor.sax.features=http://apache.org/xml/features/validation/sch ema in the castor.properties file. This seems to be working, however some XML instances that we're unmarshalling don't require this strict SAX 2 validation/schema feature, can we turn this off/on programmatically and choose for each Unmarshall ? This transmission is confidential and intended solely for the person or organisation to whom it is addressed. It may contain privileged and confidential information. If you are not the intended recipient, you should not copy, distribute or take any action in reliance on it. If you have received this transmission in error, please notify the sender immediately. Any opinions or advice contained in this e-mail are those of the individual sender except where they are stated to be the views of RDF Group or EMS plc. All messages passing through this gateway are virus scanned. ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
