Interface IEntityResolver2

Extended interface for mapping external entity references to input sources, or providing a missing external subset. The EntityResolver property is used to provide implementations of this interface to parsers. When a parser uses the methods in this interface, the ResolveEntity(String, String, String, String) method (in this interface) is used instead of the older (SAX 1.0) ResolveEntity(String, String) method.

Inherited Members
Assembly: Lucene.Net.Benchmark.dll
Syntax
public interface IEntityResolver2 : IEntityResolver
Remarks

This module, both source code and documentation, is in the Public Domain, and comes with NO WARRANTY.

If a SAX application requires the customized handling which this interface defines for external entities, it must ensure that it uses an XMLReader with the http://xml.org/sax/features/use-entity-resolver2 feature flag set to true (which is its default value when the feature is recognized). If that flag is unrecognized, or its value is false, or the resolver does not implement this interface, then only the IEntityResolver method will be used.

That supports three categories of application that modify entity resolution. Old Style applications won't know about this interface; they will provide an IEntityResolver. Transitional Mode provide an IEntityResolver2 and automatically get the benefit of its methods in any systems (parsers or other tools) supporting it, due to polymorphism. Both Old Style and Transitional Mode applications will work with any SAX2 parser. New style applications will fail to run except on SAX2 parsers that support this particular feature. They will insist that feature flag have a value of "true", and the IEntityResolver2 implementation they provide might throw an exception if the original SAX 1.0 style entity resolution method is invoked.

Methods

Name Description
GetExternalSubset(String, String)

Allows applications to provide an external subset for documents that don't explicitly define one. Documents with DOCTYPE declarations that omit an external subset can thus augment the declarations available for validation, entity processing, and attribute processing (normalization, defaulting, and reporting types including ID). This augmentation is reported through the StartDTD(String, String, String) method as if the document text had originally included the external subset; this callback is made before any internal subset data or errors are reported.

This method can also be used with documents that have no DOCTYPE declaration.When the root element is encountered, but no DOCTYPE declaration has been seen, this method is invoked.If it returns a value for the external subset, that root element is declared to be the root element, giving the effect of splicing a DOCTYPE declaration at the end the prolog of a document that could not otherwise be valid. The sequence of parser callbacks in that case logically resembles this: 

... comments and PIs from the prolog (as usual)
StartDTD("rootName", source.getPublicId (), source.getSystemId ());
StartEntity("[dtd]");
... declarations, comments, and PIs from the external subset
EndEntity("[dtd]");
EndDTD();
... then the rest of the document(as usual)
StartElement(..., "rootName", ...);

Note that the InputSource gets no further resolution. Implementations of this method may wish to invoke ResolveEntity(String, String, String, String) to gain benefits such as use of local caches of DTD entities.Also, this method will never be used by a (non - validating) processor that is not including external parameter entities.

Uses for this method include facilitating data validation when interoperating with XML processors that would always require undesirable network accesses for external entities, or which for other reasons adopt a "no DTDs" policy. Non - validation motives include forcing documents to include DTDs so that attributes are handled consistently. For example, an XPath processor needs to know which attibutes have type "ID" before it can process a widely used type of reference.

Warning: Returning an external subset modifies the input document.By providing definitions for general entities, it can make a malformed document appear to be well formed.
ResolveEntity(String, String, String, String)

Allows applications to map references to external entities into input sources, or tell the parser it should use conventional URI resolution. This method is only called for external entities which have been properly declared.

This method provides more flexibility than the IEntityResolver interface, supporting implementations of more complex catalogue schemes such as the one defined by theOASIS XML Catalogs specification.

Parsers configured to use this resolver method will call it to determine the input source to use for any external entity being included because of a reference in the XML text. That excludes the document entity, and any external entity returned by GetExternalSubset(String, String). When a(non - validating) processor is configured not to include a class of entities(parameter or general) through use of feature flags, this method is not invoked for such entities.

Note that the entity naming scheme used here is the same one used in the ILexicalHandler, or in the SkippedEntity(String) method.

Extension Methods

See Also