Java Doc for HTMLSerializer.java in  » Portal » uPortal_rel-2-6-1-GA » org » jasig » portal » serialize » Java Source Code / Java DocumentationJava Source Code and Java Documentation

If an output stream is used, the encoding is taken from the output format (defaults to UTF-8). If a writer is used, make sure the writer uses the same encoding (if applies) as specified in the output format.

The serializer supports both DOM and SAX. DOM serializing is done by calling HTMLSerializer.serialize and SAX serializing is done by firing SAX events and using the serializer as a document handler.

If an I/O exception occurs while serializing, the serializer will not throw an exception directly, but only throw it at the end of serializing (either DOM or SAX's org.xml.sax.DocumentHandler.endDocument .

For elements that are not specified as whitespace preserving, the serializer will potentially break long text lines at space boundaries, indent lines, and serialize elements on separate lines. Line terminators will be regarded as spaces, and spaces at beginning of line will be stripped.

XHTML is slightly different than HTML:

• Element/attribute names are lower case and case matters
• Attributes must specify value, even if empty string
• Empty elements must have '/' in empty tag
• Contents of SCRIPT and STYLE elements serialized as CDATA

This method will check if it has not been called before ( HTMLSerializer._started ), will serialize the document type declaration, and will serialize all pre-root comments and PIs that were accumulated in the document (see HTMLSerializer.serializePreRoot ).

This method will check if it has not been called before ( HTMLSerializer._started ), will serialize the document type declaration, and will serialize all pre-root comments and PIs that were accumulated in the document (see HTMLSerializer.serializePreRoot ). Pre-root will be serialized even if this is not the first root element of the document.