Xerces 3.2 includes a wired up disallow-doctype property so the library should set it in the ParserPool class.
It's actually safe to set unilaterally because the older version just ignored the property, but it's also possible if we want to to conditionally check for support via canSetParameter() if we want to log a warning.
Environment
None
Activity
Scott Cantor January 12, 2018 at 7:06 PM
Removed original hack from SP master branch now that it's handled by the library.
Takeshi Nishimura January 11, 2018 at 7:05 PM
Exactly. I must forget the name.
Scott Cantor January 11, 2018 at 6:48 PM
There's no variable anymore, it's a parser property, nothing at all to do with the original hack.
As it happens I was and am handling this in the code in every version, so there's really nothing to do here. "Stay current" and that's it.
Takeshi Nishimura January 11, 2018 at 6:41 PM
Is the variable name XERCES_DISABLE_DTD ? It is confusing if the name will be changed in 3.2.
Scott Cantor January 11, 2018 at 4:28 PM
I forgot that I implemented a defaulted setting in 2.6.0 to set the XERCES_DISALLOW_DTD variable in the code.
Since 3.0 will be assuming Xerces 3.2, we should be able to remove that code in favor of the parser setting.
Xerces 3.2 includes a wired up disallow-doctype property so the library should set it in the ParserPool class.
It's actually safe to set unilaterally because the older version just ignored the property, but it's also possible if we want to to conditionally check for support via canSetParameter() if we want to log a warning.