1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
// -*- C++ -*-
//=============================================================================
/**
* @file EntityResolver.h
*
* @author Nanbor Wang <nanbor@cs.wustl.edu>
*/
//=============================================================================
#ifndef _ACEXML_ENTITYHANDLER_H_
#define _ACEXML_ENTITYHANDLER_H_
#include /**/ "ace/pre.h"
#include "ACEXML/common/ACEXML_Export.h"
#if !defined (ACE_LACKS_PRAGMA_ONCE)
#pragma once
#endif /* ACE_LACKS_PRAGMA_ONCE */
#include "ACEXML/common/InputSource.h"
#include "ACEXML/common/SAXExceptions.h"
/**
* @class ACEXML_EntityResolver
*
* @brief ACEXML_EntityResolver
*
* If a SAX application needs to implement customized handling for
* external entities, it must implement this interface and register an
* instance with the SAX driver using the setEntityResolver method.
*
* The XML reader will then allow the application to intercept any
* external entities (including the external DTD subset and external
* parameter entities, if any) before including them.
*
* Many SAX applications will not need to implement this interface,
* but it will be especially useful for applications that build XML
* documents from databases or other specialised input sources, or for
* applications that use URI types other than URLs.
*/
class ACEXML_Export ACEXML_EntityResolver
{
public:
virtual ~ACEXML_EntityResolver ();
/**
* Allow the application to resolve external entities.
*/
virtual ACEXML_InputSource *resolveEntity (const ACEXML_Char *publicId,
const ACEXML_Char *systemId) = 0;
};
#include /**/ "ace/post.h"
#endif /* _ACEXML_ENTITYHANDLER_H_ */
|
