Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-1357

XSLT scripts for integration tests failing silently

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Optional Optional
    • None
    • 8.0.0.Alpha1
    • Test Suite
    • None
    • Wildfly integration tests

      We use XSLT scripts to build custom Wildfly distributions for testing.

      Hard-coding of Wildfly subsystem namespace versions with no corresponding update to the scripts when schema versions change is causing XSLT scripts to be executed but silently not carry out the intended changes, resulting in broken test cases, of which no one is aware.

      For example:
      <xsl:stylesheet xmlns:jgroups="urn:jboss:domain:jgroups:1.1"

      <xsl:template match="//jgroups:subsystem">
      // do something
      </xsl:template>

      <xsl:stylesheet>

      will do nothing when executed against a 2.0 jgroups schema.

      We need to have a general mechanism in place to work around the need to hardcode namespace versions when the namespace version is general and not specific. This needs to be applied to most XSLT scripts.

              rhn-engineering-rhusar Radoslav Husar
              rachmato@redhat.com Richard Achmatowicz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: