You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In release 1.0.1, setting these was silently ignored (which was itself technically a bug - see issue #46 for some background). In release 1.0.2 these cause an error because the default schema language is XSD.
Unfortunately its not possible at this time to apply a DTD to an arbitrary XML document as JAXP doesn't provide a means to do this. Research is been done on this as part of Java XML Validation Collection
The text was updated successfully, but these errors were encountered:
I think, this issues scope is too far. My suggestion would be, like follows:
As an alternative to publicId, and systemId, provide a boolean attribute "usingDtd".
If this attribute is true, then turn "validating" on upon creation of the XML parser. As a side effect, this enforces presence of a DTD declaration, but I think we can live with that.
Regarding the scope, I put this in as a place holder for later work, I've updated the issue to mark it as an enhancement request and I'm not putting a milestone against it until I do further work on my own validation projects. So its more of a long term aspiration.
Regarding your points 1 and 2, I think the plugin already does these. As I understand it and as discussed in issue #46, the "validating" boolean works the same as your suggested "usingDtd". Issue #47 talks about improving the documentation to make this more clear.
In release 1.0.1, setting these was silently ignored (which was itself technically a bug - see issue #46 for some background). In release 1.0.2 these cause an error because the default schema language is XSD.
Unfortunately its not possible at this time to apply a DTD to an arbitrary XML document as JAXP doesn't provide a means to do this. Research is been done on this as part of Java XML Validation Collection
The text was updated successfully, but these errors were encountered: