Public Methods | |
bool | checkRootElement (const unsigned int elemId) |
Destructor | |
virtual | ~XMLValidator () |
Virtual validator interface | |
virtual int | checkContent (XMLElementDecl *const elemDecl, QName **const children, const unsigned int childCount)=0 |
virtual void | faultInAttr (XMLAttr &toFill, const XMLAttDef &attDef) const=0 |
virtual void | preContentValidation (bool reuseGrammar)=0 |
virtual void | postParseValidation ()=0 |
virtual void | reset ()=0 |
virtual bool | requiresNamespaces () const=0 |
virtual void | validateAttrValue (const XMLAttDef *attDef, const XMLCh *const attrValue)=0 |
virtual void | validateElement (const XMLElementDecl *elemDef)=0 |
virtual Grammar * | getGrammar () const=0 |
virtual void | setGrammar (Grammar *aGrammar)=0 |
Virtual DTD handler interface | |
virtual bool | handlesDTD () const=0 |
Virtual Schema handler interface | |
virtual bool | handlesSchema () const=0 |
Setter methods | |
void | setScannerInfo (XMLScanner *const owningScanner, ReaderMgr *const readerMgr, XMLBufferMgr *const bufMgr) |
void | setErrorReporter (XMLErrorReporter *const errorReporter) |
Error emittor methods | |
void | emitError (const XMLValid::Codes toEmit) |
void | emitError (const XMLValid::Codes toEmit, const XMLCh *const text1, const XMLCh *const text2=0, const XMLCh *const text3=0, const XMLCh *const text4=0) |
void | emitError (const XMLValid::Codes toEmit, const char *const text1, const char *const text2=0, const char *const text3=0, const char *const text4=0) |
Static Public Methods | |
void | reinitMsgMutex () |
void | reinitMsgLoader () |
Protected Methods | |
XMLValidator (XMLErrorReporter *const errReporter=0) | |
const XMLBufferMgr * | getBufMgr () const |
XMLBufferMgr * | getBufMgr () |
const ReaderMgr * | getReaderMgr () const |
ReaderMgr * | getReaderMgr () |
const XMLScanner * | getScanner () const |
XMLScanner * | getScanner () |
Basically, at this level, the primary concern is to be able to query core information about elements and attributes. Adding decls to the validator requires that you go through the derived interface because they all have their own decl types. At this level, we can return information via the base decl classes, from which each validator derives its own decl classes.
|
The derived class should clean up its allocated data, then this class will do the same for data allocated at this level. |
|
The derived class should look up its declaration of the passed element from its element pool. It should then use the content model description contained in that element declaration to validate that the passed list of child elements are valid for that content model. The count can be zero, indicating no child elements. Note that whitespace and text content are not validated here. Those are handled by the scanner. So only element ids are provided here.
|
|
DEPRECATED. For those validators that contrain the possible root elements of a document to only particular elements, they should use this call to validate that the passed root element id is a legal root element. |
|
This call is a convenience by which validators can emit errors. Most of the grunt work of loading the text, getting the current source location, ect... is handled here. If the loaded text has replacement parameters, then text strings can be passed. These will be used to replace the tokens {0}, {1}, {2}, and {3} in the order passed. So text1 will replace {0}, text2 will replace {1}, and so forth. textX Up to four replacement parameters. They can be provided as either XMLCh strings, or local code page strings which will be transcoded internally.
|
|
The derived class should fault in the passed XMLAttr value. It should use the passeed attribute definition (which is passed via the base type so it must often be downcast to the appropriate type for the derived validator class), to fill in the passed attribute. This is done as a performance enhancement since the derived class has more direct access to the information. |
|
Retrieve the Grammar used |
|
This method allows the scanner to ask the validator if it handles DTDs or not. |
|
This method allows the scanner to ask the validator if it handles Schema or not. |
|
This method is called by the scanner after the parse has completed. It gives the validator a chance to check certain things that can only be checked after the whole document has been parsed, such as referential integrity of ID/IDREF pairs and so forth. The validator should just issue errors for any problems it finds. |
|
This method is called by the scanner after a Grammar is scanned. |
|
The derived class should return a boolean that indicates whether it requires namespace processing or not. Some do and some allow it to be optional. This flag is used to control whether the client code's requests to disable namespace processing can be honored or not. |
|
This method is called by the scanner before a new document is about to start. It gives the validator a change to reset itself in preperation for another validation pass. |
|
This method is called to set an error reporter on the validator via which it will report any errors it sees during parsing or validation. This is generally called by the owning scanner.
|
|
Set the Grammar |
|
|
|
The derived class should apply any rules to the passed attribute value that are above and beyond those defined by XML 1.0. The scanner itself will impose XML 1.0 rules, based on the type of the attribute. This will generally be used to check things such as range checks and other datatype related validation. If the value breaks any rules as defined by the derived class, it should just issue errors as usual. |
|
The derived class should apply any rules to the passed element decl that are above and beyond those defined by XML 1.0. If the value breaks any rules as defined by the derived class, it should just issue errors as usual. |