Description
To be able to reuse the logic from DocViewSaxImporter (e.g. in the context of JCRVLT-345) the parsing part (i.e. deserializing into DocViewNodes) should be separated from the actual import.
Attachments
Issue Links
- blocks
-
SLING-11134 Extract Oak index definitions and package them as an additional file
- Closed
- breaks
-
JCRVLT-644 Import of package with not well-formed DocViews behaves differently since 3.6.0 for isStrict = false
- Closed
- causes
-
JCRVLT-638 Importing empty multivalue property does no longer work
- Closed
- is related to
-
JCRVLT-582 Package import fails for namespaced paths and path mapping
- Open
-
SLING-7959 ContentParser: Complete support for (Extended) DocView
- Open
- relates to
-
JCRVLT-407 DocView XML: Proper namespace support for node names during import
- Resolved
-
JCRVLT-345 Support pluggable node/file/filter validators
- Closed
-
SLING-10808 Generate scripting capabilities from Jackrabbit FileVault content packages
- Closed
- links to