Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This method receives notification of an unparsed entity declaration event. The notation name corresponds to a notation reported by the notationDeclevent. It is up to the application to record the entity for later reference, if necessary. If the system identifier is a URL, the reader must resolve it before passing it to the application.

Syntax

HRESULT unparsedEntityDecl(
  const wchar_t* 
pwchName, 
	int 
cchName, 
  const wchar_t* 
pwchPublicId, 
  int 
cchPublicId,
  const wchar_t* 
pwchSystemId,
  int 
cchSystemId,
  const wchar_t* 
pwchNotationName,
  int 
cchNotationName
);

Parameters

pwchName

[in] Pointer to the unparsed entity's name.

cchName

[in] Length of the entity.

pwchPublicId

[in] Pointer to the entity's public identifier or NULL (if none was given).

cchPublicId

[in] Length of the public identifier.

pwchSystemId

[in] Pointer to the entity's system identifier (required).

cchSystemId

[in] Length of the system identifier.

pwchNotationName

[in] Pointer to the name of the associated notation.

cchNotationName

[in] Length of the notation.

Return Value

S_OK

Returned if no errors occur.

E_FAIL

Returned if the parse should be aborted.

Requirements

Header msxml2.h, msxml2.idl
Library uuid.lib
Windows Embedded CE Windows CE .NET 4.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.