[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.
Actually, if what is being reported is true then we already broke this
behavior. In Xerces 1 the dynamic validation and validation features
were carefully interlocked so that "the right thing happened". If that
has been broken in Xerces 2 then it should be fixed.
Comment from Xerces 1 DTDValidator.java:
//
// Turning on validation/dynamic turns on validation if it is off, and this
// is remembered. Turning off validation DISABLES validation/dynamic if it
// is on. Turning off validation/dynamic DOES NOT turn off validation if it
// was explicitly turned on, only if it was turned on BECAUSE OF the call to
// turn validation/dynamic on. Turning on validation will REENABLE and turn
// validation/dynamic back on if it was disabled by a call that turned off
// validation while validation/dynamic was enabled.
//
This was admittedly complex, but was arrived at after years of working on
this issue and should not be (have been) discarded lightly.
-Glenn
