Edwin, Edwin Goei wrote: > Yes, currently, if you use JAXP and turn on validation (and > namespaceAware), this also turns on XML Schema validation. I agree with > Arnaud, that this probably isn't the best thing to do. I sent some > email regarding this issue and how it may be incompatible with future > JAXP API specs. I'd vote to change the behavior now before its use gets > too entrenched.
Can you clarify? So in the new release of JAXP schema won't be automatically turned on? To turn on the schema support user must use "http://java.sun.com/xml/jaxp/properties/schemaLanguage"; property? If so, how can users specify: "My application receives documents that may include different grammars: some may include DTD, others may include XML Schemas. I want the parser to validate against the DTD if XML document has DTD, otherwise against XML Schema"? Thank you! -- Elena Litani / IBM Toronto -------- Original Message -------- Subject: Re: Xerces 1.4.4: Exposing XML Schema normalized values [README] Date: Thu, 18 Oct 2001 18:37:35 -0700 From: Edwin Goei <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Arnaud Le Hors wrote: > > For what it's worth I'd like to point out that the first error was to > make schema processing happen by default. I'm not sure whether people > care to do the right thing or not at this point but here is what I > think. > > To be backward compatible everytime a new feature is added it must be > off by default. That way, new applications can get the new behavior by > turning the new feature on and old applications still get the old > behavior they need not to break. > > The general trend seems to be "let's make it easy for new applications", > but that's just plain wrong. If you care about backward compatibility > that is. I do, but I seem to represent a minority, since everytime such > a question gets raised I have to go to the front to make my point > again... Yes, currently, if you use JAXP and turn on validation (and namespaceAware), this also turns on XML Schema validation. I agree with Arnaud, that this probably isn't the best thing to do. I sent some email regarding this issue and how it may be incompatible with future JAXP API specs. I'd vote to change the behavior now before its use gets too entrenched. -Edwin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
