Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep
Home >> All >> org >> w3c >> dom >> [ ls Javadoc ]

• org.w3c.dom.ls: Javadoc index of package org.w3c.dom.ls.


Package Samples:

• org.w3c.dom.ls: This package contains the DOM Level 3 Core interfaces.  

Classes:

• LSSerializer: A LSSerializer provides an API for serializing (writing) a DOM document out into XML. The XML data is written to a string or an output stream. Any changes or fixups made during the serialization affect only the serialized data. The Document object and its children are never altered by the serialization operation. During serialization of XML data, namespace fixup is done as defined in [ DOM Level 3 Core ] , Appendix B. [ DOM Level 2 Core ] allows empty strings as a real namespace URI. If the namespaceURI of a Node is empty string, the serialization will treat them as null , ignoring the prefix if ...
• LSParser: An interface to an object that is able to build, or augment, a DOM tree from various input sources. LSParser provides an API for parsing XML and building the corresponding DOM document structure. A LSParser instance can be obtained by invoking the DOMImplementationLS.createLSParser() method. As specified in [ DOM Level 3 Core ] , when a document is first made available via the LSParser: there will never be two adjacent nodes of type NODE_TEXT, and there will never be empty text nodes. it is expected that the value and nodeValue attributes of an Attr node initially return the XML 1.0 normalized ...
• LSParserFilter: LSParserFilter s provide applications the ability to examine nodes as they are being constructed while parsing. As each node is examined, it may be modified or removed, or the entire parse may be terminated early. At the time any of the filter methods are called by the parser, the owner Document and DOMImplementation objects exist and are accessible. The document element is never passed to the LSParserFilter methods, i.e. it is not possible to filter out the document element. Document , DocumentType , Notation , Entity , and Attr nodes are never passed to the acceptNode method on the filter. The ...
• LSInput: This interface represents an input source for data. This interface allows an application to encapsulate information about an input source in a single object, which may include a public identifier, a system identifier, a byte stream (possibly with a specified encoding), a base URI, and/or a character stream. The exact definitions of a byte stream and a character stream are binding dependent. The application is expected to provide objects that implement this interface whenever such objects are needed. The application can either provide its own objects that implement this interface, or it can use ...
• LSSerializerFilter: LSSerializerFilter s provide applications the ability to examine nodes as they are being serialized and decide what nodes should be serialized or not. The LSSerializerFilter interface is based on the NodeFilter interface defined in [ DOM Level 2 Traversal and Range ] . Document , DocumentType , DocumentFragment , Notation , Entity , and children of Attr nodes are not passed to the filter. The child nodes of an EntityReference node are only passed to the filter if the EntityReference node is skipped by the method LSParserFilter.acceptNode() . When serializing an Element , the element is passed to ...
• LSOutput: This interface represents an output destination for data. This interface allows an application to encapsulate information about an output destination in a single object, which may include a URI, a byte stream (possibly with a specified encoding), a base URI, and/or a character stream. The exact definitions of a byte stream and a character stream are binding dependent. The application is expected to provide objects that implement this interface whenever such objects are needed. The application can either provide its own objects that implement this interface, or it can use the generic factory method ...
• LSResourceResolver: LSResourceResolver provides a way for applications to redirect references to external resources. Applications needing to implement custom handling for external resources can implement this interface and register their implementation by setting the "resource-resolver" parameter of DOMConfiguration objects attached to LSParser and LSSerializer . It can also be register on DOMConfiguration objects attached to Document if the "LS" feature is supported. The LSParser will then allow the application to intercept any external entities, including the external DTD subset and external parameter entities, ...
• DOMImplementationLS: DOMImplementationLS contains the factory methods for creating Load and Save objects. The expectation is that an instance of the DOMImplementationLS interface can be obtained by using binding-specific casting methods on an instance of the DOMImplementation interface or, if the Document supports the feature "Core" version "3.0" defined in [ DOM Level 3 Core ] , by using the method DOMImplementation.getFeature with parameter values "LS" (or "LS-Async" ) and "3.0" (respectively). See also the Document Object Model (DOM) Level 3 Load and Save Specification .
• LSException: Parser or write operations may throw an LSException if the processing is stopped. The processing can be stopped due to a DOMError with a severity of DOMError.SEVERITY_FATAL_ERROR or a non recovered DOMError.SEVERITY_ERROR , or if DOMErrorHandler.handleError() returned false . Note: As suggested in the definition of the constants in the DOMError interface, a DOM implementation may choose to continue after a fatal error, but the resulting DOM tree is then implementation dependent. See also the Document Object Model (DOM) Level 3 Load and Save Specification .
• LSProgressEvent: This interface represents a progress event object that notifies the application about progress as a document is parsed. It extends the Event interface defined in [ DOM Level 3 Events ] . The units used for the attributes position and totalSize are not specified and can be implementation and input dependent. See also the Document Object Model (DOM) Level 3 Load and Save Specification .
• LSLoadEvent: This interface represents a load event object that signals the completion of a document load. See also the Document Object Model (DOM) Level 3 Load and Save Specification .

Home | Contact Us | Privacy Policy | Terms of Service