All Packages from org.merlotxml.util.xml.* to org.merlotxml.util.xml.xml4j.*

Home >> All >> org >> merlotxml >> [ util Javadoc ]

•

• org.merlotxml.util: Javadoc index of package org.merlotxml.util.

Package Samples:

• org.merlotxml.util.xml.xml4j
• org.merlotxml.util.xml.xerces
• org.merlotxml.util.xml

Classes:

• DTDContentSpecNode: Interface to specify a ContentSpecification node. This is used to describe the content specification of what a DTD element can contain. Example from a DTD: (el1?, el2+ (el3 | el4 | el5)*) Each node is part of a tree and has a type. CONTENT_GROUP nodes correspond to a ( ) delimted container, a CONTENT_SINGLE node would be a single element leaf with no ordinality specified. (like 'el3' in the above example) Possible types: CONTENT_GROUP: ( stuff between parens ) getLeft returns the first node getRight returns null CONTENT_OR: el3 | el4 getLeft returns the first leaf getRight returns a leaf or another ...
• DTDCache: This singleton class is responsible for loading and caching all DTD's required by the system. This manager can load DTD's from the filesystem, URL's, and zip/jar files (not currently implemented). Apps should use this class to retrieve all their DTD's for valid documents (non-validating apps usually ignore the DTD anyway, so they don't really need to use this, but if they do get a DTD, it might be a good idea to call into this class. Here's an example of getting a dtd: DTDCacheEntry dtdentry = DTDCache.getSharedInstance().findDTD(publicId, systemId); where publicId is the DOCTYPE's given public ...
• DTDContentSpec: Interface to specify a ContentSpecification This is used to describe the content specification of what a DTD element can contain. The types this can return are ANY, EMPTY, PCDATA, GROUP where GROUP type specs will have a tree of ContentSpecNodes describing what's in the content specification
• DTDElement: This is an interface that will provide DTD information about an element definition. In the above example, the element's name is "blah", and it has a content spec with (foo?, bar+, baz*).
• DTDDocument: This interface provides means to access the DTD definitions in a manner that can be independent of whatever third party underlying structures are used for the implementation.
• DOMLiaison: DOM Liaison This interface makes up for deficiencies in the DOM API. It allows you to plug in different XML libraries by creating implementations of this interface.
• DTDContentSpecImpl: A Content Specification based on xml4j This is mostly unimplemented due to a possible requirements change while working on this. Do not try to use this stuff :-)
• WrapperException: Wrapper Exception Used to wrap exceptions, usually those thrown by implementations of custom interfaces
• DTDContentSpecNodeImpl: A Content Specification Node based on xml4j mostly dead unused code right now... requirements changes
• DOMLiaisonImplException: DOM Liaison Implementation Exception Used to wrap exceptions thrown by implementors of DOMLiaison
• ValidDOMLiaison: This interface provides means to access the DTD definitions as well as the DOM document
• EncodingMap: This provides a mapping of XML character encoding types to java encoding types
• DTDCacheEntry: This contains information we need to keep with a dtd that has been cached.
• ManifestMaker: This is a util class for creating java Manifest files for packing in jars
• ValidDocument: Container for a validated Document and it's DTDDocuments
• DOMLiaisonFactory: Convenience class to make getting a DOM Liaison easier
• DTDAttribute: This interface provides access to an attribute
• DTDDocumentImpl: A DTDDocument based on the XML 4j package
• DTDElementImpl: A DTDDocument based on the XML 4j package
• DOMLiaison: Xerces DOM Liaison Implementation
• DTDConstants: provides constant values
• XPathUtil: General XPath utilities
• StringUtil: String utilities
• FileUtil: File utilities

Home | Contact Us | Privacy Policy | Terms of Service