Improve XSLT in overlord commons installer ------------------------------------------ Key: SRAMP-251 URL: https://issues.jboss.org/browse/SRAMP-251 Project: S-RAMP Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 0.3.0 - JBPM6 Integration Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.3.1 - jBPM - bugfix 1 The current overlord commons installer XSLT used to add security domains to jboss eap/wildfly has an ambiguous element declaration. When adding the security domain, the xslt has this: {code} <security-domains> <security-domain /> </security-domains> {code} Because the XSLT doesn't declare a default namespace, this is problematic depending on the processor used. Instead, the XSLT should be explicit about the QNames used in any element it creates. Note that the XSLT is currently designed to work with both EAP and Wildfly, which have different namespaces for the element being created. So we'll likely need multiple templates for multiple versions of the "as" namespace.