[
https://issues.jboss.org/browse/WFLY-1357?page=com.atlassian.jira.plugin....
]
Radoslav Husar commented on WFLY-1357:
--------------------------------------
{quote}
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.
{quote}
Most transformations now ignore the concrete version (mostly rbac being an exception
here), the remaining jgroups/infinispan done in WFLY-3575.
XSLT scripts for integration tests failing silently
---------------------------------------------------
Key: WFLY-1357
URL:
https://issues.jboss.org/browse/WFLY-1357
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite
Affects Versions: 8.0.0.Alpha1
Environment: Wildfly integration tests
Reporter: Richard Achmatowicz
Assignee: Ondrej Zizka
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
(v6.2.6#6264)