July 19, 1999
Changes:
Improved Lexer. With JDK 1.6, the XMLParser seems to have better performance overall because of changes in the lexical analyzer.
New Interface: XMLToken. Applications can register an interface handle and the interface callback method 'token()' receives XML tokens registered and found by the parser. XML tokens are defined as interface constants. They are:
STagName,
EmptyElemTag,
STag,
ETag,
ETagName,
Attribute,
AttName,
AttValue,
Reference,
Comment,
CharData,
CDSect,
PI,
PITarge,
XMLDecl,
TextDecl,
DTDName,
AttListDecl,
elementdecl,
ElemDeclName,
EntityDecl,
EntityDeclName,
EntityValue,
NotationDecl,
ExternalID.
The tokens above correspond to the syntax variables from W3C XML specifications.
New API in the following Classes:
1. oracle.xml.parser.XMLParser
-setTokenHandler (XMLToken handler). Sets XMLtoken interface handler.
-setToken (int token, boolean val). Registers on/off XML token.
This is the first production release for V1.0.2.
Oracle XML Parser 1.0.1.4.0
---------------------------
June 10, 1999
Changes:
Bug fixes for #893971, i.e XML parser cannot parse documents from InputStream; #900146 normalize() is wrong if the literal contains angle brackets; #898423, multiplicity info about elements enhancement.
New API in the following Classes:
1. oracle.xml.parser.ElementDecl
-getParseTree( Returns the root Node of Content Model parse tree, which could then be traversed node by node using getFirstChild() and getLastChild(). The Node types are: PLUS, COMMA, ASTERISK, ELEMENT, QMARK ).
This is the fourth production patch release.
Oracle XML Parser 1.0.1.3.0
---------------------------
May 10, 1999
Changes:
Bug fixes for #860330, XML parser cannot parse documents with stylesheet PI's in them; #860329, XML parser gives errors in validate mode if doc doesn't have a DTD; #856914, XML document should accept a java.io.printwriter; and some enhancements were made to optimize performance in the non-validating mode.
This is the third production patch release.
Oracle XML Parser 1.0.1.2.0
---------------------------
April 9, 1999
Changes:
Bug fixes for #860163, parsing external DTD failed with a null pointer; #860153, when the element doesn't have any attributes, have XMLElement return empty NamedNodeMap instead of null; fixed a bug in printExternalDTD to print the parenthesis correctly in an ELEMENT declaration.
In addition, in case of errors in user-defined SAX functions, better error messages will result.
New APIs in the following Classes:
1. oracle.xml.parser.XMLElement
-getChildrenByTagName( Gets all immediate children with a given tag name)
This is the second production patch release.
Oracle XML Parser 1.0.1.1.0
---------------------------
March 12, 1999
Changes:
Bug fixes for #843157, parseDTD(InputSource, rootElement) and parseDTD(URL, rootelement) then parse(InputSource) bugs; #843143, parse(InputSource) bug; #793012, no need to print a trace of an exception which is rethrown.
This is the first production patch release.
Oracle XML Parser 1.0.1.0.0
---------------------------
February 5, 1999
Changes:
NodeFactory class has been made public. Applications can extend this class to create custom-made nodes in the DOM tree.
Bug fixes for #808645, XML parser should support user-supplied element factories, resulting in the exposure of a number of classes and methods;
adding a method getAttDefs() to get
the default values of a Attribute, adding a method setDynDTDURL() that loads the DTD as
a Java resource. In addition, a method to obtain the version string will be added.
New APIs in the following Classes:
1. oracle.xml.parser.XMLParser
-setNodeFactory(Register a user defined NodeFactory)
This is the first production release.
Oracle XML Parser 1.0.0.3.0
---------------------------
January 29, 1999
Changes:
Bug fixes for #808648, minor bugs in XML parser's print method, and other
internally found bugs, e.g., if the name isn't in the attribute list, a
null is now returned.
This is the last beta patch release before production.
Oracle XML Parser 1.0.0.2.0
---------------------------
January 15, 1999
Changes:
Bug fixes for #794676, i.e., when parsing InputStream and entity references to files are defined in the DTD of the XML document, an error message is printed if the file is not of URL format; 791919, i.e., character set encodings for Norway, Sweden, Italy, Netherlands, Greece, and Belgium have been added.
Lastly, the following APIs have been made public:
APIs in the following new Classes:
1. oracle.xml.parser.DTD
2. oracle.xml.parser.AttrDecl
3. oracle.xml.parser.ElementDecl
New APIs in the following Classes:
1. oracle.xml.parser.XMLParser
- parseDTD (parses an external
DTD file)
- setBaseURL (set a base
URL for resolving external entities)
2. oracle.xml.parser.XMLDocument
- print (prints the XMLDocument)
- printExternalDTD (prints
the External DTD)
- getVersion/setVersion
(gets/sets the XML version of the document)
- getEncoding/setEncoding
(gets/sets the encoding of the document)
Oracle XML Parser 1.0.0.1.0
---------------------------
December 23, 1998
Changes:
Bug fixes for #783023, i.e., the parse methods taking InputStream and InputSource arguments give an exception; #786219, i.e., the hasChildNodes method gives an exception when checking if a node's child has children; #784474, i.e., the getAttribute method returns a string containing the value of the attribute node twice, not once.
Modifications to reduce memory usage and improve performance when using SAX APIs.
Oracle XML Parser 1.0.0.0.0
---------------------------
December 7, 1998
The Oracle XML parser is an early beta release and is written in Java. It will check if an XML document is well-formed and, optionally, if it is valid. The parser will construct a Java object tree which can be accessed.
The licensing agreement is found in LICENSE. The parser is currently available only for testing purposes. We expect to make the parser available for commercial use in the future.
Please post any questions, comments, or bug reports to the XML Forum on the Oracle Technology Network at http://technet.oracle.com. At this time OTN is your only support resource.
The parser conforms to the following standards:
* The W3C recommendation for Extensible Markup Language (XML) 1.0 at
http://www.w3.org/TR/1998/REC-xml-19980210
* The W3C recommendation for Document Object Model Level 1 1.0 at
http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001
* The W3C proposed recommendation for Namespaces in XML at
http://www.w3.org/TR/1998/PR-xml-names-19981117
* The Simple API for XML (SAX) 1.0 at http://www.megginson.com/SAX/index.html
The parser currently supports the following encodings: UTF-8, UTF-16, ISO-10646-UCS-2, ISO-10646-UCS-4, US-ASCII, EBCDIC-CP-US, ISO-8859-1, and Shift_SJIS. UTF-8 is the default encoding if none is specified. Any other ASCII or EBCDIC based encodings that are supported by the JDK may be used. However, they must be specified in the format required by the JDK instead of as official character set names defined by IANA. Additional encodings will be added to the list of supported encodings in future releases.
The parser also provides error recovery. It will recover from most errors and continue processing until a fatal error is encountered.
The following directories and files are found in the release:
license.html - licensing agreement
readme.html - this file
doc/ - API documentation
lib/ - contains the XML parser archive
sample/ - contains examples of how to use the XML parser