Org.Xml.Sax.Ext.ILexicalHandler.StartEntity Method
Report the beginning of some internal and external XML entities.

Syntax

[Android.Runtime.Register("startEntity", "(Ljava/lang/String;)V", "GetStartEntity_Ljava_lang_String_Handler:Org.Xml.Sax.Ext.ILexicalHandlerInvoker, Mono.Android, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null")]
public void StartEntity (string name)

See Also

ILexicalHandler.EndEntity(string)
IDeclHandler.InternalEntityDecl(string, System.String)
IDeclHandler.ExternalEntityDecl(string, System.String, System.String)

Parameters

name
The name of the entity. If it is a parameter entity, the name will begin with '%', and if it is the external DTD subset, it will be "[dtd]".

Exceptions

TypeReason
Org.Xml.Sax.SAXExceptionThe application may raise an exception.

Remarks

Report the beginning of some internal and external XML entities.

The reporting of parameter entities (including the external DTD subset) is optional, and SAX2 drivers that report LexicalHandler events may not implement it; you can use the http://xml.org/sax/features/lexical-handler/parameter-entities feature to query or control the reporting of parameter entities.

General entities are reported with their regular names, parameter entities have '%' prepended to their names, and the external DTD subset has the pseudo-entity name "[dtd]".

When a SAX2 driver is providing these events, all other events must be properly nested within start/end entity events. There is no additional requirement that events from Org.Xml.Sax.Ext.IDeclHandler or Org.Xml.Sax.IDTDHandler be properly ordered.

Note that skipped entities will be reported through the Org.Xml.Sax.IContentHandler.SkippedEntity(string) event, which is part of the ContentHandler interface.

Because of the streaming event model that SAX uses, some entity boundaries cannot be reported under any circumstances:

  • general entities within attribute values
  • parameter entities within declarations

These will be silently expanded, with no indication of where the original entity boundaries were.

Note also that the boundaries of character references (which are not really entities anyway) are not reported.

All start/endEntity events must be properly nested.

[Android Documentation]

Requirements

Namespace: Org.Xml.Sax.Ext
Assembly: Mono.Android (in Mono.Android.dll)
Assembly Versions: 0.0.0.0
Since: Added in API level 1