[ODFTOOLKIT-478] Adding namespaces to manifest and digital signature DOM by fix & refactoring of generator

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.6.2-incubating
• Fix Version/s: 0.6.2-incubating
• Component/s: generator, odfdom
• Flags: Patch
• Assignee: Svante Schubert
• Reporter: Svante Schubert
• Created: 02/Oct/18 11:05
• Updated: 02/Oct/18 11:14
• Resolved: 02/Oct/18 11:14

Description

There are no namespaces generated for the generated DOM classes of the manifest schema and the digital signature schema.

I realized this during my attempt to continue merging the ODFDOM of my feature branch

https://github.com/svanteschubert/odftoolkit/tree/odf-changes

with our latest ODFDOM version.

As I am funded by PrototypeFund and will work as well on the source code generation for the ODF Toolkit, I have done several updates already.

1. Updated from Apache Velocity 1.7 to 2.0 (to read the latest manual and get latest features)
2. Using latest Apache Xerces parser instead of the JDK bundled parser (just a precaution) for a compile-time library.
3. The Velocity template shall in the future derive from each other ODF 1.2 DOM java fixes/enhancements for the DOM of the content.xml/meta.xml/styles.xml shall be simultaneously used by manifest and signature.
4. I continue to refactor (after this issue) and make generation more modular so DOM from other formats can easier be loaded.
5. Later (after this issue), it is to consider if some Attributes in general and some simple Elements become members of a class to raise. Performance tests might tell.

 I have first refactored within Schema Generator and fixed afterwards the ODFDOM package layer, therefore there are two patches.