By separating the configuration of a parser from the specific parser instance, applications can create new configurations and re-use the existing parser components and external API generators (e.g. the DOMParser and SAXParser).
The internals of any specific parser configuration instance are hidden. Therefore, each configuration may implement the parsing mechanism any way necessary. However, the parser configuration should follow these guidelines:
reset
method on each component before parsing. This is only required if the configuration is re-using existing components that conform to the XMLComponent
interface. If the configuration uses all custom parts, then it is free to implement everything as it sees fit as long as it follows the other guidelines. setFeature
and setProperty
method on each component during parsing to propagate features and properties that have changed. This is only required if the configuration is re-using existing components that conform to the XMLComponent
interface. If the configuration uses all custom parts, then it is free to implement everything as it sees fit as long as it follows the other guidelines. By separating the configuration of a parser from the specific parser instance, applications can create new configurations and re-use the existing parser components and external API generators (e.g. the DOMParser and SAXParser).
The internals of any specific parser configuration instance are hidden. Therefore, each configuration may implement the parsing mechanism any way necessary. However, the parser configuration should follow these guidelines:
reset
method on each component before parsing. This is only required if the configuration is re-using existing components that conform to the XMLComponent
interface. If the configuration uses all custom parts, then it is free to implement everything as it sees fit as long as it follows the other guidelines. setFeature
and setProperty
method on each component during parsing to propagate features and properties that have changed. This is only required if the configuration is re-using existing components that conform to the XMLComponent
interface. If the configuration uses all custom parts, then it is free to implement everything as it sees fit as long as it follows the other guidelines. By separating the configuration of a parser from the specific parser instance, applications can create new configurations and re-use the existing parser components and external API generators (e.g. the DOMParser and SAXParser).
The internals of any specific parser configuration instance are hidden. Therefore, each configuration may implement the parsing mechanism any way necessary. However, the parser configuration should follow these guidelines:
reset
method on each component before parsing. This is only required if the configuration is re-using existing components that conform to the XMLComponent
interface. If the configuration uses all custom parts, then it is free to implement everything as it sees fit as long as it follows the other guidelines. setFeature
and setProperty
method on each component during parsing to propagate features and properties that have changed. This is only required if the configuration is re-using existing components that conform to the XMLComponent
interface. If the configuration uses all custom parts, then it is free to implement everything as it sees fit as long as it follows the other guidelines.
|
|