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

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

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

    [ https://issues.apache.org/jira/browse/JCRVLT-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916856#comment-16916856 ] 

Tobias Bocanegra commented on JCRVLT-357:
-----------------------------------------

I agree that the importer can be optimized ;-) but it has grown over the last years to accommodate all special cases that came up, and is IMO a bit fragile to changes. I would be very scared to change much in that code.
also, it must still support importing of very large trees, which do not fit into memory...

> 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
>             Fix For: 3.2.10
>
>
> 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)