[EMAIL PROTECTED] wrote:
One may fear such change might break some people. But when a user turns on the dynamic validation feature (whether the validation feature is on or off), he's expecting something to happen, isn't he? So I don't think we would actually break anybody.
You would still break people. For example, an app written with the current Xerces requires that both validation and validation/dynamic be turned on for the dynamic validation to work. If their application turns off validation, then currently *no* validation occurs, dynamic or no.
However, if we made this change, when they upgrade to the latest Xerces, the parser starts validating documents that it previously wasn't. I would consider this broken because the expected behavior no longer holds. We're not just fixing a "bug" here, we're changing behavior. If the parser was behaving incorrectly before, then I would agree with you and tell users that they have to change their code because the parser was faulty. But this is not the case. -- Andy Clark * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
