incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian Hopf (JIRA)" <>
Subject [jira] [Updated] (ODFTOOLKIT-172) Enable mechanism to initiate custom DOM classes for custom XML
Date Wed, 19 Dec 2012 06:09:18 GMT


Florian Hopf updated ODFTOOLKIT-172:

    Fix Version/s:     (was: odfdom-0.9)
> Enable mechanism to initiate custom DOM classes for custom XML
> --------------------------------------------------------------
>                 Key: ODFTOOLKIT-172
>                 URL:
>             Project: ODF Toolkit
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: odfdom-0.8.7
>         Environment: Operating System: Windows
> Platform: PC
>            Reporter: Svante Schubert
>            Assignee: Svante Schubert
>            Priority: Minor
> Users might want to register their own DOM classes for their XML files.
> Currently for every ODF XML file a typed DOM tree is being generated.
> Typed DOM as every XML element & attribute is represented by a special ODF class
(inheriting from DOM implementation for Element or Attr).
> The sources of those typed DOM classes are being generated from the ODF schema. Their
purpose is to give the user a clue about what can be added to the XML node.
> The classes being used for this typed DOM tree are bundled with the ODFDOM library and
intantiated when an XML file is being parsed.
> Although it is possible to exchange those classes with own implementation, it is only
possible for ODF XML nodes. It is not impossible to provide own classes for custom XML and
let them being invoked during parsing.
> If for instance the user might register its own Factory that take care of certain XML
namespaces, the library would be extensible.
> Allowing that for instance MathML support (special DOM classes) are being added during

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message