>>>>> "Colin" == Colin Paul Adams <[EMAIL PROTECTED]> writes:
>>>>> "Sarah" == Leitner, Sarah M [Contractor] <Leitner> writes:
Sarah> So are you saying I can't do this for DOM? If so, how do I
Sarah> validate my code using a DTD?
Colin> You don't need to use an entity resolver at all for
Colin> validation. Just use DOMBuilder to parse the document,
Colin> first setting the "validation" feature on the DOMBuilder.
Colin> If you are building a DOM programatically, then you could
Colin> serialize it and re-parse it to validate (not very
Colin> efficient, I know). -- Colin Paul Adams Preston Lancashire
Sorry Sarah, I should have read the whole thread.
Erik's entity resolver will do what you want.
What I was talking about is the DOM 3.0 draft setEntityResolver
function. In that the resolveEntity function is supposed to return a
DOMInputSource *. it is this class that is not fully implemented (or
indeed fully specified) in xerces. Erik's code is returning an
InputSource * which is a Xerces-specific class.
Sorry for confusing the issue.
--
Colin Paul Adams
Preston Lancashire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
