Add support for "oak" XML-Namespace
Description
Gliffy Diagrams
Activity
Show:
Stefan Seifert February 27, 2017 at 3:57 PM
PR is merged
Alexander Muthmann February 27, 2017 at 3:54 PM
Sry, didn't know the workflow
Yes, the issue happens from conga
Stefan Seifert February 27, 2017 at 3:52 PM
(please do not set issues with unmerged PRs to resolved)
the list of default list of namespaces is hardcoded, but the API of the content package builder allows to add your own ones. i assume you you are using this in context of CONGA, and in CONGA it's not yet possible to define additional XML namespaces for generated packages.
nevertheless it makes sense to add the oak NS to the list of default namespaces.
Alexander Muthmann February 25, 2017 at 10:02 AMEdited
Due to the changes in XmlNamespaces I had to increase the version from 1.1.x to 1.2.0
Fixed
Details
Details
Assignee
Unassigned
UnassignedReporter
Alexander MuthmannComponents
Fix versions
Priority
MajorCreated February 25, 2017 at 9:58 AM
Updated November 13, 2017 at 2:58 PM
Resolved February 27, 2017 at 3:57 PM
The XML-Namespaces used to build a content-package are hard-coded in XmlNamespace.java.
Currently the oak namespace is not supported. Therefor it's not possible to create a content-package to define an oak:index definition.