Derby
  1. Derby
  2. DERBY-1758

Enable xmlSuite to run as part of derbyall in environments that have the required external jars.

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.2.1.6, 10.2.2.0, 10.3.1.4
    • Fix Version/s: 10.3.1.4
    • Component/s: Test
    • Labels:
      None
    • Urgency:
      Normal

      Description

      Due to the fact the XML support in Derby has external dependencies on Apache Xalan and a JAXP parser (such as, but not limited to, Apache Xerces), the tests for XML, which are all included in "xmlSuite", are not currently run as part of derbyall.

      Changes for DERBY-688 (and DERBY-567 indirectly) have now made it so that JVMs which have Apache Xalan and a JAXP parser embedded in them can run the XML tests without requiring additional jars, assuming that the embedded version of Xalan is at least the minimum version required by Derby (which is currently 2.5).

      So given that, the xmlSuite should be enabled as part of derbyall for any environment that is capable of running them.

      Per comments in DERBY-688, enabling the XML suite could include the following tasks:

      1. Enable the suite to run as part of derbyall but ONLY if the JVM has
      access to all of the required Xalan/JAXP classes.

      2. Resolve the following diff in lang/xmlBinding.java that occurs on
      some platforms (ex. Linux):

      < Inserted roughly 40k of data.
      10 del
      < Inserted roughly 40k of data.
      10a9,10
      > Inserted roughly 39k of data.
      > Inserted roughly 37k of data.
      21 del
      < 1, [ roughly 40k ]
      22 del
      < 2, [ roughly 40k ]
      22a21,22
      > 1, [ roughly 39k ]
      > 2, [ roughly 37k ]

      3. Add new tests to verify Derby behavior when XML classes are
      not present.

      Note that #3 may turn out to be its own Jira issue; the first two, however, should both be addressed as part of this issue since the xmlSuite will not run (and pass) on all platforms if either 1 or 2 is not addressed.

      1. d1758_secmgr_v1.stat
        0.5 kB
        A B
      2. d1758_secmgr_v1.patch
        13 kB
        A B
      3. d1758_remove_xgen_v1.stat
        0.5 kB
        A B
      4. d1758_remove_xgen_v1.patch
        221 kB
        A B
      5. d1758_remove_xbindAndSuite.patch
        32 kB
        A B
      6. d1758_newXMLSuite_v1.patch
        8 kB
        A B
      7. d1758_newXBindTest_v1.patch
        23 kB
        A B
      8. d1758_newSecMgr_doNotCommit.patch
        19 kB
        A B
      9. d1758_newJUnitTests_v2.patch
        112 kB
        A B
      10. d1758_newJUnitTests_v1.stat
        0.4 kB
        A B
      11. d1758_newJUnitTests_v1.patch
        105 kB
        A B
      12. d1758_followup_v1.patch
        21 kB
        A B

        Issue Links

          Activity

          Gavin made changes -
          Workflow jira [ 12382336 ] Default workflow, editable Closed status [ 12799551 ]
          A B made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          A B made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          A B made changes -
          Fix Version/s 10.3.0.0 [ 12310800 ]
          Summary Enable xmlSuite to run as part of derbyall for JVMs that embed the required external jars. Enable xmlSuite to run as part of derbyall in environments that have the required external jars.
          Description Due to the fact the XML support in Derby has external dependencies on Apache Xalan and a JAXP parser (such as, but not limited to, Apache Xerces), the tests for XML, which are all included in "xmlSuite", are not currently run as part of derbyall.

          Changes for DERBY-688 (and DERBY-567 indirectly) have now made it so that JVMs which have Apache Xalan and a JAXP parser embedded in them can run the XML tests without requiring additional jars, assuming that the embedded version of Xalan is at least the minimum version required by Derby (which is currently 2.5).

          So given that, the xmlSuite should be enabled as part of derbyall for any JVMs that are capable of running them. Currently, this appears to mean only ibm142 and ibm15.

          Per comments in DERBY-688, enabling the XML suite could include the following tasks:

            1. Enable the suite to run as part of derbyall but ONLY for JVMs that
               embed the required Xalan/JAXP classes.

            2. Resolve the following diff in lang/xmlBinding.java that occurs on
               some platforms (ex. Linux):

              < Inserted roughly 40k of data.
              10 del
              < Inserted roughly 40k of data.
              10a9,10
              > Inserted roughly 39k of data.
              > Inserted roughly 37k of data.
              21 del
              < 1, [ roughly 40k ]
              22 del
              < 2, [ roughly 40k ]
              22a21,22
              > 1, [ roughly 39k ]
              > 2, [ roughly 37k ]

            3. Add new tests to verify Derby behavior when XML classes are
              not present.

          Note that #3 may turn out to be its own Jira issue; the first two, however, should both be addressed as part of this issue since the xmlSuite will not run (and pass) on all platforms if either 1 or 2 is not addressed.
          Due to the fact the XML support in Derby has external dependencies on Apache Xalan and a JAXP parser (such as, but not limited to, Apache Xerces), the tests for XML, which are all included in "xmlSuite", are not currently run as part of derbyall.

          Changes for DERBY-688 (and DERBY-567 indirectly) have now made it so that JVMs which have Apache Xalan and a JAXP parser embedded in them can run the XML tests without requiring additional jars, assuming that the embedded version of Xalan is at least the minimum version required by Derby (which is currently 2.5).

          So given that, the xmlSuite should be enabled as part of derbyall for any environment that is capable of running them.

          Per comments in DERBY-688, enabling the XML suite could include the following tasks:

            1. Enable the suite to run as part of derbyall but ONLY if the JVM has
                access to all of the required Xalan/JAXP classes.

            2. Resolve the following diff in lang/xmlBinding.java that occurs on
               some platforms (ex. Linux):

              < Inserted roughly 40k of data.
              10 del
              < Inserted roughly 40k of data.
              10a9,10
              > Inserted roughly 39k of data.
              > Inserted roughly 37k of data.
              21 del
              < 1, [ roughly 40k ]
              22 del
              < 2, [ roughly 40k ]
              22a21,22
              > 1, [ roughly 39k ]
              > 2, [ roughly 37k ]

            3. Add new tests to verify Derby behavior when XML classes are
              not present.

          Note that #3 may turn out to be its own Jira issue; the first two, however, should both be addressed as part of this issue since the xmlSuite will not run (and pass) on all platforms if either 1 or 2 is not addressed.
          Derby Info [Patch Available]
          A B made changes -
          Derby Info [Patch Available]
          A B made changes -
          Attachment d1758_secmgr_v1.patch [ 12346245 ]
          Attachment d1758_secmgr_v1.stat [ 12346246 ]
          A B made changes -
          Link This issue is blocked by DERBY-2131 [ DERBY-2131 ]
          A B made changes -
          Attachment d1758_remove_xbindAndSuite.patch [ 12345512 ]
          A B made changes -
          Attachment d1758_newXMLSuite_v1.patch [ 12345502 ]
          A B made changes -
          Attachment d1758_newSecMgr_doNotCommit.patch [ 12345453 ]
          A B made changes -
          Attachment d1758_newXBindTest_v1.patch [ 12345167 ]
          A B made changes -
          Attachment d1758_remove_xgen_v1.patch [ 12344045 ]
          Attachment d1758_remove_xgen_v1.stat [ 12344046 ]
          A B made changes -
          Assignee A B [ army ]
          A B made changes -
          Attachment d1758_followup_v1.patch [ 12343810 ]
          Bryan Pendleton made changes -
          Derby Info [Patch Available]
          A B made changes -
          Derby Info [Patch Available]
          A B made changes -
          Attachment d1758_newJUnitTests_v2.patch [ 12343588 ]
          A B made changes -
          Derby Info [Patch Available]
          A B made changes -
          Derby Info [Patch Available]
          A B made changes -
          Attachment d1758_newJUnitTests_v1.patch [ 12343418 ]
          Attachment d1758_newJUnitTests_v1.stat [ 12343419 ]
          A B made changes -
          Field Original Value New Value
          Link This issue is related to DERBY-688 [ DERBY-688 ]
          A B created issue -

            People

            • Assignee:
              A B
              Reporter:
              A B
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development