[jboss-jira] [JBoss JIRA] (WFLY-1357) XSLT scripts for integration tests failing silently

Radoslav Husar (Jira) issues at jboss.org
Wed Feb 13 06:01:00 EST 2019


     [ https://issues.jboss.org/browse/WFLY-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar closed WFLY-1357.
--------------------------------
      Assignee: Radoslav Husar
    Resolution: Out of Date


Out of date -- we no longer use these transformations and use CLI scripting instead.

> XSLT scripts for integration tests failing silently
> ---------------------------------------------------
>
>                 Key: WFLY-1357
>                 URL: https://issues.jboss.org/browse/WFLY-1357
>             Project: WildFly
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 8.0.0.Alpha1
>         Environment: Wildfly integration tests
>            Reporter: Richard Achmatowicz
>            Assignee: Radoslav Husar
>            Priority: Optional
>
> 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.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jboss-jira mailing list