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

exporting Groups with XML option does not create a format that is recognized by the XML ingester

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.2.1
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-4624Reinvestigation into applying nice formatting and rendering for exported XML
      KULRICE-4332 Build xml export support for Groups screen
      KULRICE-1130improve performance of xml ingestion
      KULRICE-2634Implement support for better XML export, XML import and migration features
      KULRICE-4073XML Transform Export
      KULRICE-2450XML Ingester does not display helpful error messages
      KULRICE-13915XML Export for document does not include the nextAppDocStatus
      KULRICE-5041Migrate xml import/export framework to the Rice core
      KULRICE-9805Lookup - Need export for document type xml to use proper export function
      KULRICE-9487Inquiry export button does not open file download dialog

      Description

      exported file:
      <?xml version="1.0"?>
      <table>
      <row>
      <column>Default</column>
      <column>KUALI</column>
      <column>UA.TRMS.TravelAdministrators</column>
      <column>Users who are staff in the UA.TRMS department and administrators of the Travel application.</column>
      </row>
      </table>

      Error:
      Ingestion failed
      Failed to ingest xml doc: export-grouptraveladmin.xml
      Error parsing xml doc ingester5385183989933746901.tmp:export-grouptraveladmin.xml
      org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'table'.
      at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
      at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
      at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
      at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
      at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
      at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
      at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
      at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
      at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
      at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
      at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
      at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
      at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
      at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
      at org.kuali.rice.kew.batch.XmlIngesterServiceImpl.validate(XmlIngesterServiceImpl.java:161)

        Activity

        Hide
        Saurabh Ajmera (Inactive) added a comment -

        Greg Patterson added a comment - 21/Apr/10 04:58 PM
        Anne,

        We've marked this in a Post1.0 implementation task. I've linked it for reference.
        [ Show » ]
        Greg Patterson added a comment - 21/Apr/10 04:58 PM Anne, We've marked this in a Post1.0 implementation task. I've linked it for reference.

        [ Permalink | Edit | Delete | « Hide ]
        Eric Westfal added a comment - 22/Apr/10 03:27 PM
        Greg, after looking at this, it looks like an exporter was already implemented for this. See the following classes:

        org.kuali.rice.kew.export.DataExporter

        and then you would just need to add an entry to the business object entry in the data dictionary for GroupImpl:

        <property name="exporterClass" value="org.kuali.rice.kew.export.DataExporter"/>

        I'm not sure if the original exporter that was implemented is actually working or not, but you can figure that out
        [ Show » ]
        Eric Westfal added a comment - 22/Apr/10 03:27 PM Greg, after looking at this, it looks like an exporter was already implemented for this. See the following classes: org.kuali.rice.kew.export.DataExporter and then you would just need to add an entry to the business object entry in the data dictionary for GroupImpl: <property name="exporterClass" value="org.kuali.rice.kew.export.DataExporter"/> I'm not sure if the original exporter that was implemented is actually working or not, but you can figure that out

        [ Permalink | Edit | Delete | « Hide ]
        Greg Patterson added a comment - 23/Apr/10 04:56 PM
        Completed and committed.

        EN-1773: KR-REG: exporting Groups with XML option does not create a format that is recognized by the XML ingester
        EN-1472: Build xml export support for Groups screen

        Completed by hooking up the GroupExporter written in the rice code with a minor namespace fix and hooks to the bean and DataExporter definition.

        Refer https://uisapp2.iu.edu/jira-prd/browse/EN-1773

        Show
        Saurabh Ajmera (Inactive) added a comment - Greg Patterson added a comment - 21/Apr/10 04:58 PM Anne, We've marked this in a Post1.0 implementation task. I've linked it for reference. [ Show » ] Greg Patterson added a comment - 21/Apr/10 04:58 PM Anne, We've marked this in a Post1.0 implementation task. I've linked it for reference. [ Permalink | Edit | Delete | « Hide ] Eric Westfal added a comment - 22/Apr/10 03:27 PM Greg, after looking at this, it looks like an exporter was already implemented for this. See the following classes: org.kuali.rice.kew.export.DataExporter and then you would just need to add an entry to the business object entry in the data dictionary for GroupImpl: <property name="exporterClass" value="org.kuali.rice.kew.export.DataExporter"/> I'm not sure if the original exporter that was implemented is actually working or not, but you can figure that out [ Show » ] Eric Westfal added a comment - 22/Apr/10 03:27 PM Greg, after looking at this, it looks like an exporter was already implemented for this. See the following classes: org.kuali.rice.kew.export.DataExporter and then you would just need to add an entry to the business object entry in the data dictionary for GroupImpl: <property name="exporterClass" value="org.kuali.rice.kew.export.DataExporter"/> I'm not sure if the original exporter that was implemented is actually working or not, but you can figure that out [ Permalink | Edit | Delete | « Hide ] Greg Patterson added a comment - 23/Apr/10 04:56 PM Completed and committed. EN-1773: KR-REG: exporting Groups with XML option does not create a format that is recognized by the XML ingester EN-1472: Build xml export support for Groups screen Completed by hooking up the GroupExporter written in the rice code with a minor namespace fix and hooks to the bean and DataExporter definition. Refer https://uisapp2.iu.edu/jira-prd/browse/EN-1773

          People

          • Assignee:
            Saurabh Ajmera (Inactive)
            Reporter:
            Saurabh Ajmera (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel