| <?xml version="1.0" standalone="no"?> |
| <!-- |
| * Licensed to the Apache Software Foundation (ASF) under one or more |
| * contributor license agreements. See the NOTICE file distributed with |
| * this work for additional information regarding copyright ownership. |
| * The ASF licenses this file to You under the Apache License, Version 2.0 |
| * (the "License"); you may not use this file except in compliance with |
| * the License. You may obtain a copy of the License at |
| * |
| * http://www.apache.org/licenses/LICENSE-2.0 |
| * |
| * Unless required by applicable law or agreed to in writing, software |
| * distributed under the License is distributed on an "AS IS" BASIS, |
| * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| * See the License for the specific language governing permissions and |
| * limitations under the License. |
| --> |
| |
| <!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd"> |
| |
| <s1 title="SAX Programming Guide"> |
| |
| <anchor name="UsingSAX1API"/> |
| <s2 title="Using the SAX API"> |
| <p>The SAX API for XML parsers was originally developed for |
| Java. Please be aware that there is no standard SAX API for |
| C++, and that use of the &XercesCName; SAX API does not |
| guarantee client code compatibility with other C++ XML |
| parsers.</p> |
| |
| <p>The SAX API presents a callback based API to the parser. An |
| application that uses SAX provides an instance of a handler |
| class to the parser. When the parser detects XML constructs, |
| it calls the methods of the handler class, passing them |
| information about the construct that was detected. The most |
| commonly used handler classes are DocumentHandler which is |
| called when XML constructs are recognized, and ErrorHandler |
| which is called when an error occurs. The header files for the |
| various SAX handler classes are in the <code>xercesc/sax/</code> |
| directory.</p> |
| |
| <p>As a convenience, &XercesCName; provides |
| HandlerBase, a single class which is publicly derived |
| from all the Handler classes. HandlerBase's default |
| implementation of the handler callback methods is to do |
| nothing. A convenient way to get started with &XercesCName; is |
| to derive your own handler class from HandlerBase and override |
| just those methods in HandlerBase which you are interested in |
| customizing. This simple example shows how to create a handler |
| which will print element names, and print fatal error |
| messages. The source code for the sample applications show |
| additional examples of how to write handler classes.</p> |
| |
| <p>This is the header file MySAXHandler.hpp:</p> |
| <source>#include <xercesc/sax/HandlerBase.hpp> |
| |
| class MySAXHandler : public HandlerBase { |
| public: |
| void startElement(const XMLCh* const, AttributeList&); |
| void fatalError(const SAXParseException&); |
| };</source> |
| |
| <p>This is the implementation file MySAXHandler.cpp:</p> |
| |
| <source>#include "MySAXHandler.hpp" |
| #include <iostream> |
| |
| using namespace std; |
| |
| MySAXHandler::MySAXHandler() |
| { |
| } |
| |
| void MySAXHandler::startElement(const XMLCh* const name, |
| AttributeList& attributes) |
| { |
| char* message = XMLString::transcode(name); |
| cout << "I saw element: "<< message << endl; |
| XMLString::release(&message); |
| } |
| |
| void MySAXHandler::fatalError(const SAXParseException& exception) |
| { |
| char* message = XMLString::transcode(exception.getMessage()); |
| cout << "Fatal Error: " << message |
| << " at line: " << exception.getLineNumber() |
| << endl; |
| XMLString::release(&message); |
| }</source> |
| |
| <p>The XMLCh and AttributeList types are supplied by |
| &XercesCName; and are documented in the API reference. |
| Examples of their usage appear in the source code for |
| the sample applications.</p> |
| </s2> |
| |
| <anchor name="SAXParser"/> |
| <s2 title="SAXParser"> |
| <anchor name="ConstructParser"/> |
| <s3 title="Constructing a SAXParser"> |
| <p>In order to use &XercesCName; SAX to parse XML files, you will |
| need to create an instance of the SAXParser class. The example |
| below shows the code you need in order to create an instance |
| of SAXParser. The DocumentHandler and ErrorHandler instances |
| required by the SAX API are provided using the HandlerBase |
| class supplied with &XercesCName;.</p> |
| |
| <source> |
| #include <xercesc/parsers/SAXParser.hpp> |
| #include <xercesc/sax/HandlerBase.hpp> |
| #include <xercesc/util/XMLString.hpp> |
| |
| #include <iostream> |
| |
| using namespace std; |
| using namespace xercesc; |
| |
| int main (int argc, char* args[]) { |
| |
| try { |
| XMLPlatformUtils::Initialize(); |
| } |
| catch (const XMLException& toCatch) { |
| char* message = XMLString::transcode(toCatch.getMessage()); |
| cout << "Error during initialization! :\n" |
| << message << "\n"; |
| XMLString::release(&message); |
| return 1; |
| } |
| |
| char* xmlFile = "x1.xml"; |
| SAXParser* parser = new SAXParser(); |
| parser->setDoValidation(true); |
| parser->setDoNamespaces(true); // optional |
| |
| DocumentHandler* docHandler = new HandlerBase(); |
| ErrorHandler* errHandler = (ErrorHandler*) docHandler; |
| parser->setDocumentHandler(docHandler); |
| parser->setErrorHandler(errHandler); |
| |
| try { |
| parser->parse(xmlFile); |
| } |
| catch (const XMLException& toCatch) { |
| char* message = XMLString::transcode(toCatch.getMessage()); |
| cout << "Exception message is: \n" |
| << message << "\n"; |
| XMLString::release(&message); |
| return -1; |
| } |
| catch (const SAXParseException& toCatch) { |
| char* message = XMLString::transcode(toCatch.getMessage()); |
| cout << "Exception message is: \n" |
| << message << "\n"; |
| XMLString::release(&message); |
| return -1; |
| } |
| catch (...) { |
| cout << "Unexpected Exception \n" ; |
| return -1; |
| } |
| |
| delete parser; |
| delete docHandler; |
| return 0; |
| }</source> |
| </s3> |
| |
| <anchor name="SAXFeatures"/> |
| <s3 title="SAXParser Supported Features"> |
| |
| <p>The behavior of the SAXParser is dependant on the values of the following features. All |
| of the features below are set using the "setter" methods (e.g. <code>setDoNamespaces</code>), |
| and are queried using the corresponding "getter" methods (e.g. <code>getDoNamespaces</code>). |
| The following only gives you a quick summary of supported features. Please |
| refer to <jump href="api-&XercesC3Series;.html">API Documentation</jump> for complete detail. |
| </p> |
| <p>None of these features can be modified in the middle of a parse, or an exception will be thrown.</p> |
| |
| |
| <anchor name="namespaces"/> |
| <table> |
| <tr><th colspan="2"><em>void setDoNamespaces(const bool)</em></th></tr> |
| <tr><th><em>true:</em></th><td> Perform Namespace processing. </td></tr> |
| <tr><th><em>false:</em></th><td> Do not perform Namespace processing. </td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| <tr><th><em>note:</em></th><td> If the validation scheme is set to Val_Always or Val_Auto, then the |
| document must contain a grammar that supports the use of namespaces. </td></tr> |
| <tr><th><em>see:</em></th><td> |
| <link anchor="validation-dynamic">setValidationScheme</link> |
| </td></tr> |
| </table> |
| <p/> |
| |
| <anchor name="validation-dynamic"/> |
| <table> |
| <tr><th colspan="2"><em>void setValidationScheme(const ValSchemes)</em></th></tr> |
| <tr><th><em>Val_Auto:</em></th><td> The parser will report validation errors only if a grammar is specified. </td></tr> |
| <tr><th><em>Val_Always:</em></th><td> The parser will always report validation errors. </td></tr> |
| <tr><th><em>Val_Never:</em></th><td> Do not report validation errors. </td></tr> |
| <tr><th><em>default:</em></th><td> Val_Never </td></tr> |
| <tr><th><em>note:</em></th><td> If set to Val_Always, the document must |
| specify a grammar. If this feature is set to Val_Never and document specifies a grammar, |
| that grammar might be parsed but no validation of the document contents will be |
| performed. </td></tr> |
| <tr><th><em>see:</em></th><td> |
| <link anchor="load-external-dtd">setLoadExternalDTD</link> |
| </td></tr> |
| </table> |
| |
| <p/> |
| |
| <anchor name="schema"/> |
| <table> |
| <tr><th colspan="2"><em>void setDoSchema(const bool)</em></th></tr> |
| <tr><th><em>true:</em></th><td> Enable the parser's schema support. </td></tr> |
| <tr><th><em>false:</em></th><td> Disable the parser's schema support. </td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| <tr><th><em>note</em></th><td> If set to true, namespace processing must also be turned on. </td></tr> |
| <tr><th><em>see:</em></th><td> |
| <link anchor="namespaces">setDoNamespaces</link> |
| </td></tr> |
| </table> |
| |
| <p/> |
| |
| <table> |
| <tr><th colspan="2"><em>void setValidationSchemaFullChecking(const bool)</em></th></tr> |
| <tr><th><em>true:</em></th><td> Enable full schema constraint checking, including checking |
| which may be time-consuming or memory intensive. Currently, particle unique |
| attribution constraint checking and particle derivation restriction checking |
| are controlled by this option. </td></tr> |
| <tr><th><em>false:</em></th><td> Disable full schema constraint checking. </td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| <tr><th><em>note:</em></th><td> This feature checks the Schema grammar itself for |
| additional errors that are time-consuming or memory intensive. It does <em>not</em> affect the |
| level of checking performed on document instances that use Schema grammars. </td></tr> |
| <tr><th><em>see:</em></th><td> |
| <link anchor="schema">setDoSchema</link> |
| </td></tr> |
| </table> |
| |
| <p/> |
| |
| <anchor name="load-schema"/> |
| <table> |
| <tr><th colspan="2"><em>void setLoadSchema(const bool)</em></th></tr> |
| <tr><th><em>true:</em></th><td> Load the schema. </td></tr> |
| <tr><th><em>false:</em></th><td> Don't load the schema if it wasn't found in the grammar pool. </td></tr> |
| <tr><th><em>default:</em></th><td> true </td></tr> |
| <tr><th><em>note:</em></th><td> This feature is ignored and no schemas are loaded if schema processing is disabled. </td></tr> |
| <tr><th><em>see:</em></th><td> |
| <link anchor="schema">setDoSchema</link> |
| </td></tr> |
| </table> |
| |
| <p/> |
| |
| <anchor name="load-external-dtd"/> |
| <table> |
| <tr><th colspan="2"><em>void setLoadExternalDTD(const bool)</em></th></tr> |
| <tr><th><em>true:</em></th><td> Load the External DTD. </td></tr> |
| <tr><th><em>false:</em></th><td> Ignore the external DTD completely. </td></tr> |
| <tr><th><em>default:</em></th><td> true </td></tr> |
| <tr><th><em>note</em></th><td> This feature is ignored and DTD is always loaded |
| if the validation scheme is set to Val_Always or Val_Auto. </td></tr> |
| <tr><th><em>see:</em></th><td> |
| <link anchor="validation-dynamic">setValidationScheme</link> |
| </td></tr> |
| </table> |
| |
| <p/> |
| |
| <anchor name="continue-after-fatal"/> |
| <table> |
| <tr><th colspan="2"><em>void setExitOnFirstFatalError(const bool)</em></th></tr> |
| <tr><th><em>true:</em></th><td> Stops parse on first fatal error. </td></tr> |
| <tr><th><em>false:</em></th><td> Attempt to continue parsing after a fatal error. </td></tr> |
| <tr><th><em>default:</em></th><td> true </td></tr> |
| <tr><th><em>note:</em></th><td> The behavior of the parser when this feature is set to |
| false is <em>undetermined</em>! Therefore use this feature with extreme caution because |
| the parser may get stuck in an infinite loop or worse. </td></tr> |
| </table> |
| |
| <p/> |
| |
| <table> |
| <tr><th colspan="2"><em>void setValidationConstraintFatal(const bool)</em></th></tr> |
| <tr><th><em>true:</em></th><td> The parser will treat validation error as fatal and will |
| exit depends on the state of |
| <link anchor="continue-after-fatal">setExitOnFirstFatalError</link>. |
| </td></tr> |
| <tr><th><em>false:</em></th><td> The parser will report the error and continue processing. </td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| <tr><th><em>note:</em></th><td> Setting this true does not mean the validation error will |
| be printed with the word "Fatal Error". It is still printed as "Error", but the parser |
| will exit if |
| <link anchor="continue-after-fatal">setExitOnFirstFatalError</link> |
| is set to true. </td></tr> |
| <tr><th><em>see:</em></th><td> |
| <link anchor="continue-after-fatal">setExitOnFirstFatalError</link> |
| </td></tr> |
| </table> |
| |
| <p/> |
| |
| <anchor name="use-cached"/> |
| <table> |
| <tr><th colspan="2"><em>void useCachedGrammarInParse(const bool)</em></th></tr> |
| <tr><th><em>true:</em></th><td>Use cached grammar if it exists in the pool.</td></tr> |
| <tr><th><em>false:</em></th><td>Parse the schema grammar.</td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| <tr><th><em>note:</em></th><td>The getter function for this method is called isUsingCachedGrammarInParse.</td></tr> |
| <tr><th><em>note:</em></th><td>If the grammar caching option is enabled, this option is set to true automatically |
| and any setting to this option by the user is a no-op.</td></tr> |
| <tr><th><em>see:</em></th><td> |
| <link anchor="cache-grammar">cacheGrammarFromParse</link> |
| </td></tr> |
| </table> |
| |
| <p/> |
| |
| <anchor name="cache-grammar"/> |
| <table> |
| <tr><th colspan="2"><em>void cacheGrammarFromParse(const bool)</em></th></tr> |
| <tr><th><em>true:</em></th><td>Cache the grammar in the pool for re-use in subsequent parses.</td></tr> |
| <tr><th><em>false:</em></th><td>Do not cache the grammar in the pool</td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| <tr><th><em>note:</em></th><td>The getter function for this method is called isCachingGrammarFromParse</td></tr> |
| <tr><th><em>note:</em></th><td> If set to true, the useCachedGrammarInParse |
| is also set to true automatically.</td></tr> |
| <tr><th><em>see:</em></th><td> |
| <link anchor="use-cached">useCachedGrammarInParse</link> |
| </td></tr> |
| </table> |
| |
| <p/> |
| |
| <anchor name="StandardUriConformant"/> |
| <table> |
| <tr><th colspan="2"><em>void setStandardUriConformant(const bool)</em></th></tr> |
| <tr><th><em>true:</em></th><td> Force standard uri conformance. </td></tr> |
| <tr><th><em>false:</em></th><td> Do not force standard uri conformance. </td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| <tr><th><em>note:</em></th><td> If set to true, malformed uri will be rejected |
| and fatal error will be issued. </td></tr> |
| </table> |
| <p/> |
| |
| <anchor name="CalculateSrcOffset"/> |
| <table> |
| <tr><th colspan="2"><em>void setCalculateSrcOfs(const bool)</em></th></tr> |
| <tr><th><em>true:</em></th><td> Enable src offset calculation. </td></tr> |
| <tr><th><em>false:</em></th><td> Disable src offset calculation. </td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| <tr><th><em>note:</em></th><td> If set to true, the user can inquire about |
| the current src offset within the input source. Setting it to false (default) |
| improves the performance.</td></tr> |
| </table> |
| <p/> |
| |
| <anchor name="IdentityConstraintChecking"/> |
| <table> |
| <tr><th colspan="2"><em>void setIdentityConstraintChecking(const bool);</em></th></tr> |
| <tr><th><em>true:</em></th><td> Enable identity constraint checking. </td></tr> |
| <tr><th><em>false:</em></th><td> Disable identity constraint checking. </td></tr> |
| <tr><th><em>default:</em></th><td> true </td></tr> |
| </table> |
| <p/> |
| |
| <anchor name="GenerateSyntheticAnnotations"/> |
| <table> |
| <tr><th colspan="2"><em>void setGenerateSyntheticAnnotations(const bool);</em></th></tr> |
| <tr><th><em>true:</em></th><td> Enable generation of synthetic annotations. A synthetic annotation will be |
| generated when a schema component has non-schema attributes but no child annotation. </td></tr> |
| <tr><th><em>false:</em></th><td> Disable generation of synthetic annotations. </td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| </table> |
| <p/> |
| |
| <anchor name="XercesValidateAnnotations"/> |
| <table> |
| <tr><th colspan="2"><em>setValidateAnnotation</em></th></tr> |
| <tr><th><em>true:</em></th><td> Enable validation of annotations. </td></tr> |
| <tr><th><em>false:</em></th><td> Disable validation of annotations. </td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| <tr><th><em>note:</em></th><td> Each annotation is validated independently. </td></tr> |
| </table> |
| <p/> |
| |
| <anchor name="IgnoreAnnotations"/> |
| <table> |
| <tr><th colspan="2"><em>setIgnoreAnnotations</em></th></tr> |
| <tr><th><em>true:</em></th><td> Do not generate XSAnnotations when traversing a schema.</td></tr> |
| <tr><th><em>false:</em></th><td> Generate XSAnnotations when traversing a schema.</td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| </table> |
| <p/> |
| |
| <anchor name="DisableDefaultEntityResolution"/> |
| <table> |
| <tr><th colspan="2"><em>setDisableDefaultEntityResolution</em></th></tr> |
| <tr><th><em>true:</em></th><td> The parser will not attempt to resolve the entity when the resolveEntity method returns NULL.</td></tr> |
| <tr><th><em>false:</em></th><td> The parser will attempt to resolve the entity when the resolveEntity method returns NULL.</td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| </table> |
| <p/> |
| |
| <anchor name="SkipDTDValidation"/> |
| <table> |
| <tr><th colspan="2"><em>setSkipDTDValidation</em></th></tr> |
| <tr><th><em>true:</em></th><td> When schema validation is on the parser will ignore the DTD, except for entities.</td></tr> |
| <tr><th><em>false:</em></th><td> The parser will not ignore DTDs when validating.</td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| <tr><th><em>see:</em></th><td> |
| <link anchor="schema">DoSchema</link></td></tr> |
| </table> |
| <p/> |
| |
| <anchor name="XercesIgnoreCachedDTD"/> |
| <table> |
| <tr><th colspan="2"><em>setIgnoreCachedDTD</em></th></tr> |
| <tr><th><em>true:</em></th><td> Ignore a cached DTD when an XML document contains both an |
| internal and external DTD, and the use cached grammar from parse option |
| is enabled. Currently, we do not allow using cached DTD grammar when an |
| internal subset is present in the document. This option will only affect |
| the behavior of the parser when an internal and external DTD both exist |
| in a document (i.e. no effect if document has no internal subset).</td></tr> |
| <tr><th><em>false:</em></th><td> Don't ignore cached DTD. </td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| <tr><th><em>see:</em></th><td> |
| <link anchor="use-cached">useCachedGrammarInParse</link></td></tr> |
| </table> |
| <p/> |
| |
| <anchor name="XercesHandleMultipleImports"/> |
| <table> |
| <tr><th colspan="2"><em>setHandleMultipleImports</em></th></tr> |
| <tr><th><em>true:</em></th><td> During schema validation allow multiple schemas with the same namespace |
| to be imported.</td></tr> |
| <tr><th><em>false:</em></th><td> Don't import multiple schemas with the same namespace. </td></tr> |
| <tr><th><em>default:</em></th><td> false </td></tr> |
| </table> |
| <p/> |
| |
| <table> |
| <tr><th colspan="2"><em>void setExternalSchemaLocation(const XMLCh* const)</em></th></tr> |
| <tr><th><em>Description</em></th><td> The XML Schema Recommendation explicitly states that |
| the inclusion of schemaLocation/ noNamespaceSchemaLocation attributes in the |
| instance document is only a hint; it does not mandate that these attributes |
| must be used to locate schemas. Similar situation happens to <import> |
| element in schema documents. This property allows the user to specify a list |
| of schemas to use. If the targetNamespace of a schema specified using this |
| method matches the targetNamespace of a schema occurring in the instance |
| document in schemaLocation attribute, or |
| if the targetNamespace matches the namespace attribute of <import> |
| element, the schema specified by the user using this property will |
| be used (i.e., the schemaLocation attribute in the instance document |
| or on the <import> element will be effectively ignored). </td></tr> |
| <tr><th><em>Value</em></th><td> The syntax is the same as for schemaLocation attributes |
| in instance documents: e.g, "http://www.example.com file_name.xsd". |
| The user can specify more than one XML Schema in the list. </td></tr> |
| <tr><th><em>Value Type</em></th><td> XMLCh* </td></tr> |
| </table> |
| |
| <p/> |
| <table> |
| <tr><th colspan="2"><em>void setExternalNoNamespaceSchemaLocation(const XMLCh* const)</em></th></tr> |
| <tr><th><em>Description</em></th><td> The XML Schema Recommendation explicitly states that |
| the inclusion of schemaLocation/ noNamespaceSchemaLocation attributes in the |
| instance document is only a hint; it does not mandate that these attributes |
| must be used to locate schemas. This property allows the user to specify the |
| no target namespace XML Schema Location externally. If specified, the instance |
| document's noNamespaceSchemaLocation attribute will be effectively ignored. </td></tr> |
| <tr><th><em>Value</em></th><td> The syntax is the same as for the noNamespaceSchemaLocation |
| attribute that may occur in an instance document: e.g."file_name.xsd". </td></tr> |
| <tr><th><em>Value Type</em></th><td> XMLCh* </td></tr> |
| </table> |
| |
| <p/> |
| |
| <table> |
| <tr><th colspan="2"><em>void useScanner(const XMLCh* const)</em></th></tr> |
| <tr><th><em>Description</em></th><td> This property allows the user to specify the name of |
| the XMLScanner to use for scanning XML documents. If not specified, the default |
| scanner "IGXMLScanner" is used.</td></tr> |
| <tr><th><em>Value</em></th><td> The recognized scanner names are: <br/> |
| 1."WFXMLScanner" - scanner that performs well-formedness checking only.<br/> |
| 2. "DGXMLScanner" - scanner that handles XML documents with DTD grammar information.<br/> |
| 3. "SGXMLScanner" - scanner that handles XML documents with XML schema grammar information.<br/> |
| 4. "IGXMLScanner" - scanner that handles XML documents with DTD or/and XML schema grammar information.<br/> |
| Users can use the predefined constants defined in XMLUni directly (fgWFXMLScanner, fgDGXMLScanner, |
| fgSGXMLScanner, or fgIGXMLScanner) or a string that matches the value of one of those constants.</td></tr> |
| <tr><th><em>Value Type</em></th><td> XMLCh* </td></tr> |
| <tr><th><em>note: </em></th><td> See <jump href="program-others-&XercesC3Series;.html#UseSpecificScanner">Use Specific Scanner</jump> |
| for more programming details. </td></tr> |
| </table> |
| |
| <p/> |
| |
| <table> |
| <tr><th |
| colspan="2"><em>setSecurityManager(Security Manager * const)</em></th></tr> |
| <tr><th><em>Description</em></th> |
| <td> |
| Certain valid XML and XML Schema constructs can force a |
| processor to consume more system resources than an |
| application may wish. In fact, certain features could |
| be exploited by malicious document writers to produce a |
| denial-of-service attack. This property allows |
| applications to impose limits on the amount of |
| resources the processor will consume while processing |
| these constructs. |
| </td></tr> |
| <tr><th><em>Value</em></th> |
| <td> |
| An instance of the SecurityManager class (see |
| <code>xercesc/util/SecurityManager</code>). This |
| class's documentation describes the particular limits |
| that may be set. Note that, when instantiated, default |
| values for limits that should be appropriate in most |
| settings are provided. The default implementation is |
| not thread-safe; if thread-safety is required, the |
| application should extend this class, overriding |
| methods appropriately. The parser will not adopt the |
| SecurityManager instance; the application is |
| responsible for deleting it when it is finished with |
| it. If no SecurityManager instance has been provided to |
| the parser (the default) then processing strictly |
| conforming to the relevant specifications will be |
| performed. |
| </td></tr> |
| <tr><th><em>Value Type</em></th><td> SecurityManager* </td></tr> |
| </table> |
| |
| <p/> |
| |
| <table> |
| <tr><th |
| colspan="2"><em>setLowWaterMark(XMLSize_t)</em></th></tr> |
| <tr><th><em>Description</em></th> |
| <td> |
| If the number of available bytes in the raw buffer is less than |
| the low water mark the parser will attempt to read more data before |
| continuing parsing. By default the value for this parameter is 100 |
| bytes. You may want to set this parameter to 0 if you would like |
| the parser to parse the available data immediately without |
| potentially blocking while waiting for more date. |
| </td></tr> |
| <tr><th><em>Value</em></th> |
| <td> |
| New low water mark. |
| </td></tr> |
| <tr><th><em>Value Type</em></th><td> XMLSize_t </td></tr> |
| </table> |
| |
| <p/> |
| |
| <table> |
| <tr><th |
| colspan="2"><em>setInputBufferSize(const size_t bufferSize)</em></th></tr> |
| <tr><th><em>Description</em></th> |
| <td> |
| Set maximum input buffer size. |
| This method allows users to limit the size of buffers used in parsing |
| XML character data. The effect of setting this size is to limit the |
| size of a ContentHandler::characters() call. |
| The parser's default input buffer size is 1 megabyte. |
| </td></tr> |
| <tr><th><em>Value</em></th> |
| <td> |
| The maximum input buffer size |
| </td></tr> |
| <tr><th><em>Value Type</em></th><td> XMLCh* </td></tr> |
| </table> |
| <p/> |
| </s3> |
| </s2> |
| |
| </s1> |