Skip Headers

# XSD File Format

Previous

Next

Starting with 10g (10.1.3.1.0), the `sessions.xml` file uses an XML schema file format (XSD file) instead of the old document type definition. In addition to gaining all the benefits of using an XSD, this change ensures that the TopLink run-time environment provides better diagnostics during `sessions.xml` file loading and validation.

The XSD files are also available on OTN at: `http://www.oracle.com/technology/oracleas/schema/sessions_10_1_3.xsd`

When you use the XSD formatted `sessions.xml` file, the TopLink run time separates `sessions.xml` file validation from session instantiation. Separating XML file formatting problems from Session Manager session instantiation problems simplifies troubleshooting. Exceptions thrown during validation clearly indicate that the failure is due to an invalid `sessions.xml` file as Example: Enhanced Validation Exceptions illustrates.

Enhanced Validation Exceptions

    Exception [TOPLINK-9010] (Oracle TopLink - 10g (10.0.3)(Build 040127Dev)): oracle.toplink.exceptions.SessionLoaderException
    Exception Description: A End tag does not match start tag 'session'. was thrown while parsing the XML file against the XML schema.
    Internal Exception: oracle.xml.parser.v2.XMLParseException: End tag does not match start tag 'session'.