Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-5041

Migrate xml import/export framework to the Rice core

        Details

        • Type: Improvement Improvement
        • Status: Closed Closed
        • Priority: Blocker Blocker
        • Resolution: Fixed
        • Affects Version/s: None
        • Fix Version/s: 2.0
        • Component/s: Modularity
        • Security Level: Public (Public: Anyone can view)
        • Labels:
          None
        • Similar issues:
          KULRICE-1111move db import/export code into rice tools
          KULRICE-2634Implement support for better XML export, XML import and migration features
          KULRICE-2155Extract database import/export process from kul-cfg-dbs to rice-tools
          KULRICE-4201Create a POC using JAXB
          KULRICE-18Extend "RiceTestCase" so that it can also be used by Rice Client developers and not just Rice Core Developers
          KULRICE-4633Break out core into it's own module
          KULRICE-6020Affirm strategy for XML namespacing on Rice services
          KULRICE-2579Clean up xml bootstrap files
          KULRICE-1065clean up old db import/export code
          KULRICE-9450Enhance JAXBConfigImpl to handle both .xml and .properties files
        • Rice Module:
          Rice Core
        • KAI Review Status:
          Not Required
        • KTI Review Status:
          Not Required

          Description

          This has to be done in order to support modularity of KEW, EDL, and KIM. Currently xml import/export is part of kew but it's handling import and export for EDL and for KIM.

          In order to accomplish this, we will need to introduce an SPI as part of the core-framework module that allows modules to "register" their XmlLoaders and XmlExporters with an impex registry running in the core. The ingester UI will also need to move to "core-web"

            Issue Links

            is relied upon by

            Sub Task - A small part of the whole. KULRICE-4827 Create edoclite module

            • Major - Major loss of function.
            • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Eric Westfall added a comment -

              This work is effectively done and has been committed on the 2.0 trunk.

              Show
              Eric Westfall added a comment - This work is effectively done and has been committed on the 2.0 trunk.
              Hide
              Permalink
              Jessica Coltrin (Inactive) added a comment -

              Closing since these items are now in the release notes.

              Show
              Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

                People

                • Assignee:
                  Eric Westfall
                  Reporter:
                  Eric Westfall
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel