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

Quick Search    Search Deep

gnu.xml.aelfred2.* (5)gnu.xml.dom.* (107)gnu.xml.libxmlj.* (45)gnu.xml.pipeline.* (13)
gnu.xml.stream.* (34)gnu.xml.transform.* (53)gnu.xml.util.* (7)gnu.xml.validation.* (112)
gnu.xml.xpath.* (56)

Package Samples:

gnu.xml.dom.ls: This is a Free Software DOM Level 3 implementation, supporting these features: "XML" "Events" "MutationEvents" "HTMLEvents" (won't generate them though) "UIEvents" (also won't generate them) "USER-Events" (a conformant extension) "Traversal" (optional) "XPath" "LS" and "LS-Async" It is intended to be a reasonable base both for experimentation and supporting additional DOM modules as clean layers.  
gnu.xml.dom.html2: This is a Free Software DOM Level 3 implementation, supporting these features: "XML" "Events" "MutationEvents" "HTMLEvents" (won't generate them though) "UIEvents" (also won't generate them) "USER-Events" (a conformant extension) "Traversal" (optional) "XPath" "LS" and "LS-Async" It is intended to be a reasonable base both for experimentation and supporting additional DOM modules as clean layers.  
gnu.xml.aelfred2
gnu.xml.dom
gnu.xml.libxmlj.dom
gnu.xml.libxmlj.sax
gnu.xml.libxmlj.transform
gnu.xml.libxmlj.util
gnu.xml.pipeline
gnu.xml.transform
gnu.xml.util
gnu.xml.xpath
gnu.xml.libxmlj
gnu.xml.validation.datatype
gnu.xml.validation.xmlschema
gnu.xml.stream
gnu.xml.validation.relaxng

Classes:

PipelineFactory: This provides static factory methods for creating simple event pipelines. These pipelines are specified by strings, suitable for passing on command lines or embedding in element attributes. For example, one way to write a pipeline that restores namespace syntax, validates (stopping the pipeline on validity errors) and then writes valid data to standard output is this: nsfix | validate | write ( stdout ) In this syntax, the tokens are always separated by whitespace, and each stage of the pipeline may optionally have a parameter (which can be a pipeline) in parentheses. Interior stages are called ...
ValidationConsumer: This class checks SAX2 events to report validity errors; it works as both a filter and a terminus on an event pipeline. It relies on the producer of SAX events to: Conform to the specification of a non-validating XML parser that reads all external entities, reported using SAX2 events. Report ignorable whitespace as such (through the ContentHandler interface). This is, strictly speaking, optional for nonvalidating XML processors. Make SAX2 DeclHandler callbacks, with default attribute values already normalized (and without "<"). Make SAX2 LexicalHandler startDTD() and endDTD () callbacks. Act ...
EventFilter: A customizable event consumer, used to assemble various kinds of filters using SAX handlers and an optional second consumer. It can be constructed in two ways: To serve as a passthrough, sending all events to a second consumer. The second consumer may be identified through getNext() 55 . To serve as a dead end, with all handlers null; getNext() 55 returns null. Additionally, SAX handlers may be assigned, which completely replace the "upstream" view (through EventConsumer ) of handlers, initially null or the "next" consumer provided to the constructor. To make it easier to build specialized filter ...
XCat: Packages OASIS XML Catalogs , primarily for entity resolution by parsers. That specification defines an XML syntax for mappings between identifiers declared in DTDs (particularly PUBLIC identifiers) and locations. SAX has always supported such mappings, but conventions for an XML file syntax to maintain them have previously been lacking. This has three main operational modes. The primary intended mode is to create a resolver, then preloading it with one or more site-standard catalogs before using it with one or more SAX parsers: XCat catalog = new XCat (); catalog.setErrorHandler (diagnosticErrorHandler); ...
DomParser: This parser emits SAX2 parsing events as it traverses a DOM tree, using any conformant implementation of DOM. It exposes all SAX1 features, and the following SAX2 features and properties (as identified by standard URIs which are not fully provided here). Note that if a Level 1 DOM implementation is given, then this behaves as if namespaces were disabled, and namespace prefixes were enabled. Name Notes Features ... URL prefix is http://xml.org/sax/features/ (URL)/external-general-entities false (does no parsing) (URL)/external-parameter-entities false (does no parsing) (URL)/namespaces Value is ...
XMLWriter: This class is a SAX handler which writes all its input as a well formed XML or XHTML document. If driven using SAX2 events, this output may include a recreated document type declaration, subject to limitations of SAX (no internal subset exposed) or DOM (the important declarations, with their documentation, are discarded). By default, text is generated "as-is", but some optional modes are supported. Pretty-printing is supported, to make life easier for people reading the output. XHTML (1.0) output has can be made particularly pretty; all the built-in character entities are known. Canonical XML can ...
DomConsumer: This consumer builds a DOM Document from its input, acting either as a pipeline terminus or as an intermediate buffer. When a document's worth of events has been delivered to this consumer, that document is read with a gnu.xml.util.DomParser and sent to the next consumer. It is also available as a read-once property. The DOM tree is constructed as faithfully as possible. There are some complications since a DOM should expose behaviors that can't be implemented without API backdoors into that DOM, and because some SAX parsers don't report all the information that DOM permits to be exposed. The general ...
CallFilter: Input is sent as an XML request to given URI, and the output of this filter is the parsed response to that request. A connection is opened to the remote URI when the startDocument call is issued through this filter, and the request is finished when the endDocument call is issued. Events should be written quickly enough to prevent the remote HTTP server from aborting the connection due to inactivity; you may want to buffer text in an earlier pipeline stage. If your application requires validity checking of such outputs, have the output pipeline include a validation stage. In effect, this makes a ...
SAXDriver: An enhanced SAX2 version of Microstar's Ælfred XML parser. The enhancements primarily relate to significant improvements in conformance to the XML specification, and SAX2 support. Performance has been improved. See the package level documentation for more information. Name Notes Features ... URL prefix is http://xml.org/sax/features/ (URL)/external-general-entities Value defaults to true (URL)/external-parameter-entities Value defaults to true (URL)/is-standalone (PRELIMINARY) Returns true iff the document's parsing has started (some non-error event after startDocument() was reported) and ...
NSFilter: This filter ensures that element and attribute names are properly prefixed, and that such prefixes are declared. Such data is critical for operations like writing XML text, and validating against DTDs: names or their prefixes may have been discarded, although they are essential to the exchange of information using XML. There are various common ways that such data gets discarded: By default, SAX2 parsers must discard the "xmlns*" attributes, and may also choose not to report properly prefixed names for elements or attributes. (Some parsers may support changing the namespace-prefixes value from the ...
SAXNullTransformerFactory: Implements null transforms. XSLT stylesheets are not supported. This class provides a way to translate three representations of XML data (SAX event stream, DOM tree, and XML text) into each other. In essence it's a thinnish wrapper around basic SAX event pipeline facilities, which exposes only limited functionality. The javax.xml.transform functionality is implemented as follows: The SAXSource class just wraps an org.xml.sax.XMLReader and org.xml.sax.InputSource , while the SAXResult class is less functional than a EventConsumer . (Notably, it drops all but one declaration from any DTD.) The DOMSource ...
DoParse: This class provides a driver which may be invoked from the command line to process a document using a SAX2 parser and a specified XML processing pipeline. This facilitates some common types of command line tools, such as parsing an XML document in order test it for well formedness or validity. The SAX2 XMLReaderFactory should return a SAX2 XML parser which supports both of the standardized extension handlers (for declaration and lexical events). That parser will be used to produce events. The first parameter to the command gives the name of the document that will be given to that processor. If ...
StringFunction: The string function converts an object to a string as follows: A node-set is converted to a string by returning the string-value of the node in the node-set that is first in document order. If the node-set is empty, an empty string is returned. A number is converted to a string as follows NaN is converted to the string NaN positive zero is converted to the string 0 negative zero is converted to the string 0 positive infinity is converted to the string Infinity negative infinity is converted to the string -Infinity if the number is an integer, the number is represented in decimal form as a Number ...
XIncludeFilter: Filter to process an XPointer-free subset of XInclude , supporting its use as a kind of replacement for parsed general entities. XInclude works much like the #include of C/C++ but works for XML documents as well as unparsed text files. Restrictions from the 17-Sept-2002 CR draft of XInclude are as follows: URIs must not include fragment identifiers. The CR specifies support for XPointer element() fragment IDs, which is not currently implemented here. xi:fallback handling of resource errors is not currently supported. DTDs are not supported in included files, since the SAX DTD events must have completely ...
DomNode: "Node", "EventTarget", and "DocumentEvent" implementation. This provides most of the core DOM functionality; only more specialized features are provided by subclasses. Those subclasses may have some particular constraints they must implement, by overriding methods defined here. Such constraints are noted here in the method documentation. Note that you can create events with type names prefixed with "USER-", and pass them through this DOM. This lets you use the DOM event scheme for application specific purposes, although you must use a predefined event structure (such as MutationEvent) to pass data ...
DomEntityReference: "EntityReference" implementation (reference to parsed entity). This is a non-core DOM class, supporting the "XML" feature. It does not represent builtin entities (such as "&") or character references, which are always directly expanded in DOM trees. Note that while the DOM specification permits these nodes to have a readonly set of children, this is not required. Similarly, it does not require a DOM to couple EntityReference nodes with any Entity nodes that have the same entity name (and equivalent children). It also effectively guarantees that references created directly or indirectly ...
DomAttr: "Attr" implementation. In DOM, attributes cost quite a lot of memory because their values are complex structures rather than just simple strings. To reduce your costs, avoid having more than one child of an attribute; stick to a single Text node child, and ignore even that by using the attribute's "nodeValue" property. As a bit of general advice, only look at attribute modification events through the DOMAttrModified event (sent to the associated element). Implementations are not guaranteed to report other events in the same order, so you're very likely to write nonportable code if you monitor events ...
DomDoctype: "DocumentType" implementation (with no extensions for supporting any document typing information). This is a non-core DOM class, supporting the "XML" feature. Few XML applications will actually care about this partial DTD support , since it doesn't expose any (!) of the data typing facilities which can motivate applications to use DTDs. It does not expose element content models, or information about attribute typing rules. Plus the information it exposes isn't very useful; as one example, DOM exposes information about unparsed ENTITY objects, which is only used with certain element attributes, ...
Consumer: Event consumer which constructs DOM documents using the implementation in this package, using SAX2 events. This packages various backdoors into this DOM implementation, as needed to address DOM requirements that can't be met by strictly conforming implementations of DOM. These requirements all relate to org.w3c.dom.DocumentType nodes and features of that node type. These features are normally not used, because that interface only exposes a subset of the information found in DTDs. More, that subset does not include the most important typing information. For example, it excludes element content models ...
WellFormednessFilter: This filter reports fatal exceptions in the case of event streams that are not well formed. The rules currently tested include: setDocumentLocator ... may be called only before startDocument startDocument/endDocument ... must be paired, and all other calls (except setDocumentLocator) must be nested within these. startElement/endElement ... must be correctly paired, and may never appear within CDATA sections. comment ... can't contain "--" character data ... can't contain "]]>" whitespace ... can't contain CR whitespace and character data must be within an element processing instruction ... can't ...
XmlReader: This SAX2 parser optionally layers a validator over the Ælfred2 SAX2 parser. While this will not evaluate every XML validity constraint, it does support all the validity constraints that are of any real utility outside the strict SGML-compatible world. See the documentation for the SAXDriver class for information about the SAX2 features and properties that are supported, and documentation for the ValidationConsumer for information about what validity constraints may not be supported. (Ælfred2 tests some of those, even in non-validating mode, to achieve better conformance.) Note that ...
NameFunction: The name function returns a string containing a QName representing the expanded-name of the node in the argument node-set that is first in document order. The QName must represent the expanded-name with respect to the namespace declarations in effect on the node whose expanded-name is being represented. Typically, this will be the QName that occurred in the XML source. This need not be the case if there are namespace declarations in effect on the node that associate multiple prefixes with the same namespace. However, an implementation may include information about the original prefix in its representation ...
DomEntity: "Entity" implementation. This is a non-core DOM class, supporting the "XML" feature. There are two types of entities, neither of which works particularly well in this API: Unparsed Entities Since ENTITY/ENTITIES attributes, the only legal use of unparsed entities in XML, can't be detected with DOM, there isn't much point in trying to use unparsed entities in DOM applications. (XML Linking is working to provide a better version of this functionality.) Parsed Entities While the DOM specification permits nodes for parsed entities to have a readonly set of children, this is not required and there is ...
EventConsumer: Collects the event consumption apparatus of a SAX pipeline stage. Consumers which permit some handlers or other characteristics to be configured will provide methods to support that configuration. Two important categories of consumers include filters , which process events and pass them on to other consumers, and terminus (or terminal ) stages, which don't pass events on. Filters are not necessarily derived from the EventFilter class, although that class can substantially simplify their construction by automating the most common activities. Event consumers which follow certain conventions for the ...

Home | Contact Us | Privacy Policy | Terms of Service