You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2019/08/27 12:16:00 UTC

[jira] [Updated] (JCRVLT-357) Split up DocViewSaxImporter: Separate parsing from importing

     [ https://issues.apache.org/jira/browse/JCRVLT-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus updated JCRVLT-357:
-----------------------------------
    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.  (was: 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) from the actual import.)

> Split up DocViewSaxImporter: Separate parsing from importing
> ------------------------------------------------------------
>
>                 Key: JCRVLT-357
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-357
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: vlt
>            Reporter: Konrad Windszus
>            Priority: Major
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)