Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: FutureVersion
    • Component/s: Core & storage
    • Labels:
      None

      Description

      In order to facilitate the move to a different backend in 3.0, and also allowing people the choice of the 3.0 backend provider, we should have an export tool which can export the old format repository to the JCR XML export format (System View). This will also be useful in 3.0 for people who want to have an implementation-independent database dump.

      A couple of requirements:

      • Must run with existing 2.8.x
      • Must have an export functionality in the Admin UI
      • Should have also a simple GUI
      • Should have also a command-line interface
      • Should also export version histories (though there is no standard representation defined in JCR, we may have to invent our own.)
      • May have built-in compression (the XML files are bound to be large)

      (For 3.0 it then obviously becomes: add a tool which allows importing of such XML document.)

        Issue Links

        1.
        Export Tool GUI-Discussion Sub-task Closed Unassigned
         

          Activity

          Hide
          Harry Metske added a comment -

          You can find the export tool in the 2.8 branches.
          It will not be enhanced/fixed any further since we dropped JCR in 2.9.

          Show
          Harry Metske added a comment - You can find the export tool in the 2.8 branches. It will not be enhanced/fixed any further since we dropped JCR in 2.9.
          Hide
          Harry Metske added a comment -

          Since we less or more cancelled 3.0, we will not fix this in 2.8.5.

          Show
          Harry Metske added a comment - Since we less or more cancelled 3.0, we will not fix this in 2.8.5.
          Hide
          Juan Pablo Santos Rodríguez added a comment -

          Couldn't be classes added in JSPWIKI-690 extended in order to import a 2.8 repo? If this export/import process becomes part of the installation process, it would ease the migration scenario (i.e., we would not worry about someone's editing while the import takes place).

          Show
          Juan Pablo Santos Rodríguez added a comment - Couldn't be classes added in JSPWIKI-690 extended in order to import a 2.8 repo? If this export/import process becomes part of the installation process, it would ease the migration scenario (i.e., we would not worry about someone's editing while the import takes place).
          Hide
          Janne Jalkanen added a comment -

          Bumped to 2.8.3.

          Show
          Janne Jalkanen added a comment - Bumped to 2.8.3.
          Hide
          Florian Holeczek added a comment -

          That's right, but for the user it's not as easy as e.g. with relational databases yet (At least not until this summer, when I've been working with Jackrabbit). We'll save much time with implementing such a feature - because it will avoid many, many questions on the mailing list

          Show
          Florian Holeczek added a comment - That's right, but for the user it's not as easy as e.g. with relational databases yet (At least not until this summer, when I've been working with Jackrabbit). We'll save much time with implementing such a feature - because it will avoid many, many questions on the mailing list
          Hide
          Janne Jalkanen added a comment -

          Well, yes.

          JCR standardizes on import/export format, and there is an API to do it.

          Show
          Janne Jalkanen added a comment - Well, yes. JCR standardizes on import/export format, and there is an API to do it.
          Hide
          Florian Holeczek added a comment -

          For 3.0 it then obviously becomes: add a tool which allows importing of such XML document.

          I think exporting would be a user-friendly feature for 3.0, too. This way, JSPWiki content would be easily portable to another installation. Else the user would depend on the repository's export functionality (if there is any).

          Show
          Florian Holeczek added a comment - For 3.0 it then obviously becomes: add a tool which allows importing of such XML document. I think exporting would be a user-friendly feature for 3.0, too. This way, JSPWiki content would be easily portable to another installation. Else the user would depend on the repository's export functionality (if there is any).
          Hide
          Janne Jalkanen added a comment -

          In addition, we probably need something which allows exporting/importing user databases...

          Show
          Janne Jalkanen added a comment - In addition, we probably need something which allows exporting/importing user databases...
          Hide
          Janne Jalkanen added a comment -

          Committed a first version for review to JSPWIKI_2_8_BRANCH.

          Show
          Janne Jalkanen added a comment - Committed a first version for review to JSPWIKI_2_8_BRANCH.

            People

            • Assignee:
              Unassigned
              Reporter:
              Janne Jalkanen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development