|
|||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||
See:
Description
| Interface Summary | |
| AttributeMap | Similar to the Attributes interface in SAX. |
| AttributeMap.Pair | Represents a single attribute as a name-value pair. |
| ContentHandler | Receives notification of the logical content of a document. |
| HTMLParser | This interface is intended to provide limited support for templating in the context of CMS and similar applications, where users are expected to submit HTML that may have custom tags that have to be processed programmaticaly. |
| Class Summary | |
| AttributeMapImpl | An implementation of the AttributeMap interface. |
| HTMLlat1 | Defines Character entity references for ISO 8859-1 characters. |
| HTMLParserFactory | Different projects may need different HTML parsers. |
| HTMLspec | Defines Character entity references for markup-significant and internationalization characters. |
| HTMLsym | Defines Character entity references for symbols, mathematical symbols, and Greek letters. |
| StringTemplate | A utility class to make it easier to read Java code that generates HTML. |
| XHTMLParser | A SAX-based implementation of HTMLParser. |
| Exception Summary | |
| HTMLParserConfigurationException | Encapsulates a configuration error. |
| HTMLParserException | Encapsulates a general html parser error or warning. |
This package provides facilities for implementing little
HTML-like markup languages that extend HTML. See HTMLParser and com.arsdigita.templating.html.demo for concrete examples.
Conceptually, the package revolves around two interfaces:
HTMLParser and ContentHandler. An html parser can read
HTML text and dispatch events to the content handler. The
content handler may then process custom tags in a useful
manner.
At this time, the package only provides a single implementation
of the HTMLParser
interface, namely, the XHTMLParser class that relies on
a SAX parser to perform the actual parsing.
One example implementation of the ContentHandler is provided by
DemoTagHandler.
Another possible implementation of the ContentHandler interface would be a
class that "understands" custom "link" tags of the following form:
<p>As we mentioned in our <link cms_id="23889">previous article</link>,
serious Java practitioner tend to shun the
<a href="http://www.google.com/search?q=double-checked+locking">Double-Checked
Locking</a> pattern...
where the <link> tag may be used to link one
CMS article to another.
|
|||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||