on present,
has schemaLocation attribute present etc.
Regards,
-- Neeraj
> Simon
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 16 April 2002 10:31 a.m.
> To: [EMAIL PROTECTED]
> Subject: Re: Validating XML documents using t
"Dallaway, Simon" wrote:
> Thanks for the response. I guess to some extent the problem is one needs to
> be solved within the standard JAXP specification, possibly by deprecating
> setValidating and defining setDTDValidating and setXSDValidating methods
> instead?
JAXP tries to solve this problem
] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 16 April 2002 10:31 a.m.
To: [EMAIL PROTECTED]
Subject: Re: Validating XML documents using the Xerces parser
Hi Simon,
The deal is this: the SAX validation feature was developed in the days of
DTD's. When you turned it on, it meant "report
Hi Simon,
The deal is this: the SAX validation feature was developed in the days of
DTD's. When you turned it on, it meant "report validation errors" so for a
document with no DTD--which, by the XML 1.0 spec is invalid--we'd have to
report errors. i.e., on a schema-valid document we'd have to r
I'm a little confused. I've figured out that in order to make the parser
pick up and use an XSD specified by an xsi:schemaLocation attribute I need
to set the Apache attribute shown in the code fragment below.
factory.setNamespaceAware(true);
factory.setValidating(true);
factory.
