org.w3c.dom.ls

Interface LSOutput

Contents

  • public interface 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 DOMImplementationLS.createLSOutput() to create objects that implement this interface.

    The LSSerializer will use the LSOutput object to determine where to serialize the output to. The LSSerializer will look at the different outputs specified in the LSOutput in the following order to know which one to output to, the first one that is not null and not an empty string will be used:

    1. LSOutput.characterStream
    2. LSOutput.byteStream
    3. LSOutput.systemId

    LSOutput objects belong to the application. The DOM implementation will never modify them (though it may make copies and modify the copies, if necessary).

    See also the Document Object Model (DOM) Level 3 Load and Save Specification.

    • Method Detail

      • getCharacterStream

        Writer getCharacterStream()
        An attribute of a language and binding dependent type that represents a writable stream to which 16-bit units can be output.

      • setCharacterStream

        void setCharacterStream(Writer characterStream)
        An attribute of a language and binding dependent type that represents a writable stream to which 16-bit units can be output.

      • getByteStream

        OutputStream getByteStream()
        An attribute of a language and binding dependent type that represents a writable stream of bytes.

      • setByteStream

        void setByteStream(OutputStream byteStream)
        An attribute of a language and binding dependent type that represents a writable stream of bytes.

      • getSystemId

        String getSystemId()
        The system identifier, a URI reference [IETF RFC 2396], for this output destination.
        If the system ID is a relative URI reference (see section 5 in [IETF RFC 2396]), the behavior is implementation dependent.

      • setSystemId

        void setSystemId(String systemId)
        The system identifier, a URI reference [IETF RFC 2396], for this output destination.
        If the system ID is a relative URI reference (see section 5 in [IETF RFC 2396]), the behavior is implementation dependent.

      • getEncoding

        String getEncoding()
        The character encoding to use for the output. The encoding must be a string acceptable for an XML encoding declaration ([XML 1.0] section 4.3.3 "Character Encoding in Entities"), it is recommended that character encodings registered (as charsets) with the Internet Assigned Numbers Authority [IANA-CHARSETS] should be referred to using their registered names.

      • setEncoding

        void setEncoding(String encoding)
        The character encoding to use for the output. The encoding must be a string acceptable for an XML encoding declaration ([XML 1.0] section 4.3.3 "Character Encoding in Entities"), it is recommended that character encodings registered (as charsets) with the Internet Assigned Numbers Authority [IANA-CHARSETS] should be referred to using their registered names.

Document created the 11/06/2005, last modified the 04/03/2020
Source of the printed document:https://www.gaudry.be/en/java-api-rf-org/w3c/dom/ls/LSOutput.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:fr Manuel PHP : https://docs.oracle.com

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut