[ODFTOOLKIT-44] Remove Xerces Parser Implementation from API

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: simple-odfdom-0.8
• Fix Version/s: odfdom-0.8.7
• Component/s: java
• Environment: Operating System: All; Platform: All
• Bugzilla Id: 67
• Assignee: Svante Schubert
• Reporter: Svante Schubert
• Created: 29/Jul/09 19:57
• Updated: 02/May/13 02:28
• Resolved: 28/May/10 13:45

Description

There is one current dependency of the ODFDOM API to the Xerces parser that is overwhelming (esp. obvious when viewing the JavaDoc).

Currently all ODF elements and attributes take advantage of the Xerces DOM implementation by inheriting from it.

Instead the W3C interfaces for attribute, element and document should be implemented and dispatched via composition to the implementation, hiding the implemention.
The advantage no user might use accidentally Xerces implementation that would be dropped when we change the parser and even more important we have the change to notify ourselves when the DOM implementation is being invoked and are able to do additional actions (important if we might want to keep DOM and DOC layer in synch)..

There come three classes into my mind that each should implement one of the W3C DOM interfaces:

org.odftoolkit.odfdom.OdfAttribute
org.odftoolkit.odfdom.OdfElement
org.odftoolkit.odfdom.OdfFileDom

should implement

http://www.j2ee.me/javase/6/docs/api/org/w3c/dom/Attr.html
http://www.j2ee.me/javase/6/docs/api/org/w3c/dom/Element.html
http://www.j2ee.me/javase/6/docs/api/org/w3c/dom/Document.html

The downside seems to be that instead of one Java object, there are two being referenced. It would be interesting would this means in terms of resource (esp. memory) consumption.

Issue Links

• is depended upon by: ODFTOOLKIT-34 Assigning shape objects the adequate style:family (graphic/presentation)
• is depended upon by: ODFTOOLKIT-45 Provide only allowed newChildElement methods dependent on attribute value
• is depended upon by: ODFTOOLKIT-46 Use composition instead of inheritance between DOM and DOC level